You mean the "allow remote connections" setting in management studio?
I'm guessing you dont want this. This option turns on the sp_configure 'remote access' , 1option, which is an old feature of SQL Server that pre-dates linked servers.
with a key for each protocol. eg. tcp, sm (shared memory) np (named pipes)
A value of enabled is set to 1 inside each key of tcp or np, depending on what you want enabled.
The easiest way (for me at least) is to script this with xp_regwrite which is an undocumented stored procedure, but does the job & means you can include it with your other sql server configuration scripts that run in sqlcmd/SSMS after an install is performed.
You mean the "allow remote connections" setting in management studio?
I'm guessing you dont want this. This option turns on the
sp_configure 'remote access' , 1
option, which is an old feature of SQL Server that pre-dates linked servers.What you actually want is this: How to configure SQL Server 2005 to allow remote connections (the naming convention here isn't at all confusing!)
In which case, yes there's a registry key. Assuming you only have a default instance installed, then the registry path is:
with a key for each protocol. eg. tcp, sm (shared memory) np (named pipes)
A value of enabled is set to 1 inside each key of tcp or np, depending on what you want enabled.
The easiest way (for me at least) is to script this with xp_regwrite which is an undocumented stored procedure, but does the job & means you can include it with your other sql server configuration scripts that run in sqlcmd/SSMS after an install is performed.
eg: