Change SQL server instance collation after Sharepoint installation

Installed Sharepoint 2013 with the SQL Server 2012 db instance using the default collation Latin1_General_CI_AS. SQL is just used for Sharepoint 2013. the system is not released yet for production Run the installation and configurations and database
attach for all content databases. all content dbs were created by SP with proper collation Latin1_General_CI_AS_KS_WS, as well as search, UP and all service applications.
Would like to change the SQL collation for the instance to Latin1_General_CI_AS_KS_WS(as
https://support.microsoft.com/en-us/kb/2008668) . Steps that I see:
1. Stop IIS on SP
2. Script logins
3. recreate instance collation
setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=<Name> /SQLSYSADMINACCOUNTS=<Sysadmins> /SAPWD=PasswordSA /SQLCOLLATION=Latin1_General_CI_AS_KS_WS
4.recreate logins (including Sharepoint farm, portal and services service accounts) from previous scripts. Redeploy linked servers ,remote logins,endpoints, backup devices
4. attach all Sharepoint databases
5. since it is preproduction not need msdb also model can remain as recreated by setup
do you see any issue?

Hello,
Please take in consideration the steps suggested by Darren Madsen on the following resource.
http://darrenmarsden.com/post/sql-collation-settings-for-sharepoint
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Similar Messages

Sql Server 2008 - problems after incorrect installation of SSIS component

During the addition of SSIS component to an existing installation of Sql Server 2008 the setup has been made using Sql Server 2008 R2 media.
Now SSMS shows the following error during the connection to the instance :
Method not found: 'Int32.Microsoft.SqlServer.Management.Sdk.Sfc.ISfcDomain.GetLogicalVersion()'
I've tried to remove R2 components and to repair the existing 2008 installation.
At the moment 2008 R2 Native client and Setup are still present in the list of Programs and Features.
From previous comments I understand this method is in a Sql Server 2008 R2 assembly, so it seems that SSMS is running as R2 but is using 2008 libraries.
How can I correct this ?
Thanks.

Hello,
Be careful uninstalling now SQL Server 2008 R2 components. If you uninstall shared components that are SQL Server 2008
R2 components the whole SQL Server 2008 instance will be unusable. For more information about having SQL Server 2008 and SQL Server 2008 R2 installed on the same computer, please read the following article:
http://msdn.microsoft.com/en-us/library/ee210714(v=sql.105).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

How to change SQL Server security groups name after server rename?

A Windows 2003 server has been renamed from LAMDAMIRROR1A to LAMDAMIRROR2A and the following
sql has been run in SQL Server 2008 R2 on the server :
exec sp_dropserver 'LAMDAMIRROR1A'
exec sp_addserver 'LAMDAMIRROR2A','local'
However, although everything appears ok, the 5 Windows 2003 Groups (automatically created by
the SQL 2008 R2 Install) still contain 'LAMDAMIRROR1A' in their name. Does this matter ? Can the Windows Groups be just renamed (right click , rename) or will this cause problems ?
The Windows Groups are :
SQLServer2005SQLBrowserUser$LAMDAMIRROR1A
SQLServerDTSUser$LAMDAMIRROR1A
SQLServerMSSQLServerADHelperUser$LAMDAMIRROR1A
SQLServerMSSQLUser$LAMDAMIRROR1A
SQLServerSQLAgentUser$LAMDAMIRROR1A
There are also Registry entries containing the old 'LAMDAMIRROR1A' name. Does this matter ?
Should this be changed ?
eg.
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\Machines\OriginalMachineName.
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Services\Report Server\GroupPrefix.
My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\printers\Microsoft XPS
DocumentWriter\DsSpooler\serverName.
etc

Hi,
If you have executed the sp_dropserver and sp_addserver in SQL Server 2008 R2, we need to verify if you renamed the SQL Server instance successfully. You can select information from @@SERVERNAME or sys.servers to verify if the renaming operation is completely
successful in SQL Server Management Studio (SSMS). If yes, whether you change the registry entries containing the old 'LAMDAMIRROR1A' name or not, there’s no impact on SQL Server Services. For more details, please review this article:
How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server.
In addition, if you must rename the windows groups, you can just right-click the group in Computer Management/System Tools/Local Users and Groups/Groups and rename it, or you can create new groups with new names, for more details, please review this article:
Manage Local Groups. If there are some issues regards the Windows, you can post the question in the Windows Server forums at
http://social.technet.microsoft.com/Forums/windowsserver/en-US/home?category=windowsserver . It is appropriate and more experts will assist you.
Thanks
Lydia Zhang

Cannot start SQL Server (SQLEXPRESS) 2012 after changes to IPALL

I made a change to Protocols for SQLEXPRESS, TCP/IP, IP Addresses, IPALL and now receive an error when attempting to restart SQL Server. Can anyone help with this? Is it possible to restore system to prior checkpoint in order to correct
this?
Please help.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0xd, status code 0x10. Reason: Unable to retrieve registry settings from TCP/IP protocol's 'IPAll' configuration key. The data is invalid.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0xd, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The data is invalid.
Error: 17826, Severity: 18, State: 3.
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
Error: 17120, Severity: 16, State: 1.
SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Hi Chuck,
The Error "TDSSNIClient initialization failed with error 0xd, status code 0x10. Reason: Unable to retrieve registry settings from TCP/IP protocol's 'IPAll' configuration key. The data is invalid" Suggest that there is a problem with the data stored in one
of the registry keys related to SQL server start up. Although the information provided is not sufficient to pinpoint to a specific issues. Still try the following step open the SQL server configuration manager
Select SQL server Network Configuration->Protocols for <Your SQLExpress instance Name>
On the right side double click TCP/IP.Select IPAddresses Tab. Scroll the way down till you file IPALL
Make sure that there are only a valid TCP/IP Port number is present. Even the leading or trailing whitespaces could make a difference here. Once you have verified that above two conditions are met. Try starting the SQL server instance.
Also make sure that the TCP/IP port is not being used by any other program.
You can run the command netstat -aon on the command prompt to see the list of ports being used. Make sure that the port you have specified for SQL server is not listed under the TCP protocols.
Hope this helps.
Regards
Sathish S N
Please click the Mark as answer button and vote as helpful if this reply solves your problem

SCOM 2012 Installation does not show the SQL Server Instance for reporting services

I have an issue when I try to install SCOM 2012 with the Reporting Server feature, so in the step that I have to select a SQL Server Instance I cannot do that, because as you can see in the picture no one option appears.
In my scenario I have a DCSERVER, SQLSERVER2008 R2, SCCMSERVER 2012 and in other server I are trying to install SCOM 2012. I are trying to use the same SQLSERVER to SCOM 2012.
Should I do other procedure on SQL Server before to continue? I will apreciate someone could say me what I need to do to resolve this issue.
Regards,
Paul Mendoza.

Hi Paul
Can you confirm that SQL Reporting Services is installed on the server that you are doing the install.
For a lab environment where you have SCOM Management Server, Web Server on one server and SQL Server on another you need to:
- run setup on the SCOM Server and choose NOT to install reporting. The install here will create the OperationsManager database and OperationsManagerDW (reporting) database.
- run setup on the SQL Server where SQL Reporting Services is installed. Then choose to install reporting. You should then see the SQL Reporting Services instance on the above window which is blank in your screenshot.
Take note of the warning in that window - SCOM uses its own role based security within SQL Reporting Services and this can break other reporting. E.g. you can't install SCOM and SCSM reporting (SQL RS component) together.
Cheers
Graham
New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/

DPM failing SQL backups due to error: "the SQL Server instance refused a connection to the protection agent. (ID 30172 Details: Internal error code: 0x80990F85)

I ran across this error starting on 6/4/2011 and have been unable to find the root of the problem. In our environment, we have a DPM 2010 server dedicated to backing up all our SQL envrionment (about 45 SQL Servers total). All of the SQL
environment is backing up fine except for a SQL Cluster Application. This particular SQL Instances is part of a 6 node failover cluster with 6 SQL Instances distributed amongst them. The other 5 SQL instances in the cluster are backing
up fine; only one instance is failing. The DPM Alerts section shows this error when attempting to do a SQL backup of one of the databases on this SQL instance:
Affected area: KEN-PROD-VDB001\POSREPL1\master
Occurred since: 6/11/2011 11:00:56 PM
Description: Recovery point creation jobs for SQL Server 2008 database KEN-PROD-VDB001\POSREPL1\master on SQL Server (POSREPL1) - Store Settings.ken-prod-cl004.aarons.aaronrents.com have been failing. The number of failed recovery point creation jobs =
4.
If the datasource protected is SharePoint, then click on the Error Details to view the list of databases for which recovery point creation failed. (ID 3114)
The DPM job failed for SQL Server 2008 database KEN-PROD-VDB001\POSREPL1\master on SQL Server (POSREPL1) - Store Settings.ken-prod-cl004.aarons.aaronrents.com because the SQL Server instance refused a connection to the protection agent. (ID 30172 Details:
Internal error code: 0x80990F85)
More information
Recommended action: This can happen if the SQL Server process is overloaded, or running short of memory. Please ensure that you are able to successfully run transactions against the SQL database in question and then retry the failed job.
Create a recovery point...
Resolution: To dismiss the alert, click below
Inactivate alert
I have checked the cluster node this particular SQL instance is running on using Perfmon and the machine is nowhere near capacity on CPU, memory, network, or Disk I/O.  I have failed this SQL Application to another node in the cluster and
receive the same error (this other node has another clustered SQL application on it that is actively running as well as backing up fine). The only thing that I am aware of that has changed is that we installed SP2 for SQL 2008 about 2 weeks prior
to when the failures started to occur. However, we updated all six clustered SQL Instances at the same time and only this one is having this issue so I don't believe that caused the problem. We are running SQL 2008 SP2 (version 10.0.4000.0)
on all clustered instances along with DPM 2010 (version 3.0.7696.0) on this particular DPM server that has the issue.
One last thing, I have also noticed errors in the event log pertaining to the same SQL backups that are failing (but the time stamps are not concurrent with each backup attempt):
Log Name:      Application
Source:        MSDPM
Date:          6/13/2011 1:09:12 AM
Event ID:      4223
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      KEN-PROD-BS002.aarons.aaronrents.com
Description:
The description for Event ID 4223 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
DPM writer was unable to snapshot the replica of KEN-PROD-VDB001\POSREPL1\model. This may be due to:
1) No valid recovery points present on the replica.
2) Failure of the last express full backup job for the datasource.
3) Failure while deleting the invalid incremental recovery points on the replica.
Problem Details:
<DpmWriterEvent><__System><ID>30</ID><Seq>1833</Seq><TimeCreated>6/13/2011 5:09:12 AM</TimeCreated><Source>f:\dpmv3_rtm\private\product\tapebackup\dpswriter\vssfunctionality.cpp</Source><Line>815</Line><HasError>True</HasError></__System><DetailedCode>-2147212300</DetailedCode></DpmWriterEvent>
the message resource is present but the message is not found in the string/message table
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSDPM" />
    <EventID Qualifiers="0">4223</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-06-13T05:09:12.000000000Z" />
    <EventRecordID>68785</EventRecordID>
    <Channel>Application</Channel>
    <Computer>KEN-PROD-BS002.aarons.aaronrents.com</Computer>
    <Security />
