SQL Server 2005 Deployment on Windows Shared Server Hosting

SQL Server 2005 Deployment management on Windows Shared Server Hosting Plan

Requirement:

Windows shared hosting Server should be with 32-bit processor and minimum of 3GB of RAM including Windows Server™ 2003 operating system.

Possibilities:

a) In various situations, managing several instances of SQL Server on a particular server can support additional users than a single instance of SQL Server.

b) CLR integration with SQL Server offers developers who are well-known with .NET programming the skill to code database objects by using the programming language they previously know.

EXEC sp_configure ‘show advanced options’, 1
RECONFIGURE
GO

EXEC sp_configure ‘clr enabled’, 1
RECONFIGURE
GO

c) Using the query cost governor can avoid run off queries from overwhelming lots of resources on a Windows shared hosting server.

Whenever SQL Server obtains a query, the query optimizer produces probable time that the query is likely to take. The query cost governor limit can be used to stop all queries that are probable to take more than a particular amount of time. However, it is possible for the probable time to be inaccurate, which will cause fast-running queries to be cancelled. The choice to apply query cost governor limits is a negotiation between maintaining suitable server performance under load versus the possible for generating client support issues.

EXEC sp_configure ‘show advanced options’, 1
RECONFIGURE GO

EXEC sp_configure ‘query governor cost limit’, 300
RECONFIGURE GO

d) Disabling or Renaming the Built-in SA Account

In SQL Server 2005, the built-in system administrator (SA) account was kept for backward compatibility. As long as it is not necessary, this account ought to be disabled or renamed.

These commands can be used to disable or rename SA account:

ALTER LOGIN sa DISABLE;
ALTER LOGIN sa WITH NAME = [sys-admin];