Using SQL Server On Another PC - Event Date: 13 May 2006 - 13 May 2006

Message Share Topic Printable Version Google Delicious Digg StumbleUpon Windows Live Yahoo Bookmarks reddit Facebook MySpace Newsvine Furl Topic Search Topic Options Post Reply Create New Topic

   This topic gives some pointers on using a SQL Server on a separate PC to store WhosOn data.

We recommend that you use a SQL Server instance (or SQL Server 2005 Express) on the SAME pc as WhosOn. This will give the best performance and avoids all the headaches concerning networking and security. 

We do however note that some uses want to use a SQL Server on a separate PC. If you want to do this here are some pointers:

- When creating the WhosOn DB select the PC name of the PC running the SQL Server instance. Enter the 'sa' user name and password. 
- Don't use NT Authentication unless the two PC's are part of a Windows Domain and both PC's are members of the domain with full rights to each other.
- Ensure the SQL Server allows remote connections.
- Configure the WhosOn Server service to run under a Windows user that has access to the network.
- Configure the Web Charts to use 'Impersonatation'. This is done by editing the web.config file in the C:\Program Files\WhosOnV4\WebCharts\ folder.

Add:
<identity impersonate="true"
          userName="domain\user" 
          password="password" />

To the system.web section.

This enables the web charts to run under the context of a named Windows user instead of the ASPNET user (which wont have access to the network).

See: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsent7/html/vxconimpersonation.asp

There are other factors which may still stop you using a SQL Server instance on another PC, such as firewalls, domain level security, SQL Server setup etc. Whilst we dont 'force' users to use a local SQL Server - we also cannot garentee that you can use a remote instance with WhosOn.

Thanks
Steve

Author	Message Share Topic Printable Version Google Delicious Digg StumbleUpon Windows Live Yahoo Bookmarks reddit Facebook MySpace Newsvine Furl Topic Search Topic Options Post Reply Create New Topic
Stephen Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Admin Group Joined: 21 Oct 2005 Location: Stoke on Trent Posts: 1392	Post Options Post Reply Quote Stephen Report Post Quote Reply Calendar Event: Using SQL Server On Another PC Posted: 13 May 2006 at 2:08pm
	This topic gives some pointers on using a SQL Server on a separate PC to store WhosOn data. We recommend that you use a SQL Server instance (or SQL Server 2005 Express) on the SAME pc as WhosOn. This will give the best performance and avoids all the headaches concerning networking and security. We do however note that some uses want to use a SQL Server on a separate PC. If you want to do this here are some pointers: - When creating the WhosOn DB select the PC name of the PC running the SQL Server instance. Enter the 'sa' user name and password. - Don't use NT Authentication unless the two PC's are part of a Windows Domain and both PC's are members of the domain with full rights to each other. - Ensure the SQL Server allows remote connections. - Configure the WhosOn Server service to run under a Windows user that has access to the network. - Configure the Web Charts to use 'Impersonatation'. This is done by editing the web.config file in the C:\Program Files\WhosOnV4\WebCharts\ folder. Add: <identity impersonate="true" userName="domain\user" password="password" /> To the system.web section. This enables the web charts to run under the context of a named Windows user instead of the ASPNET user (which wont have access to the network). See: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsent7/html/vxconimpersonation.asp There are other factors which may still stop you using a SQL Server instance on another PC, such as firewalls, domain level security, SQL Server setup etc. Whilst we dont 'force' users to use a local SQL Server - we also cannot garentee that you can use a remote instance with WhosOn. Thanks Steve