</System>
<EventData>
    <Data>DPM writer was unable to snapshot the replica of KEN-PROD-VDB001\POSREPL1\model. This may be due to:
1) No valid recovery points present on the replica.
2) Failure of the last express full backup job for the datasource.
3) Failure while deleting the invalid incremental recovery points on the replica.
Problem Details:
<DpmWriterEvent><__System><ID>30</ID><Seq>1833</Seq><TimeCreated>6/13/2011 5:09:12 AM</TimeCreated><Source>f:\dpmv3_rtm\private\product\tapebackup\dpswriter\vssfunctionality.cpp</Source><Line>815</Line><HasError>True</HasError></__System><DetailedCode>-2147212300</DetailedCode></DpmWriterEvent>
</Data>
    <Binary>3C00440070006D005700720069007400650072004500760065006E0074003E003C005F005F00530079007300740065006D003E003C00490044003E00330030003C002F00490044003E003C005300650071003E0031003800330033003C002F005300650071003E003C00540069006D00650043007200650061007400650064003E0036002F00310033002F003200300031003100200035003A00300039003A0031003200200041004D003C002F00540069006D00650043007200650061007400650064003E003C0053006F0075007200630065003E0066003A005C00640070006D00760033005F00720074006D005C0070007200690076006100740065005C00700072006F0064007500630074005C0074006100700065006200610063006B00750070005C006400700073007700720069007400650072005C00760073007300660075006E006300740069006F006E0061006C006900740079002E006300700070003C002F0053006F0075007200630065003E003C004C0069006E0065003E003800310035003C002F004C0069006E0065003E003C004800610073004500720072006F0072003E0054007200750065003C002F004800610073004500720072006F0072003E003C002F005F005F00530079007300740065006D003E003C00440065007400610069006C006500640043006F00640065003E002D0032003100340037003200310032003300300030003C002F00440065007400610069006C006500640043006F00640065003E003C002F00440070006D005700720069007400650072004500760065006E0074003E00</Binary>
