CODEWITHSUNDEEP
c#sql-serverstored-proceduressqlclr
Jeffrey Bane
Jeffrey Bane

Reputation: 592

CLR stored procedure deploy to multiple SQL Server clusters

I have a CLR stored procedure I wrote and in the database connection string in the Visual Studio project it's pointing to "localhost". This works fine when I was developing on my machine.

Now it has to be deployed to multiple SQL Server cluster instances. I deployed it to one as a test and I'm a little confused as to why it works. When you're on the cluster, trying to connect a query window to "localhost" times out and that makes sense since it's a cluster. However, the CLR stored procedure works fine.

I would have thought I would have had to use the cluster instance name in Visual Studio and re-build the .dll

My question is, is the connection string from Visual Studio in a CLR stored procedure even used after you deploy it to a server?

Thanks in advance.

Upvotes: 1

Views: 395

Answers (1)

Jeffrey Bane
Jeffrey Bane

Reputation: 592

http://technet.microsoft.com/en-us/library/ms131053.aspx

Seems that's the case. "context connection=true" means in the context of the connection the CLR proc was called from and has nothing to do with the connection string in the Visual Studio project.

Upvotes: 1

Related Questions