All geek questions in one place

Configure an instance of SQL Server as (local)

Each member of our development team has a copy of our application database that runs on the local version of SQL Server 2008 Enterprise Service Pack 1 (SP1). Everyone can access the database by specifying the name of their server and instance in their web.config file, but in order to best share the developer version of our web.config file, we standardized the process of creating connection strings using the built-in security server and setting the property (local ) This strategy works fine for most of our 64-bit Windows 7 machines, but in some cases (locally) is not recognized. We compared the settings using the SQL Server configuration manager (namely, to make sure the named pipes protocol was enabled), and we tried to set the "(local)" alias through the SQL Server Client Network Utility, but we were out of luck. What needs to be done to use (locally) in our connection chains?

+4
source share
2 answers

Trying to change the pipe name for your instance to "\. \ Pipe \ sql \ query".

This parameter can be found by starting SQL Server Configuration Manager and going to SQL Server Network Configuration> Protocols for (Instance Name) and right-clicking on Named Pipes and selecting Properties. If Named Pipes is not enabled, be sure to enable it before restarting the SQL Server service (see Comment from @NoahHeldman).

When connecting to a default instance (that is, without an instance name), SQL Server uses the default port 1433 and the default channel name is "\. \ Pipe \ sql \ query". Changing it back into alignment should (hopefully) fix it.

+10
source

Those machines in which the connection to the database as (local) does not work are likely to do so, because during the installation of the database the instance name was set to something specific, rather than the default "default instance". You can change these instance names that can solve this problem: http://coderjournal.com/2008/02/how-to-change-instance-name-of-sql-server/ .

I think this happens when you already have SQL Server Express installed and running, and then install SQL Server Developer Edition / Standard / etc .... not 100% sure though, but from what I remember, it’s maybe so,

+2
source

Source: https://habr.com/ru/post/1336022/

More articles:


All Articles