</EventData>
</Event>
Any help would be greatly appreciated!

Don't know if this helps or not, but I also noticed another peculiar issue that is derived from this problem. If I go to "Modify protection group", then expand the cluster, then expand all six nodes in the cluster, five of them show "All SQL Servers"
and allow me to expand the SQL Instance and show all databases; the one that is having a problem backing up, when I expand the node, doesn't even show that SQL exists on the node, when in fact, it does.
I would also like to add that the databases on this node that will not backup are running fine. They run hundreds of transactions daily so we know SQL itself is OK. Even though it is a busy SQL Server, there is plenty of available resources as
the SQL buffer and memory counters show the node is not under durress.

[Forum FAQ] Troubleshooting error "The specified SQL server instance is not valid" when installing SCOM reporting service

Symptom
If you have failed to install SCOM reporting service, you may encounter below error when you reinstall it:
“The specified SQL server instance is not valid”.
(Figure 1)
Figure 1.
Reason
This issue may be caused by multiple reasons, for example the reasons in Figure 1.
However, you may find that SSRS and Report Server website are configured correctly and no SSL or proxy Server is used. In these scenario, you can open the log file under path
to find the root reason:
C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\LogFiles
Later, you will find the error as below:
ERROR: Throwing Microsoft.ReportingServices.Library.ReportServerDisabledException: , Microsoft.ReportingServices.Library.ReportServerDisabledException:
The report server cannot decrypt the symmetric key that is used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content. ---> System.Runtime.InteropServices.COMException
(0x80090016): Keyset does not exist (Exception from HRESULT: 0x80090016)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSManagedCrypto.RSCrypto.ReencryptSymmetricKey(Byte[] symKeyBlob, Byte[] pPublicKeyBlob)
at Microsoft.ReportingServices.Library.ConnectionManager.<GetEncryptionKey>b__2()
--- End of inner exception stack trace ---;
Solution
According to the error message, you can delete encrypted content by following the steps below:
Open SQL Reporting Services Configuration Manager.
Select “Encryption Keys”.
Click “Delete” to delete all encrypted content. (Figure 2)
Figure 2.
After that, we can install SCOM reporting service again, after successfully install reporting service, we should see the SCOM operation console as below:
Figure 3.
In addition, you may also encounter other errors when installing SCOM reporting service, and the troubleshooting steps may be different. However, we can also check SQL reporting
service logs to find the root reason.
Here are some articles that would be helpful for SCOM reporting service installation and troubleshooting:
How to Install the Operations Manager Reporting Server
http://technet.microsoft.com/en-us/library/hh298611.aspx
Unable to install SCOM 2012 Reporting Services
http://blogs.technet.com/b/mdegre/archive/2013/05/27/unable-to-install-scom-2012-reporting-services.aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hello,
I'm afraid you must use a dedicated instance of SQL Server for each site(SCOM/SCCM). Some similar issues were disscussed on this forum:
SCCM and SCOM - SQL Server
http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/bfa14da9-4692-4c64-a107-e085c967d259
SCOM, SCCM, SQL on same server?
http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/b5373aa7-5233-4b1f-9b39-b86e481e04d5
Thanks,
Yog Li
TechNet Community Support

