SQL 2008 Instance & Shared features location?

Hello is there a way to query or find out where both the Instance & Shared features location was installed?
Thanks in advanced.

Hello,
Programmatically you can search the Registry.
The following registry key has the location of shared components.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100
(where 100 is SQL version)
On the following Registry key you will find the location of the binaries.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\Setup
Value names:
SQLBinRoot (REG_SZ), SQLPath (REG_SZ), SqlProgramDir (REG_SZ)
For more information.
https://msdn.microsoft.com/en-us/library/ms143547.aspx?f=255&MSPPError=-2147217396
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Similar Messages

Upgrade of 2008 R2 SP3 stops 2008 instance

Hello,
I have a server with both SQL 2008 and SQL 2008 R2 and am in the process to update the 2008 R2 version.
So my question is as follows:
If I upgrade 2008 R2 to the newest version does this interrupt connectivity to the 2008 instance? Or is the 2008 always available through out the process fo upgrading 2008 R2?
Regards
Paul

Hi Paul,
Two different instances are not related to each other. So upgrade of your SQL 2008 R2 instance will not create any issues to your SQL 2008 instance and it will continue to run unless there is a system wide performance issue. However, if there is a server
reboot then both instances will be unavailable.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

SQL 2008 R2 SP2, CU 1 : There are no SQL Server instances or shared features that can be updated on this computer

Hi, I know this has been posted before, but I couldn't find a solution. Currently I have a SQL 2008 R2 SP2 Enterprise 2 node cluster.
I want to keep it updated, and downloaded CU 1 from here:
http://sqlserverbuilds.blogspot.com
Version from query:
Product Version       Service Pack       Edition
10.50.4033.0          SP2                    Enterprise Edition (64-bit)
When running the installation, I get the window attached.
Any clues?

As per the message you can only update your instance with a CU/KB if the build number will be above 10.52.4321.0 (which seems to be your current build) . As per
http://sqlserverbuilds.blogspot.co.uk/ you already have the latest one available for SQL Server. Hence you wont be able to install anything unless Microsoft comes up with a new CU :)
It seems this is what you already have -
http://support.microsoft.com/kb/2977319/en-us
Now opening any KB article for any CU will have this portion Eg the KB
http://support.microsoft.com/kb/2917531 has the below.
Installation and deployment
We recommend that you test hotfixes before you deploy them in a production environment.
            This cumulative package is intended to correct only the problems that are described in this article. Apply it only to systems that are experiencing these specific problems. The updates in
this package may receive additional testing. Therefore, if you are not severely affected by any of these problems, we recommend that you wait for
                  the next SQL Server 2012 service pack
      (http://support.microsoft.com/kb/2755533/            )
             that contains the hotfixes in this package.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

SQL 2012 SP2 There are no SQL Server instances or shared features that can be updated on this computer

Hi,
I have a SQL Server instance:
Microsoft SQL Server 2012 - 11.0.5058.0 (X64)
May 14 2014 18:34:29
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
I am trying to install:
SQLServer2012SP2-KB2958429-x64-ENU
On the "Select Features" screen of the setup I get an error message when I try to click next:
"There are no SQL Server Instances or shared features that can be updated on this computer."
I've checked and re-checked the release notes - pretty sure I have the right versions of everything:
https://msdn.microsoft.com/en-us/library/67cb8b3e-3d82-47f4-840d-0f12a3bff565?f=255&MSPPError=-2147217396
Any help appreciated!
Cheers
Lucas
LucasF

Hi,
I have a SQL Server instance:
Microsoft SQL Server 2012 - 11.0.5058.0 (X64)
May 14 2014 18:34:29
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
I am trying to i
LucasF
Your SQL Server 2012 is already at SP2 see version number 11.0.5058 this corresponds to SP2. So when you run the setup it says there is nothing to upgrade
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

SQL 2008 R2 error: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified

after some year work with SQL server 2005,i decide change to SQL server 2008 R2.
When i completed install SQL 2008 R2,i can't connected to SQL server due to this following error
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (.Net SqlClient Data Provider)
And when i click to technical details,i take some thing like this
===================================
Cannot connect to HUY-PC\SQLEXPRESS.
===================================
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
Error Number: -1
Severity: 20
State: 0
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
Please!!!Some body help me solve this problem(except format my computer),i really really need your advice.

Hi huydaibang,
The older version SQL Server 2005 could be installed with SQL Server 2008 R2 side-by-side. It could not be the problem.
The reason that we get this error message is the client stack could not receive SSRP response UDP packet from SQL Browser.
Here are the steps:
1) Make sure your server name is correct, e.g., no typo on the name.
2) Make sure your instance name is correct and there is actually such an instance on your target machine.
3) Make sure the server machine is reachable, e.g, DNS can be resolve correctly, you are able to ping the server (not always true).
4) Make sure SQL Browser service is running on the server.
5) If firewall is enabled on the server, you need to put sqlbrowser.exe and/or UDP port 1434 into exception.
For more information, please refer to
http://blogs.msdn.com/b/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx.
Thanks,
Maggie
Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.

