Alex Chang's WebLog - All Comments

re: A fix for when Visual Studio .NET is slow in starting up/opening

at2000_zm — Sat, 07 Jun 2008 13:36:55 GMT

VS can load the app very slow if you have set many breakpoints. i have come across a link that provides excellent solution to this problem. it can also be used for other purpose also.

saurabhramya.googlepages.com/save%26loadbreakpointsinvisualstudio

re: How to use Trusted Connection when SQL server and web Server are on two separate machines.

Thangavignesh — Thu, 28 Feb 2008 12:18:26 GMT

this site is very useful for me

How to use Trusted Connection when SQL server and web Server are on two separate machines.

Vincent Yang — Fri, 22 Feb 2008 03:16:33 GMT

(Ref:weblogs.asp.net/.../113866.aspx)Recently,inourconsiderationt...

Top 10 Best Practices for Production ASP.NET Applications

Kyle Beyer — Wed, 13 Feb 2008 06:05:10 GMT

In no particular order, here are the top ten things I've learned to pay attention to when dealing

re: How to use Trusted Connection when SQL server and web Server are on two separate machines.

Kirill S — Fri, 25 Jan 2008 22:33:32 GMT

Alex,

I am so glad I ran into your web page. Your advice worked for me.

I experienced only minor differences, probably because I am working on Windows 2003 server.

To get the single sign on to work I had to disable Anonymous access and check Basic Authentication check box in IIS manager. I also had to add few lines in the web.config file:

Thanks,

Kirill

re: How to use Trusted Connection when SQL server and web Server are on two separate machines.

Sudip Purkayastha — Wed, 23 Jan 2008 04:20:36 GMT

Hi all,

I am facing one typical problem. my web server and DB server (which also having IIS server) are on different PC. i have configured ASP.net password on both the PCs. Now, once i try to connect the DB on trusted connection, giving IMPERSONATION=false, i get the same error.

But if i write IMPERSONATION=true USERNAME="xyz" PASSWORD="xyz" it works fine. i am having IIS 5.6

Please help.

re: How to use Trusted Connection when SQL server and web Server are on two separate machines.

Daniel — Fri, 14 Dec 2007 12:42:11 GMT

Small point I think should be mentioned in reference to Barry's and Alex's discussion

DB Trusted Conection with IIS running under domain account context - should be perfectly fine for Intranet applications.

For publically facing Internet sites - segragation between the IIS server and the internal organisation is a must. Usually this is achieved with a DMZ. SQL Server authentication is probably easiest to use in this setup as windows authentication would require a separate DMZ domain.

For DMZ info... see en.wikipedia.org/.../Demilitarized_zone_(computing)

Using SSPI in connection strings vs. a named SQL Server user « The Pursuit of a Life

Wed, 28 Nov 2007 22:33:11 GMT

Pingback from Using SSPI in connection strings vs. a named SQL Server user « The Pursuit of a Life

re: How to use Trusted Connection when SQL server and web Server are on two separate machines.

Travis — Wed, 08 Aug 2007 20:36:26 GMT

We are looking at implementing some kind of trusted connection like this in our applications.

Which do you think is worse, using a trusted connection as described in this article, or using SQL Server accounts instead of Active Directory accounts to authenticate to the database?

re:How to use Trusted Connection when SQL server and web Server are on two separate machines.

TrackBack — Sun, 10 Apr 2005 06:20:00 GMT

^_^,Pretty Good!