Setup cannot connect to the specified SQL Server instance

On a clean install domain member (Windows 2012), I am trying to setup System center 2012 VMM:
1. I installed the prerequisites as instructed during the pre-setup phase of the installation then rebooted the server (SQL Server 2012 was installed and services seem to be all started properly and SQL Configuration Manager starts as well).
2. After reboot, logged again with domain admin account and Windows update installed right away SP1 for SQL server 2012. Then I rebooted again.
3. Restarted the installation process and left default values. At the "Database configuration" step, I am leaving everything by default as well and I am getting error: "Setup cannot connect to the specified SQL Server instance. Ensure that
the server name..."
4. Tried different credentials, tried using port 1433 with no effect.
Am I missing something????
Thanks.
Benjilafouine

Definitely be sure to connect with the "ServerName\InstanceName,PortNumber". If you don't reference a port number it will try 1433 and then will connect via a dynamic port number. It is best in my opinion to always specify a specific port for each instance
to listen on in the SQL Server Configuration Manager so that you can open the fewest number of ports in the Windows firewall.

Multiple SQL Server Instances and MSDTC / AGs usage

Hello,
We are in the planning stages of migrating from SQL Server 2008R2 to 2012 to be running on Windows Server 2012, and I have a question about MSDTC, Availability Groups and multiple sql instances on a single box.
We have a couple of databases that rely on MSDTC so we know they can not participate in Availabilty Groups, but most of the other dbs we use DO NOT need MSDTC so I wondering the following:
1) Can I install two instanaces of SQL Server on a single box and have one using a local DTC, and therefore unable to use AGs, and the other instance on the same box NOT use DTC and therefor CAN use AGs?
2) If I can't do this, I assume each instance would need it's one machine. Is that correct?
Thanks
Eric

