martes, 18 de diciembre de 2012
If you've this scenario, probably it can help you.
- SQL Server has Shared Memory Protocol disabled
There is a suggestion for improve better performance in Servers with Biztalk and SQL Server.
Under certain stress conditions (such as clients accessing SQL Server from the same computer), the SQL Server Shared Memory protocol may lower BizTalk Server performance.
You can resolve this problem by disabling the use of the Shared Memory network protocol in the SQL Server Client Network Utility.
On the other hand, disabling the protocol makes all of locally format connections to be down.
o "<computer_name>\<instance_name>" for a named instance
o "(local)\<instance_name>" for a named instance
o "localhost\<instance_name>" for a named instance
o A single period "."
o ".\<instance_name>" for a named instance
- It's needed to connect with SQL Server locally.
When you connect to the Database Engine from a local client (the client application and SQL Server are on the same computer), the connection uses shared memory protocol by default, but...we've DISABLED!.
If you still need to connect locally, with Disabled Shared Memory Protocol, write np: or tcp: before:
Prefix the computer name with the protocol (for example, "np:<computer_name>" or"tcp:<computer_name>").