Lync 2013: SQL instance - Shared or Not Shared !?

I'll keep this straight to the point... I'm implementing Lync 2013 at my company and we stumbled on one SQL Cluster situation that's causing some questions on the DBA team.
So the situation is....
Background:
We currently have a two node SQL 2008 R2 (SP2) Cluster with two instances in it that are shared for other applications.
Question:
Is it recommended by Microsoft (or any Lync Expert at all) to use one of these instances for Lync 2013 databases, or should it be a separated instance to host Lync 2013 Databases?
Note: If to be created the new instance, that instance will be living in the same cluster.
Thank you all in advance for comments on this.

Thanks to both for the replies. It does help me thinking about the subject.
I've meanwhile opened an advisory case with MS to check what they say about it. (I'm posting the results afterwards of course to share their advice)
I agree with both of you, and in fact I don't really like the idea of having a shared instance for Lync 2013 with other products (specially one of them that's in there that is Sharepoint 2013). I'm quite curious on knowing how will the instance behave once
Sharepoint 2013 decides to "eat up" all the resources...
I think that having the separated instance adds at least 2 very good (and important values) that is:
1 - Security (at the instance level.. no unwanted sysadmin's - we have persistent chat by some God forsaken reason... though I don't like the idea that a DBA with the right knowledge to read our C*O's chat's going around...)
2 - Resource assignment control (better memory control, possibility of "shifting" the instance to another place if necessary + if someone "brings down" the shared instance for any reason, lync can continue to function)
The IO concern regarding lots of SQLServer.exe running around, it's also a valid concern in my opinion, though at IO level is basically the same story because what matters is the DB file read-write operations that are ongoing and that will consume the same
resources either you're in a dedicated instance or separated one...
Still our DBA brings up the fact that we need to use a shared instance for everything and he wants me to put Lync all together with the other DB's (Sharepoint 2013 included...).
What are your thoughts about this?
Thanks once again for your time and comments.

How to add a new instance to a 2 node SQL 2008 R2 Cluster under the same networkname

Hello All,
I'm fairly new to sql and have just deployed a new 2 node SQL 2008 R2 cluster.
During installation, I created a networkname SQLCLU and a named instance I01.
I now would like to add another Instance (I02) under the same networkname.
What is the proper procedure to do this?
I don't believe that I should do this using the action: "New SQL Server failover cluster" from the setup menu, but rather using the action "New Installation or add features to an existing installation"
With the second option, I'm however not sure how I should make this instance clustered..
Should I also execute the "New Installation or add features to an existing installation" action on the 2nd node in the cluster?
Many thanks for your advice!
Filip