Hi Eric,
As described in this
article, for a given availability group, the availability replicas must be hosted by separate instances of SQL Server residing on different nodes of a WSFC cluster. Thus, we cannot configure a availability group for multiple SQL Server instances that reside
on a single node.
In addition, MSDTC is not supported by AlwaysON Availability Groups because
transaction atomicity/integrity cannot be guaranteed. For example, while
using a MS DTC transaction, after failover, the new principal contacts MS DTC. But MS DTC has no knowledge of the new principal server, and it terminates any transactions that are "preparing to commit," which are considered committed
in other databases. However, using Availability Groups together with DTC does not result in an unsupported SQL Server installation. For more information, please review this article:
Cross-Database Transactions Not Supported For Database Mirroring or AlwaysOn Availability Groups (SQL Server).
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

SQL Server 2005 collation type for the Discovery System?

Greetings,
The SQL Server 2005 Eval 180 day license expired on our Discovery System. I un-installed the Eval copy and installed a licensed SQL Server 2005 EE instance. I searched for the SQL Server collation, and found SAP Note 600027, which recommended Binary order for use with the 850 Multilingual Character Set as the collation.
I attached the existing databases using the script provided with the Discovery system. Started up the SAP ERP instance. I then tried to log into the ERP 300 and got a START_CALL_SICK error message. From the error message details I find, "DB CHECK Wrong Server collation. Perform SQL2005 after upgrade steps. Please see note 126973". Note 126973 seemed to refer me to note 799058. However this talks about upgrading....
It appears to me I simply chose the wrong SQL Server 2005 collation type when installing the licensed coipy of SQL Server.
What collation type should be used?
Thanks,
Jay Warling

After reviewing what I did, it appears I neglected to detach the databases before un-installing SQL Server 2005 evaluation copy.
I did stop the ERP system via the SAP MMC before un-installing but did not detach the databases.
I believe the collation is actually correct, but I am stumped as how to proceed with the START_CALL_SICK error message.
Any ideas?
Thanks,
Jay

Is it possible to have different authentication mode for SQL Server Database Engine and corresponding SQL Server instance?

