0% found this document useful (0 votes)
39 views

09 - Post-Installation SQL Server 2008 R2

For default instance, the default ports are 1433 and 1434. For named instance on a server with existing SQL Server instance, just add the static port number to the SQL Server ports rule. If the test failed, you might have to do either of the followings: a. Specify the port number in your server registration, such as SQLMonitorNI01, b. Create an alias in SQL Server Configuration Manager.

Uploaded by

Chris D Mathews
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
39 views

09 - Post-Installation SQL Server 2008 R2

For default instance, the default ports are 1433 and 1434. For named instance on a server with existing SQL Server instance, just add the static port number to the SQL Server ports rule. If the test failed, you might have to do either of the followings: a. Specify the port number in your server registration, such as SQLMonitorNI01, b. Create an alias in SQL Server Configuration Manager.

Uploaded by

Chris D Mathews
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 9

Wake County Post-Installation SQL Server 2008 R2

1. Create an inbound Windows Firewall rule called SQL Server Ports to allow remote user access to SQL Server through assigned TCP/IP ports. (This is needed only on server running Windows Server 2008 R2 or above) For default instance, the default ports are 1433 and 1434. Named instances use static ports. a. Right click on Computer, select Manage. b. Under Server Manager, expand Configuration, then Windows Firewall with Advanced Security.

c. Right click on Inbound Rules and select New Rules . Check Port and then click Next. For named instance on a server with existing SQL Server instance, just add the static port number to the SQL Server Ports rule. You can find the two ports number in the Error log of the instance at restart.

d. Check Specific local ports and enter all the port numbers used by the SQL Server instances installed on the server. Then click Next.

e. Specify Allow the connection if it is secure.

f. Leave the New Inbound Rule Wizard/Users page blank, and click Next.

g. Leave the New Inbound Rule Wizard/Computers page blank, and click Next.

h. In the New Inbound Rule Wizard/Profile page, uncheck Public, then click Next.

i.

In the New Inbound Rule Wizard/Name page, enter SQL Server Portsin the Name field. Click Finish.

2. Open SQL Server Management Studio on a remote computer, register the newly installed SQL Server instance and test the connection. If the test failed, you might have to do either of the followings: a. Specify the port number in your server registration, such as SQLMonitor\NI01,<port number> b. Create an alias in SQL Server Configuration Manager. Expand SQL Native Client 10.0 Configuration, right click on Aliases, select New Alias.

Fill in the Alias Name, Port No for the instance, TCP/IP protocol and the server name, click Apply and OK. 3. Set up the SQL Server Service Accounts. If you have strictly followed steps 20 and 21 of the Installing SQL Server 2008 R2.docx document, the domain account Wake\SQLService is configured to run all SQL Server services, except SQL Server Browser, Full-text search, SQL Server Active Directory Helper, and SQL Writer. By default these services are run as Local Service or Network Service.You can leave them as they are. 4. Open Microsoft SQL Server Management Studio, expand Security/Logins, confirm that both Wake\SQL DBAs and Wake\sqlservice are assigned sysadmin fixed server role, then delete NT AUTHORITY\SYSTEM. 5. Create maintenance plans for each instance. a. Weekly DB Full Backup b. Daily DB Differential Backup (exclude full backup day) c. Hourly Transaction log Backup d. Daily DB Integrity Check e. Daily DB Reorg (Reorganize Index and Update Statistics) f. Weekly DB Optimization (Rebuild Index and Update Statistics) g. Weekly Cycle Error Log The owner of all maintenance jobs should be sa . 6. Configure Integration Services. Modify D:\MSSQL\100\DTS\Binn\MsDtsSrvr.ini.xml as follows:
<?xml version="1.0" encoding="utf-8"?> <DtsServiceConfigurationxmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <StopExecutingPackagesOnShutdown>true</StopExecutingPackagesOnShutdown> <TopLevelFolders> <Folder xsi:type="SqlServerFolder"> <Name>MSDB</Name> <ServerName>SQLMonitor</ServerName> </Folder> <Folder xsi:type="SqlServerFolder"> <Name>MSDB-NI01</Name> <ServerName>SQLMonitor\NI01</ServerName> </Folder>

<Folder xsi:type="FileSystemFolder"> <Name>File System</Name> <StorePath>..\Packages</StorePath> </Folder> </TopLevelFolders> </DtsServiceConfiguration>

Regedit on the server/VM Make sure that the following key is pointing to the path and file above. MyComputer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTS\ServiceConfigfile Restart SQL Server Integration Services. Set startup type of SQL Server Integration Services to Automatic 7. Create an inbound rule SQL Server Integration Services serviceon the server. This allows remote connection to the Integration Services.

Select Program, click Next.

Enter the program path D:\MSSQL\100\DTS\Binn\MsDtsSrvr.exe, then click Next.

Select Allow the connection, click Next.

Select Domain, click Next.

Enter SQL Server Integration Services servicein the Name field, then click Finish. Now you should be able to connect to the Integration Services via SSMS remotely. 8. Static IP for named instance.

You might also like