You cannot use the same network name for 2 instances. You need to use a different network name for the second instance I02
A failover cluster instance contains:
A combination of one or more disks in a Microsoft Cluster Service (MSCS) cluster group, also known as a resource group. Each resource group can contain at most one instance of SQL Server.
A network name for the failover cluster instance.
One or more IP addresses assigned to the failover cluster instance.
One instance of SQL Server that includes SQL Server, SQL Server Agent, the Full-text Search (FTS) service, and Replication. You can install a failover cluster with SQL Server only, Analysis Services
only, or SQL Server and Analysis Services
http://msdn.microsoft.com/en-in/library/ms179410(v=sql.105).aspx

When installing SQL Server is there a benefit to overriding the defaults for the Shared Feature Directory?

When installing SQL Server under feature selection you are given the option to change the Shared feature directories. When you choose to change from the default OS drive it seems that the installation
process still installs a large amount of files on the OS drive and then additional files under a similar drive structure on the alternative drive. Is there any real benefit to changing the default location?
Additional is there benefit to changing the default location for the installed features, database engine etc. We are trying to create some clean templates that we can bring up in our production
environment so we are provisioning separate drives for data, logs, backups, tempdbs but as we use the prepare image it seems like splitting the installation of sql server into two separate locations to safe minimally on file space seems counterproductive.
I have searched for best practices and this area seems glossed over in most articles, I found a few that indicate later installation of features on a machine that use a non-standard shared component
drive has caused issues. I would like to know there are benefits to taking such actions.
Thanks in advance,
Dirk

Hello,
The best reason I can think about installing SQL Server binaries on another drive different than the system drive is the
fact the page file (pagefile.sys) is located on the system drive by default. The more I/O I can prevent happening on that drive the better for the performance of operating system.
SQL Server still installs some binaries on the system drive anyway, and creating a partition for SQL Server binaries alone
may seem like a waste.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Upgrade existing instance of SQL 2008(SP4) to SQL2014 errors

Currently trying to upgrade an existing SQL 2008(SP4) instance to SQL 2014 and getting the following errors. I'm fairly new to SQL and struggling a little to figure out what the issue might be. Thanks for any advice on this.
Action required:
Use the following information to resolve the error, and then try the setup process again.
Feature failure reason:
An error occurred during the setup process of the feature.
Error details:
§ Error installing SQL Server Database Engine Services Instance Features
There was an error attempting to remove the configuration of the product which prevents any other action from occuring.
The current configuration of the product is being cancelled as a result.
Error code: 25012
Log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150502_090151\sql_engine_core_inst_Cpu64_1.log
Visit
http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sql_engine_core_inst.msi%40Sqlmsirc_NotifyFeatureStates_64%4025012 to get help on troubleshooting.
§ Error installing SQL Server Database Engine Services Instance Features
Exception has been thrown by the target of an invocation.
Error code: 0x80131604
Visit
http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x90F5BF4F%400xDC80C325&EvtType=0x90F5BF4F%400xDC80C325 to get help on troubleshooting.
§ Error installing SQL Server Database Engine Services Instance Features
The document specified by its root path '/Extension/Agent/AgentPreviousRegPath' does not exist in data store.
Error code: 0x84B20001
Visit
http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x9490803B%400xF762992B%401202%401&EvtType=0x9490803B%400xF762992B%401202%401 to get help
on troubleshooting.

Log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150502_090151\sql_engine_core_inst_Cpu64_1.log
First you should check that mentioned log file to get more informations about the issue.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Cannot see new SQL 2008 R2 Express instance on Small Business Server 2011!

