SQL Enterprise Server 2005 is used to create and maintain the database instance needed by the SoftGrid system to track and collate usage, license and application statistics for the entire Organisation. This database is important for a number of reasons- without it, the SoftGrid Clients will default to disconnected mode, in which only applications stored in the local cache will be available for use. Additionally, this database allows for all reporting needs with regard to user access to applications.
The intended audience for this documentation is Systems Administrators, Workstation Management staff and other interested technical staff. This is only an example installation and a guide that can be used.
Based on SoftGrid Architectural concerns, it is estimated that a minimum of 40GB of usable storage space is needed to store the instance and approximately 730 days (2 years) of usage data.
SQL server 2005 requires Windows 2000 Server or above. In keeping with our overall system architecture, Windows Server 2003 R2 will be used for all SQL installations in this project.
IIS and ASP.net need to be enabled.
Join the machine to the Domain (it is needed)
Installing SQL server 2005 is relatively straightforward, with little variance from the defaults required. You will need a domain level administrative account, and in this case either the installation media or an executable copy of SQL Server 2005.
Step 1. Log in with your domain credentials. Locate either the CD-ROM or executable media
Step 2. Begin installation- double click 'setup.exe'. When prompted to accept licensing terms and conditions, check the box and click 'next'.
Step 3. Click 'Install' and wait for SQL Server to configure components and setup the installation. Once the required components (.NET Framework 2.0, MS SQL Native Client and the SQL Server 2005 setup support files) have been installed click 'Next'.
Step 4. Click 'next' when prompted with the screen 'Welcome to the Microsoft SQL Server Installation Wizard. The installation will then proceed through the 'System Configuration Check'- click 'next' to proceed.
Step 5. Registration Information
Name: Any Authorised User
Company: Any Authorised Company
Step 6. Components to Install- Select all components (SQL Server Database Services, Analysis Services, Reporting Services, Notification Services, Integration Services, Workstation components) , then click 'next'
Step 7. If this is the first installation of a new database instance for SQL server, select 'Default Instance'. (If this is a second or further installation of SQL server, such as for a clustered server farm, contact the SQL database administrator for relevant database information) then click 'Next'.
Step 8. Service Account-
Use a Domain Account (See SoftGrid or Active Directory Administrator)
Domain- contoso.com (or whatever domain is relevant for the circumstance)
Start services at the end of setup-
SQL Server, Analysis Services, Reporting Services, SQL Browser
Step 9. Authentication Mode-
Mixed Mode (Windows Authentication and SQL Server Authentication)
Sa account password: S0ftgrid1
Step10. Collation Settings
Keep the default settings (SQL Collations- Dictionary Order, case-insensitive, 1252 character set)
Step 11. Report Server Installation options
Install the default configuration
Step 12. Error and Usage Report Settings
Leave defaults (none checked)
Step 13. Check installation Settings, click 'install'. Once the installation process is completed, click 'next'
Step 14. Select the 'Surface Area Configuration Tool'; then 'Surface Area Configuration for Services and Connections'
Select 'Database Engine'; 'Remote Connections'
- 'Local and Remote Connection'- 'Using both TCP/IP and named pipes'
- click 'Apply', receive the message stating 'changes will not take effect until you restart the Database Engine service'- click 'Ok', then 'Ok' once more.
- click 'finish'
Step 15. Open 'services.msc' and restart the SQL server service.
Step 15.1 Install SQL Server 2005 SP1 and make sure to stop ALL the SQL services and the Network Connections service to avoid locked files. When done, restart the server.
Step 16. Connect to the server and go to the Security / Logins and create a new SQL account called softgrid
Step 17. Select "Sql Server Authentication", enter the same password than above and untag "Enforce password expiration" then select the default database as tmpdb for the time being.
Step 18. Migrate the softricity database using the SQL Wizard (right click on one of the database then select Tasks and Copy database on the server you want to migrate from). If the Softricity database already exists on the target server, delete it otherwise the migration will create a Softricity_new database.
Step 19. When the database is migrated, make sure that the user softgrid has the rights on it and you can remove the user from the tmpdb database and select softricity as the default database.
A week or so ago I talked about how MSDE (Microsoft SQL Desktop Engine) or SQL Express should not be
do you has installed Softgrid on SQL cluster environment (active-passive)??. i´ve a problem with this case. (its same for SQL 2000 or SQL 2005 Cluster, x32 or x64 bits), Regards.
So I have seen some customers receives the following error message when installing a VAS server which is attempting to create a SQL database on a Microsoft 2003 R2 SP2 Cluster with SQL 2005 which has multiple database instances.
The installation program encountered an error when attempting to execute a database statement. The specified @server_name ("SERVERNAME\INSTANCE04) does not exist.
This issue which the workable and probably fastest way to resolve is to install the VAS to a stand- alone SQL server and then migrate the database that is created on the Stand-alone server over to the SQL Cluster. Once the database is up and running it will
work on the SQL Cluster. Use the following KB article and follow it to the letter to migrate the database.
932136 How to migrate the Microsoft SoftGrid database from one computer that is running Microsoft SQL Server to another computer that is running SQL Server
More information found on an internet blog regarding this issue:
Contents of the blog link above - provided purely for additional information:
There is a known problem with the SoftGrid installation program that it can not deal with installing the database on to SQL Server when there is a named instance as well as a default instance installed on the server.
IMHO there are a number of down falls with the installation program
During the installation of SoftGrid you are asked to select the SQL Server and select a port number (I've never really bothered about port numbers and I've been around SQL Server since 6.5 days). In the environment that we were trying to install SoftGrid
data to is one box with a SQL Server 2000 installed as the default instance (so this runs as the default port number) and SQL Server 2005 runnning as a named instance which is where we want to install SoftGrid. The SQL 2005 service runs on a port number taken
from a pool of dynamic port numbers so without messing around with the service configuration there is no way I can really know what port number SQL is currently running under. The convension is that if you set the port number to 0 then it should tell the client
that it needs to find the dynamic port number , but this didn't work. Blanking out the port number seems to tell the client tool to try to connect using NamedPipes rather than TCP/IP.
The SoftGrid installtion program, I believe, then tries to connect to the server using windows authentication which fails and prompts the user user for a SQL login. According to collegues that have run mutiple installs, it always prompts for the user.We
finally got it working by installing the SQL Server 2005 client connectivity
tools on the SoftGrid server and then using the client tools create an alias which points to the named instance we want to installl to. This acts as a proxy so it fools the SoftGrid install in thinking that it standard single instance SQL Server. The Server
even appears in the list of available server to connect to. (It still prompts for a SQL login in though)
Sorry if this is a bit long winded but let me know if this fixes the issue that you have? Also If this does not, could you tell me the "exact" error message that you recieve! :o)