Hi,
I have installed the x64 SQL Server 2008 R2 Express with default settings and run MBSA 2.3 (using default settings too). It shows three SQL Server instances: MSSQL10_50.SQLEXPRESS, SQLEXPRESS and SQLEXPRESS (32-bit). For the first, authentication
mode is Windows, for the rest two - mixed. Here https://social.msdn.microsoft.com/Forums/sqlserver/en-US/03e470dc-874d-476d-849b-c805acf5b24d/sql-mbsa-question-on-folder-permission?forum=sqlsecurity question
about such multiple instances was asked and the answer is that "MSSQL10.TEST_DB
is the instance ID for the SQL Server Database Engine of the instance, TEST_DB", so in my case, it seems that MSSQL10_50.SQLEXPRESS is the instance ID for SQL Server Database Engine of the SQLEXPRESS instance.
I have two questions:
1) How can it be that SQL Server DB Engine instance has different authentication mode than corresponding SQL Server Instance?
2) Why 32-bit instance reported although I installed only 64-bit version?
Also, this https://social.technet.microsoft.com/Forums/security/en-US/6b12c019-eaf0-402c-ab40-51d31dce968f/mbsa-23-reporting-sql-32bt-instance-is-running-in-mixed-mode-when-it-is-set-to-integrated?forum=MBSA question seems to be related to this
issue, but there is no answer :(.
Upd: Tried on clean Windows 8 installation and Windows 7 with the same result.

Because I DO NOT want the three people who will be having access to the production SQL Server to also have access to the primary host ProductionA. Since I have to allow them to RDC into the box to manage the SQL Server, I figure why not create
a separate VM for each one of them and they can RDC into those instead.
Does this make any sense?
Any tips are greatly appreciated. The main reason for doing this is because the three people who will be accessing the box, I need to isolate each one of them and at the same time keep them off of the primary ProductionA.
Thanks for your help.
M
Hello M,
Since you dont want the 3 guys to have access to Production machine A.You can install SQL Server client .By client i mean SQL server management studio(SSMS) on there local desktop and then create login for them in SQL Server.Open port on which your SQL server
is running for three of the machines so that they can connct.Now with SSMS installed on each machine each can connect to SQL server from there own machine.
I would also like you to be cautious with giving Sysadmin privilege to all three of them ,first please note down what task they would do and then decide what rights to be provided.
Your option will also work but you need to create 3 VM for that .Which is more tedious task.
Hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

I want make use of SQL Server Instance, while connecting

hi,
i have developed Code using normal conditions,Like i have not checked for SQL Server Instances, my client need to b use Instances of the SQL Server, so i need to change the code.
can any one help Regarding SQL Server Instances Connection coding.
Ex: jdbc:JSQLConnect://servername\Instance_Name
can any one help out me, it would be grate help for me,
thanks.

Read the JDBC tutorial and read the SQL Server JDBC driver documentation.
http://www.google.com/search?q=jdbc+tutorial+site:sun.com
http://www.google.com/search?q=sql+server+jdbc+driver+site:microsoft.com

Certificate empty in registry. No IP connected to SQL Server instance

Hello,
I have a SQL Server 2008r2 instance running on Windows 2008 clustered physical server. The instance starts, then fails with the following:
2014-01-02 08:41:28.82 Server      Error: 26054, Severity: 16, State: 1.
2014-01-02 08:41:28.82 Server      Could not find any IP address that this SQL Server instance depends upon. Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources
is correct, and that the IP addresses on which this SQL Server instance depends are available. Error code: 0x103.
2014-01-02 08:41:28.82 Server      Error: 17182, Severity: 16, State: 1.
2014-01-02 08:41:28.82 Server      TDSSNIClient initialization failed with error 0x103, status code 0xa. Reason: Unable to initialize the TCP/IP listener. No more data is available.
2014-01-02 08:41:28.82 Server      Error: 17182, Severity: 16, State: 1.
2014-01-02 08:41:28.82 Server      TDSSNIClient initialization failed with error 0x103, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. No more data is available.
2014-01-02 08:41:28.82 Server      Error: 17826, Severity: 18, State: 3.
2014-01-02 08:41:28.82 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2014-01-02 08:41:28.82 Server      Error: 17120, Severity: 16, State: 1.
2014-01-02 08:41:28.82 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
I found: http://support.microsoft.com/kb/2023869. I believe this will resolve my issue, however the command is not quite right. I cannot execute as in the article, but I can run certutil
-store.   There are 4 certificates in the file. Which do I use? Excerpt of file below - there are 0-3 Certificates in the file.
CA
================ Certificate 0 ================
Serial Number: 06376c00aa00648a11cfb8d4aa5c53f4 (numbers changed to protect the innocent)
Issuer: CN=Root Agency
NotBefore: 5/28/1996 4:02 PM
NotAfter: 12/31/2039 5:59 PM
Subject: CN=Root Agency
Signature matches Public Key
Root Certificate: Subject matches Issuer
Template:
Cert Hash(sha1): fe e4 49 ee 0e 39 65 a5 24 6f 00 0e 87 fd e2 a0 65 fd 98 d4 ((numbers changed to protect the innocent)
No key provider information
Cannot find the certificate and private key for decryption.
My certificate value under this registry key is empty.
Any help appreciated,
Dianne
Dianne

Hello ,
Please check below link
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/cc39d8cb-bc64-48e6-8368-24886481dd4f/sql-server-cluster-sql-server-resource-not-coming-online?forum=sqlsetupandupgrade
http://blogs.technet.com/b/taraj/archive/2009/01/07/could-not-find-any-ip-address-that-this-sql-server-instance-depends-upon.aspx
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Connect from SQL Developer to several SQL Server instances

Our SQL Server has more than one instance, but I see only one instance of them trying to connect from SQL Developer 1.2 to SQL Server. How I should define the connection information? Usually we connect to SQL Server by <hostname>/<instancename> and then the database name as CatalogName (Initial Catalog). In the Oracle world you can give only the hostname, a port number and the database name. How I can convince the SQL Developer to choose one of our SQL Server instances?

Hi user627927,
Bug/Enhancement request already logged.
We have not got this configuration in house, two people have suggested workarounds but we are unable to test them for now. The last person was unable to get these workarounds working, and we have not confirmed them in house.
Can you get the instances connected through two different ports?
It would be great if you could confirm either workaround.
-Turloch
*1/Suggestion 1 change the URL through SQLDevelopers xml connection store.
*2/Overload the port field to have instance in the eventual url
*1/Suggestion 1 change the url through SQLDevelopers xml connection store.
[Note it is probably simpler to connect a dummy connection through the connection dialog as usual save it (you cannot connect) and then add the instance information rather than having to enter all the information in an unmanaged way.]
Hi Naveen,
I had same problem as you and user579801. I managed to resolve it by doing the following.
1. Locate the file called IDEConnections.xml in the folder where you have installed SQL Developer (eg. c:\sql developer\sqldeveloper\system\oracle.jdeveloper.db.connection.11.1.1.0.11.42.62).
2. Create the following entries under <connections> tag.
<connection>
<URL>jdbc:jtds:sqlserver://\\.\;namedPipe=true;instance=SQLDBNam;</URL>
<ConnectionName>SQLServer</ConnectionName>
<user>SQLUser</user>
<ConnectionType>JDBC</ConnectionType>
<DeployPassword>false</DeployPassword>
<JdbcDriver>net.sourceforge.jtds.jdbc.Driver</JdbcDriver>
<RaptorConnectionType>Microsoft SQL Server</RaptorConnectionType>
</connection>
3. Save the file; Close and re-open the SQL Developer and try connecting.
Hope this will solve your problem. Good luck.
Regards
Raja
*2/Overload the port field to have instance in the eventual url
This took some figuring out but I cracked it in the end....
SQLServer tab:
Hostname: <servername>
Port: <portnumber>/<databasename>;instance=<instancename>
so for me the Port field looks like this: 1433/Gaffa;instance=SQL01
That should now connect to a named instance SQL Server.
Paul Fairhurst

Change sql server 2014 server name

Hi
This works on sql 2008 r2, but not on sql server 2014
sp_dropserver 'old_server'
Msg 15015, Level 16, State 1, Procedure sp_dropserver, Line 42
The server 'old_server' does not exist. Use sp_helpserver to show available servers.
sp_addserver 'new_server',local
Msg 15028, Level 16, State 1, Procedure sp_addserver, Line 74
The server 'new_server' already exists.

You mean you are changing server name(Host name) ? But this is only to change SQL instance name not server name.
Please paste output:
Select @@ServerName ServerName, Host_name() HostName
Follow steps from here:
http://mssqlfun.com/2014/06/30/rename-or-change-sql-server-standalone-default-instance/

Change SQL server instance collation after Sharepoint installation

Similar Messages

Maybe you are looking for