Hi,
As it is stated on the subject line, I'm having a problem after I did a new install of SQL 2008 R2 Express and put a new instance on SBS 2011.
I'm developing a new program using SQL 2008 in C# and VB.Net. I have SQL 2008 R2 Express installed on my computer called "MSQL8R2EDATA" on my PC. Now I need to deploy it on SBS 2011 so I can do some testing on other workstations.
I'm currently running Windows 7, 64 bit, and it's named STEVE-PC. The SBS 2011 is named SERVER1, and it's 64 bit as well.
After installation on SERVER1 (SBS 2011), I then fired up SQL Server Configuration Manager and enabled Named Pipes, TCP/IP, and VIA.
After I've completed the SQL Configuration on SERVER1, I went back on my PC (STEVE-PC) and I tried to use Management Studio to connect to the new instance MSQL8R2EDATA on SBS 2011, only problem is, I only see the computer name, not the new instance
I've installed.
Back on SBS 2011 (SERVER1), I've verified that all the protocols are enabled, and the SQL Server Browser is automatically loaded and currently running, as well the MSQL8R2EDATA instance is automatically loaded and running, yet I still cannot see
it from my PC (STEVE-PC). I even switched from dynamic ports to a static port of 64719 (that was what the MSQL8R2EDATA was listening on that port when it was dynamic), and then added new rules to the Windows Firewall for program of the SQLSERVR.EXE, and
for UDP and TCP for port 64719 to "Allow All Connections" for Domain, Private, and Public; yet I still cannot connect SERVER1\MSQL8R2EDATA. I even disabled the firewall and then trying to connect once again to SBS 2001 and it still fails.
In case you're wondering, I left it on port 64719 since there are other active SQL Servers on SBS 2011 (SharePoint, SBSMonitoring, and ACT7).
Interestingly, when I run Management Studio on SBS 2011, I can see STEVE-PC\MSQL8R2EDATA and I'm able to log in and connect to it.
So what's going on here?!? Why am I able to connect to STEVE-PC which is Windows 7 64 from SBS 2011 (SERVER1), but I cannot connect from my computer to that instance on SBS 2011??
I really could use some big time help on this.
EDIT: Sorry for the confusion, but on the Windows Firewall (WF.msc), I did add new rules for incoming connections on:
Program incoming connections to SQLSERVR.EXE
TCP Port 64719
UDP Port 64719
EDIT: To further assist, I have Management Studio installed on the SBS 2011, and I can locally log in and connect to the MSQL8R2DATA on SERVER1 with success. I even tried tcp:SERVER1\MSQL8R2DATA and again it is successful log-in and connection.
Thanks in advance!
Steve

Hi,
Thanks for the response, but I have a question:
Installing SQL Express or SQL Server is not recommended on SBS
2011 because it is a DC, however technically it will work.
I'm a newbie when it comes to SBS 2011 and I'm taking a crash course on the subject. Can you explain to me what you mean by "DC"? Also, why
isn't recommended to install a new instance on SBS 2011?
As I also stated, I've added "New Rules" to the Windows Firewall to allow incoming connections on port 64719 for both TCP and UDP, and I also allowed incoming connections for SQLSERVR.EXE but no joy to connect to the SERVER1\MSQL8R2EDATA.
And yes, I can log-in and connect locally on SERVER1 using Management Studio with success. I even used tcp:SERVER1\MSQL8R2EDATA with the same success. It's my workstation STEVE-PC that fails. If that fails, then the rest of the workstations are going to fail.
Are you suggesting that I put the SQL Server 2008 Express on another workstation and just allow to to be
accessed that way?

Master Data Services not available under shared feature while installing SQL server 2012

Hi,
I am trying to install Master Data Services but do not see the option to select MDS under the shared features when going through the SQL server 2012 installation. I have the SQL server 2012 SP1 (64 bit) install files. I have also installed SP2. I havent
found anything online about the issue.
Can someone please advise?
I have a screenshot of the installation screen which I will attach as soon as I am able to get my account verified. Thanks!

Hi Revees,
This might be a very naïve and also out of the original scope of the thread question.
We are thinking of going with the developer edition. We have 2/3 developers and some other testers and business users.
1) I understand that we need a developer license for each developer. But would we need a license for the business user. Can they have a sort of read access to the dbs?
2) If a developer has MSDN subscription, Would they need to purchase the license too assuming we purchase the developer edition of the software (and not download it using the MSDN subscription)?
Thanks for your assistance!

MS SQL 2008 R2 Named instance: Login failed. Microsoft SQL server, Error: 18452) - Tryig to access using the FQDN assigned for the backup network card.

