Installing SQL server 2005 on a different drive to C:
Does anyone know how to install SQL on a different drive using the SQL4SAP.VBS script. Does anyone know how to change the destination drive in the script? We have run out of space on C!
In the SDC under 'Installation and Upgrade Guides' you can find an installation guide for installing SQL Server 2005 manually. And then you can choose whatever drive is suitable for you.
Sven
Similar Messages
-
Error while installing SQL Server 2005 SP3
I have installed SQL Server 2005 Standand Edition (32-bit) on a standalone server machine running
Windows Server 2003 R2 Standard 64-bit with Service Pack 2. After installing SQL Server, when I tried installing the Service Pack 3 (as per application requirement) through local administrator account, I am repeatedly getting below error in
"C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_SqlSupport.msi.log"
SECUREREPAIR: SecureRepair Failed. Error code: 4ec4E6A3388
MSI (s) (F8:40) [16:49:33:515]:
Error 1260. Windows cannot open this program because it has been prevented by a software restriction policy.
I have checked rights on the folders and also got the anti-virus (symantec) services stopped on the server. Still no success, can anyone help.I have installed SQL Server 2005 Standand Edition (32-bit) on a standalone server machine running
Windows Server 2003 R2 Standard 64-bit with Service Pack 2. After installing SQL Server, when I tried installing the Service Pack 3 (as per application requirement) through local administrator account, I am repeatedly getting below error in
"C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_SqlSupport.msi.log"
SECUREREPAIR: SecureRepair Failed. Error code: 4ec4E6A3388
MSI (s) (F8:40) [16:49:33:515]:
Error 1260. Windows cannot open this program because it has been prevented by a software restriction policy.
I have checked rights on the folders and also got the anti-virus (symantec) services stopped on the server. Still no success, can anyone help.
Just to add: Have already referred
http://support.microsoft.com/kb/918357 -
Error 1406 while installing SQL server 2005 on windows 2003 64 bit standard
Hi Gurus,
When I am trying to install SQL SERVER 2005 on Windows Serevr 2005 i get the error code 1406
I tried using the script sql4sap.vbs. and tried to set the named instance.
please suggest
Please find the contents of the Summary.txt
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
Time : Mon Apr 14 14:51:07 2008
Machine : UKSAPTEST02
Product : .NET Framework 2.0
Product Version : 2.0.50727
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST02_.NET Framework 2.0.log
Last Action : InstallFinalize
Error String :Could not write value to key \Software\Classes\.appref-ms
Error Number : 1406
UKSAPTEST02 : There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information.
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Mon Apr 14 14:52:26 2008
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST02_Core.log
Many thanks
Sreeram
Edited by: sreeram kaki on Apr 14, 2008 6:12 PMHi Clas,
Thanks for the valuable suggestions,
I tried to install the database (sql server 2005) using the local admin password on another server which do not have the antivirus installed. I started the installation at 3:15 PM today and the installation is still in progerss
please see the log below from Summary.txt.
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
Time : Tue Apr 15 15:04:28 2008
Machine : UKSAPTEST01
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLSupport_1.log
Machine : UKSAPTEST01
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLNCLI_1.log
Machine : UKSAPTEST01
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SqlWriter_1.log
Machine : UKSAPTEST01
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_MSXML6_1.log
Machine : UKSAPTEST01
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLSupport_2.log
Machine : UKSAPTEST01
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLNCLI_2.log
Machine : UKSAPTEST01
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_BOL_1.log
Machine : UKSAPTEST01
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_MSXML6_2.log
Also see the last few lines of the log file
SQLSetup0001_UKSAPTEST01_SQL.log
Action start 17:10:43: Rollback_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
MSI (s) (C0!50) [17:10:43:815]: PROPERTY CHANGE: Deleting Rollback_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its current value is '1 0 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$UKSAPTEST01$RDE NT AUTHORITY\SYSTEM '.
Action ended 17:10:43: Rollback_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
<EndFunc Name='ScheduleActionX' Return='0' GetLastError='0'>
<Func Name='ScheduleActionX'>
<Func Name='SetCAContext'>
MSI (s) (C0!50) [17:10:43:815]: PROPERTY CHANGE: Adding Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its value is '1 1 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$UKSAPTEST01$RDE NT AUTHORITY\SYSTEM '.
MSI (s) (C0!50) [17:10:43:815]: Doing action: Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Action start 17:10:43: Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
MSI (s) (C0!50) [17:10:43:830]: PROPERTY CHANGE: Deleting Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its current value is '1 1 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$UKSAPTEST01$RDE NT AUTHORITY\SYSTEM '.
Action ended 17:10:43: Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
<EndFunc Name='ScheduleActionX' Return='0' GetLastError='0'>
<EndFunc Name='Write_sqlGroupMember' Return='0' GetLastError='0'>
PerfTime Stop: Write_sqlGroupMember : Tue Apr 15 17:10:43 2008
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (C0:F0) [17:10:43:830]: Doing action: Write_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
Action ended 17:10:43: Write_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
MSI (s) (C0:50) [17:10:43:830]: Invoking remote custom action. DLL: C:\WINDOWS.0\Installer\MSI1D8.tmp, Entrypoint: Write_sqlUserSecurity
Action start 17:10:43: Write_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
<Func Name='LaunchFunction'>
Function=Write_sqlUserSecurity
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: Write_sqlUserSecurity
PerfTime Start: Write_sqlUserSecurity : Tue Apr 15 17:10:43 2008
<Func Name='Write_sqlUserSecurity'>
<Func Name='ScheduleActionX'>
<Func Name='SetCAContext'>
MSI (s) (C0!34) [17:10:43:924]: PROPERTY CHANGE: Adding Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its value is '0 1 0 Setting User Security 50000 SQLServer2005SQLBrowserUser$UKSAPTEST01 SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeChan
MSI (s) (C0!34) [17:10:43:924]: Doing action: Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Action start 17:10:43: Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
MSI (s) (C0!34) [17:10:43:924]: PROPERTY CHANGE: Deleting Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its current value is '0 1 0 Setting User Security 50000 SQLServer2005SQLBrowserUser$UKSAPTEST01 SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$
Action ended 17:10:43: Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
<EndFunc Name='ScheduleActionX' Return='0' GetLastError='0'>
<EndFunc Name='Write_sqlUserSecurity' Return='0' GetLastError='0'>
PerfTime Stop: Write_sqlUserSecurity : Tue Apr 15 17:10:43 2008
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (C0:F0) [17:10:43:940]: Doing action: Write_sqlFileSDDL.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
Action ended 17:10:43: Write_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
MSI (s) (C0:10) [17:10:43:940]: Invoking remote custom action. DLL: C:\WINDOWS.0\Installer\MSI1D9.tmp, Entrypoint: Write_sqlFileSDDL
Action start 17:10:43: Write_sqlFileSDDL.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
<Func Name='LaunchFunction'>
Function=Write_sqlFileSDDL
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: Write_sqlFileSDDL
PerfTime Start: Write_sqlFileSDDL : Tue Apr 15 17:10:43 2008
Thanks & Regards,
Sreeram
Edited by: sreeram kaki on Apr 15, 2008 6:45 PM -
How to deploy MS Sql Server 2005 and 2008 jdbc driver
Hi SAP Guru's
Can somebody tell me how to deploy the jdbc driver of MS SQL Server 2005 and 2008 on SDM.
According to the SAP instruction we should have 3 files(mssqlserver.jar,msbase.jar,msutil.jar) but in 2005 driver file we only have 1 file i.e sqljdbc.jar so how do i deploy it .
Secondly i cannot deploy it on visual administrator as well and when i am doing the File to jdbc scenarion i am getting this error
" Accessing database connection "jdbc.sqlserver://localhost:1433;DatabaseName=Employee failed DriverManagerException. Cannot establish connection to URL jdbc.sqlserver://localhost:1433;DatabaseName=Employee SAPClassNotFoundException com.microsoft.sqlserver.jdbc.SQLServerDriver".
can somebody please upload the screen shots on mediafire or any other site so that i will solve my problem.Hello,
*OS: First of all: *
3 files (msbase.jar,mssqlserver.jar and msutility.jar )should be zipped to aii_af_jmsproviderlib.zip file only for UNIX OS.
For Windows OS only sqljdbc.jar file which in every version of JDBC driver should be zipped to aii_af_jmsproviderlib.zip.
You can deploy JDBC driver through SDM tool which mention in guide below:
New version of JDBC driver installation guiade:
External Driver Configuration for Process Integration 7.0
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60237e74-ef19-2b10-5a9b-b35cc6a28e83
Drivertool from this guide you can find at https://www.sdn.sap.com/irj/sdn/howtoguides
Then Exchange Infrastructure How-to Guides for SAP NetWeaver 2004 HYPERLINK "https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f04ce027-934d-2a10-5a8f-fa0b1ed4d88f"
How to Install and Configure External Drivers for JDBC & JMS
AdaptersHYPERLINK "https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e00262f5-934d-2a10-b99c-9bc63c2a7768"
Download attached system files (ZIP 16KB)
Any questions - let me know
BR,
Dzmitry -
Deploy JDBC driver for SQL server 2005 on PI 7.1
How to deploy JDBC driver for SQL server 2005 on PI 7.1
We are in SAP NetWeaver 7.1 Oracle 10G
Third party system is SQL server 2005
There are different JDBC versions are available to download for SQL server 2005.
I am not sure about the applicable version for the PI 7.1 SP level. Again JMS Adapter needs to be deploy along with this.
Please helpHi,
Hope this How to Guide help you.
How To Install and Configure External Drivers for the JDBC & JMS Adapters from
www.sdn.sap.com/irj/sdn/howtoguides
Regards,
Karthick.
Edited by: Karthick Srinivasan on Apr 13, 2009 4:07 PM -
SQL Server 2005 SP2 install on Vista
Hi,
I have all updates for Vista, tried to install SQL Server 2005 SP2, the following log file:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Professional (Build 6000)
Time : Wed Mar 26 12:20:54 2008
USER-PC : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
Machine : USER-PC
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLSupport_1.log
Machine : USER-PC
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLNCLI_1.log
Machine : USER-PC
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SqlWriter_1.log
Machine : USER-PC
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLSupport_2.log
Machine : USER-PC
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLNCLI_2.log
Machine : USER-PC
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQL.log
Machine : USER-PC
Product : Workstation Components, Books Online and Development Tools
Warning : Warning 28123.Warning: SQL Server Setup cannot install this feature because a different edition of this feature is already installed. For more information, see 'Version and Edition Upgrades' in SQL Server Books Online.
Machine : USER-PC
Product : Microsoft SQL Server 2005 Tools Express Edition
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_Tools.log
Setup succeeded with the installation, inspect the log file completely for status on all the components.
Time : Wed Mar 26 12:23:51 2008
==============================================================
When I try to start SQL Server it times out. SQL Server Express is running ok.
Can you help me get this started?
Thank you,
LucyThis is the previous errorlog:
2008-04-09 11:47:06.27 Server Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
Mar 23 2007 16:28:52
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Evaluation Edition on Windows NT 6.0 (Build 6000: )
2008-04-09 11:47:06.27 Server (c) 2005 Microsoft Corporation.
2008-04-09 11:47:06.27 Server All rights reserved.
2008-04-09 11:47:06.27 Server Server process ID is 240.
2008-04-09 11:47:06.27 Server Authentication mode is WINDOWS-ONLY.
2008-04-09 11:47:06.27 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2008-04-09 11:47:06.27 Server This instance of SQL Server last reported using a process ID of 4180 at 4/5/2008 11:17:36 AM (local) 4/5/2008 6:17:36 PM (UTC). This is an informational message only; no user action is required.
2008-04-09 11:47:06.27 Server Registry startup parameters:
2008-04-09 11:47:06.27 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2008-04-09 11:47:06.27 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2008-04-09 11:47:06.27 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2008-04-09 11:47:06.32 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2008-04-09 11:47:06.32 Server Detected 2 CPUs. This is an informational message; no user action is required.
2008-04-09 11:47:06.50 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2008-04-09 11:47:06.55 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2008-04-09 11:47:06.64 Server The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed transaction functionality, please start this service.
2008-04-09 11:47:06.64 Server Database mirroring has been enabled on this instance of SQL Server.
2008-04-09 11:47:06.64 spid4s Starting up database 'master'.
2008-04-09 11:47:06.80 spid4s 4 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:06.82 spid4s 0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:06.82 spid4s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:07.06 spid4s SQL Trace ID 1 was started by login "sa".
2008-04-09 11:47:07.10 spid4s Starting up database 'mssqlsystemresource'.
2008-04-09 11:47:07.13 spid4s The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2008-04-09 11:47:07.34 spid4s Server name is 'USER-PC'. This is an informational message only. No user action is required.
2008-04-09 11:47:07.34 spid9s Starting up database 'model'.
2008-04-09 11:47:07.53 spid9s Clearing tempdb database.
2008-04-09 11:47:08.11 Server A self-generated certificate was successfully loaded for encryption.
2008-04-09 11:47:08.11 Server Server is listening on [ 'any' <ipv6> 1433].
2008-04-09 11:47:08.11 Server Server is listening on [ 'any' <ipv4> 1433].
2008-04-09 11:47:08.17 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2008-04-09 11:47:08.17 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2008-04-09 11:47:08.17 Server Server is listening on [ ::1 <ipv6> 1434].
2008-04-09 11:47:09.12 spid9s Starting up database 'tempdb'.
2008-04-09 11:47:09.47 spid12s The Service Broker protocol transport is disabled or not configured.
2008-04-09 11:47:09.47 spid12s The Database Mirroring protocol transport is disabled or not configured.
2008-04-09 11:47:09.53 spid12s Service Broker manager has started.
2008-04-09 11:51:06.92 Server CPU time stamp frequency has changed from 1662000 to 199683 ticks per millisecond. The new frequency will be used.
2008-04-09 11:55:07.29 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 11:55:07.29 Server CPU time stamp frequency has changed from 199683 to 136029 ticks per millisecond. The new frequency will be used.
2008-04-09 12:23:09.84 Server CPU time stamp frequency has changed from 136029 to 586928 ticks per millisecond. The new frequency will be used.
2008-04-09 12:59:13.12 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 13:07:13.85 Server CPU time stamp frequency has changed from 586928 to 824822 ticks per millisecond. The new frequency will be used.
2008-04-09 13:47:17.50 Server CPU time stamp frequency has changed from 824822 to 140502 ticks per millisecond. The new frequency will be used.
2008-04-09 14:07:19.33 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 15:07:24.80 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 15:11:25.16 Server CPU time stamp frequency has changed from 140502 to 1413355 ticks per millisecond. The new frequency will be used.
2008-04-09 15:15:25.53 Server CPU time stamp frequency has changed from 1413355 to 161989 ticks per millisecond. The new frequency will be used.
2008-04-09 15:19:25.89 Server CPU time stamp frequency has changed from 161989 to 134822 ticks per millisecond. The new frequency will be used.
2008-04-09 16:23:31.73 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 17:23:37.20 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 18:11:41.58 Server CPU time stamp frequency has changed from 134822 to 154257 ticks per millisecond. The new frequency will be used.
2008-04-09 18:23:42.67 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 18:23:42.67 Server CPU time stamp frequency has changed from 154257 to 134721 ticks per millisecond. The new frequency will be used.
2008-04-09 18:35:43.79 Server CPU time stamp frequency has changed from 134721 to 151448 ticks per millisecond. The new frequency will be used.
2008-04-09 18:43:44.51 Server CPU time stamp frequency has changed from 151448 to 125134 ticks per millisecond. The new frequency will be used.
2008-04-09 19:15:47.35 Server CPU time stamp frequency has changed from 125134 to 182297 ticks per millisecond. The new frequency will be used.
2008-04-09 19:23:48.08 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 19:27:48.45 Server CPU time stamp frequency has changed from 182297 to 120770 ticks per millisecond. The new frequency will be used.
2008-04-09 19:47:50.27 Server CPU time stamp frequency has changed from 120770 to 1370171 ticks per millisecond. The new frequency will be used.
2008-04-09 20:07:52.10 Server CPU time stamp frequency has changed from 1370171 to 106932 ticks per millisecond. The new frequency will be used.
2008-04-09 20:23:53.56 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 20:35:54.65 Server CPU time stamp frequency has changed from 106932 to 88924 ticks per millisecond. The new frequency will be used.
2008-04-09 20:51:56.11 Server CPU time stamp frequency has changed from 88924 to 102106 ticks per millisecond. The new frequency will be used.
2008-04-09 20:59:56.84 Server CPU time stamp frequency has changed from 102106 to 118592 ticks per millisecond. The new frequency will be used. -
Deploying JDBC driver for SQL Server 2005 on PI 7.1
How to Deploy JDBC driver for SQL Server 2005 on PI 7.1 on Windows 2003 server
We are in NW PI 7.1 and third party db is sql server 05.
Found How-to Guide SAP NetWeaver u201804 but unable to find for NW PI 7.1
Can any one help me on this? (looking for guide step by step procedure)
Regards
MaheshHi,
Check these:
Re: Installing JDBC Drivers for PI 7.1
how to deploy MS Sql Server 2005 and 2008 jdbc driver
Mention of a SAP Note in the first link or refer this note [831162|https://service.sap.com/sap/support/notes/831162]
Regards,
Abhishek. -
SQL Server 2005 Enterprise Edition Install Question ?
Hi,
Greetings for the day !
Can someone please tell me if i can install SQL Server 2005 Enterprise Edition on Windows Server 2012 R2 as i have to migrate from Windows Server 2008 ?
Please Help ?
Thanks !Please refer the below link
http://support.microsoft.com/kb/2681562/en-us
Minimum SQL Server version requirements for Windows Server 2012 R2 or Windows 8.1
Before you install SQL Server on a computer that is running Windows Server 2012 R2 or Windows 8,1 you must make sure that you fulfill the following minimum requirements, as appropriate for your situation:
SQL Server 2014
SQL Server 2012
SQL Server 2008 R2
SQL Server 2008
--Prashanth -
Database sql server 2005 instalation problem.
Dear sir/mam,
I have installed sql server 2005 (server) and on another computer installed client. It installed successfully but on client side it does not seen, from where should i start it. so please send me procedure to install sql server 2005 on both side(client and server).Rajsarawat wrote:
Dear sir/mam,
I have installed sql server 2005 (server) and on another computer installed client. It installed successfully but on client side it does not seen, from where should i start it. so please send me procedure to install sql server 2005 on both side(client and server).You have to turn on network (external to your computer) access.
Under programs->sql server look for "surface" -
JDBC with Sql Server 2005 Express
Hi,
I need some help on this. I have a java web application that ran on Tomcat using sql server 2000 db. In my configuration file the driver and server url were
dbDriver="com.inet.tds.TdsDriver"
dbServerUrl="jdbc:inetdae7:ECCOLWXPSDE:1433?database=eclife"
Now this worked fine.
Now i am using Sql server 2005 express, so i changed the configurations to the following
dbDriver="com.inet.tds.TdsDriver"
dbServerUrl="jdbc:inetdae7:ECCOLWXPSDE\\SQLEXPRESS:1433?
database=eclife"
But it doesnt work. It doesnt create a connection. Gives a No Connection Exception when trying to use
connection = DriverManager.getConnection(dbServerUrl, username, password);
Please tell me what else needs to be done. Or is there a problem connecting to express via jdbc and sprinta.
Thankyou for your time
Shirantha.Both my Tomcat and Express 2005 are in the local machine. There is not networking involved. What i want to know is what is the different thing that is to be done from sql server 2000 to express 2005.
In sql server 2000, i have it like :
theDbDriver=com.inet.tds.TdsDriver
theDbServer=jdbc:inetdae7:ECCOLWXPSDE:1433?database=eclife
and this works FINE
Now i have uninstalled it and installed sql server 2005 EXPRESS, i have it like :
theDbDriver=com.inet.tds.TdsDriver
theDbServer=jdbc:inetdae7:ECCOLWXPSDE\\SQLEXPRESS:1433?database=eclife
and connection is not happening.
thanks for your time
Shirantha -
My question is what the steps do I need to take to upgrade SSRS from 2005 SP2 to SP4. The web server that host the SSRS is in 2005 SP2, and the OS is in window 2003.
Our SSRS report server and report server database are in different servers. The SSRS in the web server is in 2005 SP2 enterprise edition, the report server database is in sql server 2005 SP4 enterprise edition.
To upgrade the SSRS in web server from 2005 sp2 to sp4, do I need to backup/restore the encryption key? Nothing will be changed in the report server database. We will still pointing to the same database in the current server, all
I wanted to do is performing a inplace upgrade of SSRS from 2005 SP2 to SP4.
Any response will be greate appreciated. Thank you!
Li-hui ChenHi Lihui Chen,
According to your description, you want to install the Services Pack 4 for SQL Server. Right?
In SQL Server, Services Packs are used for fixing issues of current version product. It's not an Upgrade, you don't have to backup/restore your encryption key. You just need to download the Service Pack 4 on:
Microsoft SQL Server 2005 Service Pack 4 RTM . Please make sure you have administrative rights on the computer to install SQL Server 2005 SP4. For more information, see links below:
How to obtain the latest service pack for SQL Server 2005
List of the issues that are fixed in SQL Server 2005 Service Pack 4
SQL Server 2005 SP4, KBA 2463332, Installation Issues
If you have any question, please feel free to ask.
Best Regards,
Simon Hou -
SQL Server 2005 Dev Integration Services Fail
I've got VS2005 v.8.0.50727.867 (vsvista.050727-8600) on my 64bit Windows 7 box. I am trying to install SQL Server 2005 Integration Services on this Win7 box so I can load and edit the Win XP SSIS projects that I had on my XP box. So far I've
not been able to successfully install the Integration Services with a failed permission on the SQL**DTD.msi file.....I've copied this file locally and tried to run it and it would start but then would give permission error.
Is there an inherent incompatibility running SSIS projects in SQL Server 2005 on a 64bit Win 7 box? Worked great on my XP box.
I've been "upgrading" the SSIS projects to VS2008 since I was able to get SSIS installed. Any ideas what I need to do to get this beast to work?
TIA
HarryThanks Alberto
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Professional Service Pack 1 (Build 7601)
Time : Mon Aug 25 09:31:30 2014
DT0315 : Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features,
install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL
Server in Books Online.
DT0315 : Failed to find the ASP.Net Version Registration with Microsoft Internet Information Services (IIS).
Machine : DT0315
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_1.log
Machine : DT0315
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_1.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_1.log
Machine : DT0315
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_2.log
Machine : DT0315
Product : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_1.log
Machine : DT0315
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_2.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_2.log
Machine : DT0315
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_3.log
Machine : DT0315
Product : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_2.log
Machine : DT0315
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_3.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_3.log
Machine : DT0315
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_4.log
Machine : DT0315
Product : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_3.log
Machine : DT0315
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_4.log
Machine : DT0315
Product : Microsoft VSS Writer for SQL Server 2012
Product Version : 11.0.2100.60
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SqlWriter_1.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_4.log
Machine : DT0315
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_5.log
Machine : DT0315
Product : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_4.log
Machine : DT0315
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_5.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BOL_1.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_5.log
Machine : DT0315
Product : Integration Services
Error : Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: One or more of the components being installed are already registered as 32 bit components in the target application. You must install the 64 bit versions of the components being installed in a different COM+ application, or delete the existing
32 bit versions of the components being installed from the target COM+ application prior to attempting install of the 64 bit versions. COM+ applications cannot contain bit neutral components.
Machine : DT0315
Product : Microsoft SQL Server 2005 Integration Services (64-bit)
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_DTS.log
Last Action : InstallFinalize
Error String : Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: One or more of the components being installed are already registered as 32 bit components in the target application. You must install the 64 bit versions of the components being installed in a different COM+ application, or delete the existing
32 bit versions of the components being installed from the target COM+ application prior to attempting install of the 64 bit versions. COM+ applications cannot contain bit neutral components.
Error Number : 29549
Machine : DT0315
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLXML4_1.log
Machine : DT0315
Product : Microsoft SQL Server 2005 (64-bit)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQL.log
Machine : DT0315
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLXML4_2.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Analysis Services (64-bit)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_AS.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Notification Services (64-bit)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_NS.log
Machine : DT0315
Product : Microsoft SQL Server 2005 Tools (64-bit)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_Tools.log
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt. -
Installation of ODI with SQL Server 2005
Hi
I am trying to install ODI with MS Sql Server 2005.
I created a database in Sql Server & created a user with db_owner rights for logging into the database.
While trying to install Master Repository, i selected Sql Server with following details
Driver: com.microsoft.jdbc.sqlserver.SQLServerDriver
URL: jdbc:microsoft:sqlserver://<myhostname>:1433;SelectMethod=cursor
The repository does not get created giving error:
*com.sunopsis.core.q: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 1 (""): Data type 0x38 is unknown*
Now if i change the URL to jdbc:microsoft:sqlserver://<myhostname>:1433, the repository gets created successfully. But at the time of login into the topology manager using the same Master repository, it again prompts me the same error.
Has anyone faced the same issue?Hi,
You are using SQL server 2005 but trying to connect using the SQL server 2000 connection details you should be using
com.microsoft.sqlserver.jdbc.SQLServerDriver
jdbc:sqlserver://ServerName:1433;databaseName=DBNAME;SelectMethod=cursor
You will also need to make sure you are using the correct SQL server 2005 driver, if you are using a version of Java before 1.5 for ODI then you will need the SQL Server 2005 1.2 JDBC driver.
Cheers
John
http://john-goodwin.blogspot.com/ -
Unable to install SQL Express 2005 on W7 Pro machine
I am trying load a Toshiba Telecom application on a W7 Pro 64bit machine. The application has SQL Express 2005 embedded and will not install completely. I downloaded the SQL Express 2005 SP3 from MS and it comes up during the installation and states
that the PC does not have the proper hardware requirements and that it cannot install because of the wrong ASP file. The machine is an i7 with 16GB ram and 1.7TB hard drive. Can anyone help? I have the same application loaded on other W7 Pro machines with
no problem.Hi Patriot76,
According to your description, you fail to install SQL Server 2005 express SP3. Please help to post the complete setup error log here for analysis. By default, SQL Server setup log file locates in C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Log.
In addition, please confirm if your SQL Server is installed successfully.
For the hardware requirements, please make sure that your disk has at least 600 MB of available hard disk space. To install SQL Server 2005 express SP3 successfully, please pay attention to the points below.
1.Make sure that you have administrative rights on the computer.
2.Make sure that Microsoft .NET Framework 2.0 or later is installed. If you do not have the .NET Framework 2.0 installed, you must download and install it before you install SP3.
3.Make sure that you install 64-bit SQLEXPR.EXE based on your 64-bit operation system.
4.Make sure that you stop all applications and services that make connections before you install SP3.
Regards,
Michelle Li -
SQL Server 2005 High Availability and Disaster Recovery options
Hi, We are are working on a High Availability & Disaster Recovery Planning solution for an application database which is on SQL Server 2005. What different options have we got to implement this for SQL Server 2005 and after we have everything setup how
do we test the failover is working?
Thanks in advance.........
IoneDR : Disaster recovery is the best option for the business to minimize their data loss and downtime. The SQL server has a number of native options. But, everything is depends upon your recovery time objective RTO and recovery point objective RPO.
1. Data center disaster
Geo Clustering
2. Server(Host)/Drive (Except shared drive) disaster
Clustering
3. Database/Drive disaster
Database mirroring
Log shipping
Replication
Log shipping
Log shipping is the process of automating the full database backup and transaction log on a production server and then automatically restores them on to the secondary (standby) server.
Log shipping will work either Full or Bulk logged recovery model.
You can also configure log shipping in the single SQL instance.
The Stand by database can be either restoring or read only (standby).
The manual fail over is required to bring the database online.
Some data can be lost (15 minutes).
Peer-to-Peer Transactional Replication
Peer-to-peer transactional replication is designed for applications that might read or might modify the data in any database that participates in replication. Additionally, if any servers that host the databases are unavailable, you can modify the application
to route traffic to the remaining servers. The remaining servers contain same copies of the data.
Clustering
Clustering is a combination of one or more servers it will automatically allow one physical server to take over the tasks of another physical server that has failed. Its not a real disaster recovery solution because if the shared drive unavailable we cannot
bring the database to online.
Clustering is best option it provides a minimum downtime (like 5 minutes) and data loss in case any data center (Geo) or server failure.
Clustering needs extra hardware/server and it’s more expensive.
Database mirroring
Database mirroring introduced in 2005 onwards. Database Mirroring maintain an exact copy of a database on a different server. It has automatic fail over option and mainly helps to increase the database availability too.
Database mirroring only works FULL recovery model.
This needs two instances.
Mirror database always in restoring state.
http://msdn.microsoft.com/en-us/library/ms151196%28v=sql.90%29.aspx
http://blogs.technet.com/b/wbaer/archive/2008/04/19/high-availability-and-disaster-recovery-with-microsoft-sql-server-2005-database-mirroring-and-microsoft-sql-server-2005-log-shipping-for-microsoft-sharepoint-products-and-technologies.aspx
http://www.slideshare.net/rajib_kundu/disaster-recovery-in-sql-server
HADR Considerations
Need to Understand the business motivations and regulatory requirements that are driving the customer's HA/DR requirements. Understand how your customer categorizes the workload from an HA/DR perspective. There is likely to be an alignment between the needs
and categorization.
Check for both the recovery time objective (RTO) and the recovery point objective (RPO) for different workload categories, for both a failure within a data center (local high availability) and a total data center failure (disaster recovery). While RPO and
RTO vary for different workloads because of business, cost, or technological considerations, customers may prefer a single technical solution for ease in operations. However, a single technical solution may require trade-offs that need to be discussed with
customers so that their expectations are set appropriately.
Check and understand if there is an organizational preference for a particular HA/DR technology. Customers may have a preference because of previous experiences, established operational procedures, or simply the desire for uniformity across databases from
different vendors. Understand the motives behind a preference: A customers' preference for HA/DR may not be because of the functions and features of the HA/DR technology. For example, a customer may decide to adopt a third-party solution for DR to maintain
a single operational procedure. For this reason, using HA/DR technology provided by a SAN vendor (such as EMC SRDF) is a popular approach.
To design and adopt an HA/DR solution it is also important to understand the implications of applying maintenance to both hardware and software (including Windows security patching). Database mirroring is often adopted to minimize the service disruption
to achieve this objective.
HADR Options :
Failover clustering for HA and database mirroring for DR.
Synchronous database mirroring for HA/DR and log shipping for additional DR.
Geo-cluster for HA/DR and log shipping for additional DR.
Failover clustering for HA and storage area network (SAN)-based replication for DR.
Peer-to-peer replication for HA and DR (and reporting).
Backup & Restore ( DR)
keep your server DB backups in network location ( DR)
Always keep your sql server 2005 upto date, in case if you are not getting any official support from MS then you have to take care of any critical issues and more..
Raju Rasagounder Sr MSSQL DBA
Maybe you are looking for
-
How do I add an anniversary to contacts so it shows in calendar?
How do I add an anniversary to contacts so it shows in calendar?
-
Change layout Update form from QBE report
Is it possible to change the layout from the form that appears when i click on the update link from a QBE report? If yes: where? T.I.A.
-
Mix digital out and out in one task
Hello, is it possible to create a task that can be used for PWM output and setting of digitals outputs at the same time? I have a NI-USB 6210 that provides two counters and additional digital outputs. I have already implemented some code that generat
-
How does one integrate iPhoto/Aperture pics?
How does one integrate iPhoto/Aperture pics in iCloud Pages and Keynote when there is no longer a MEDIA BROWSER pop-up within this new update? Please advise.
-
After Updating Firefox Refuses to open yet the CPU says that it is?
Firefox will not Open at all, yet in the system tray it say that it is open. This has happened after I upgraded..