Hi,
I have a windows 2008 R2 Enterprise servers with standalone MS-SQL 2008 R2 named instance. The server is having two networks, once production and the second for backup. The server FQDN is resolving to the production IP. The backup NIC
DNS dynamic update is disabled and an "A" record is registered with the dns. While trying to connect to the instance using the management studio:
Successfuly able to connect using the instance name, the production hostname, production IP and backup IP.
but while trying to connect to the insance using the backup hostname getting the below error:
"Login failed. The login is an untrusted domain and cannot be used with windows authentication. (Microsoft SQL server, Error: 18452) "
This is required for the backup tool to get connected using the backup FQDN of the server.
Should I need to create a host name alias, request you to kindly assist me with the best recommedation to fix this.
http://blogs.msdn.com/b/dbrowne/archive/2012/05/21/how-to-add-a-hostname-alias-for-a-sql-server-instance.aspx

Hi,
It might be a kerberos issue. Check that there are valid SPN's registered using the setspn utility - http://technet.microsoft.com/en-us/library/cc731241.aspx
Thanks, Andrew
My blog...

ADMIRAL database on SQL 2008 R2 Named Instance

Hi,
we are running TES 6.1.0.133 (test Master) upon a remote SQL 2005 SP4 named instance database, all is right.
I need to move the ADMIRAL database to an SQL 2008 R2 SP1 named instance.
What JDBC, JRE and connection string do I need to succeed ?
The versions are JRE 1.6.0.30, Microsoft JDBC 4.0.
thank in advance you for your experience,
Frederic

You should probably ask Cisco to help you through this they can likely provide you with an updated document and jar file
You will need to update your master.props settings.
You will need potentially need a new jar
Perform on a maintenance weekend with a maximum amount of recovery time
I have a Cisco doc and Zip files from 2010 when we did this but it is likely a different JAR that you would want to apply now.
What I would think are the Sequence of events (disclaimer Cisco would be best source of sequence, order, etc)
set system queue to zero
close all client sessions
stop master services
kill all connections to Admiral database
backup admiral database
set database offline and rename
Restore admiral database backup to new target SQL server 2008 instances
Creare a backup of master.props
Apply Jar to update master / SQL scripts (if supplied by Cisco)
Update master.props with new settings
JdbcURL=jdbc:sqlserver://:;selectMethod=cursor;databaseName=Admiral (or Admiral DB name)
There could be other setting that may also need to chance
Start Tidal Master make sure it is running
Connect Client
Verify Connections
Turn on System Queue slowly ramp up from a few to your standard level

Cannot find SQL Server 2008 instance

I have installed SQL server 2008 Developer edition on my laptop. When I open SSMS I cannot find the installed instance under the Server Name group and When I choose the Browse More option and go to Database engine, the instance name does not show up. Will
appreciate any suggestions.
Thanks
akoranteng

>>I see two instances of SQL Server 2008 when i issue the commands you suggested to me
I don't why you have two instances, may be you installed two different instances.
I think local servers list is obtained by reading the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server \Instance Names\SQL
Sometimes (don't know why may it is SQL browser service or something else messed up) you don't see a locally installed instance on the drop down list. Just
type in the instance name manually inside the textbox for server name and you should be able to connect

BPC 70 SP4 and SQL 2008 Feature Pack

Is the SQL 2008 Feature Pack required in a BPC 70 SP4 installation with SQL 2008? It is listed as a prerequisite, but our DBA's would prefer that it not be installed. My understanding is that this is needed for backward compatability. Thre are notes related to this for SP3, but nothing for SP4.

Hi John,
I just checked it and you don't need all feature pack.
Just install Microsoft SQL Server 2005 Backward Compatibility Components on Microsoft SQL Server 2008 Feature Pack.
This is for executing custom packages that was created in SQL2005.
I hope it will help you.
James Lim.

SQL 2008 Instance & Shared features location?

Similar Messages

Maybe you are looking for