We were trying to restore our production server db backup in test server over LAN (due to space shortage on test server) . Test server hanged and did not respond for abt more than 15 hours (backup file 40 GB ) . The we restarted the server (resetting the power button) . Now it's showing the status 'Restoring' . According to me it's not doing anything (as seen in task manager workload ) . So how can I go ahead with checking the db .
Due to 'restoring' status I get following error
------------------------------------
Msg 927, Level 14, State 2, Line 1
Database 'envdb' cannot be opened. It is in the middle of a restore.
----------------------------------
I have a service that depends on SQL Server service. Basically we make sure that our service only starts after SQL server service started. Unfortunately this dependency does not ensure that database is available.
Basically I observed in Application log that SQL server reports that it started to listen on a port. And then I see that recovery process started. As I understand SQL server is not available while database is in the recovery state.
Note: I might have not used a correct terminology to describe SQL server recovery process as I don't have access to Application log with the exact message at the moment. I can verify the message if necessary.
Because SQL server service is started our service starts and attempts to connect to the database. Service fails to connect to database, because of the restoration process. Once restoration is done service connects successfully.
I observed that restoration process starts every time machine is rebooted. It only takes a few minutes to run, but it is enough to generate a number of error messages in event log about failed SQL connections.
My first question is: Is it normal for database to enter into recovery state every time machine is rebooted?
My second question is: If it is a normal operation, is there any way to detect that SQL server is truly available, so our code does not have to try retry establishing connection many times
I've 3 pc that have MS SQL 2000 database installed in it and connected to main server through merge replication. At first it run fine all the time. But now, it doesn't. It's happen when the pc have to restart every night. When i come to the office and check resplication status it return failed. I try to manually start synchronize but it failed too. I've to restart the pc all over again untill it ok. I hope some body out there can explain something to me and how to overcome the problem...
Transactional replication running via a pull subscription between a single subscriber and single publisher on Windows 2000 servers (all current service packs and patches) with SQL Server 2000.
Early on Sunday morning, the server hosting the publisher was rebooted...but SQL Server Agent failed to start fully, causing the log reader agent to not start and no alerts to trigger. Still trying to isolate the cause of the problem with SQL Server Agent, as it's been problematic to keep it up and running. For the most part, though, it's coming up properly after restarts of the service or reboots, and starting all agents/functions.
However, the snapshot agent ran a number of times pulling schema and batch copies for the articles in the replicated dataset, and the distribution agent now fails each time it runs with a reference to "not having the initial snapshot for the publication available". SQL Server Agent went down before this could complete, and I left it down until I could ascertain the best route to take...
Any chance I can circumvent having to reapply a initial snapshot of the publication db (this is a large set of data), and just apply transactions from the log since my downtime has only been about 60 hours? Or is there an agent setting, job run to reinitialize, or an inherent quality to SQL Server Agent that will demand a complete reapplication of the snapshots due to the down time?
I'm betting that the distribution agent will start moving data as soon as the snapshot agent finishes up (as I said, it has not completed yet), but I'm praying there's a way to get around this...
I have a clean SQL 2005 Ent. x64 SP1 clean with no user db's.....applied SP2 and everything showed "Success" except the Database Services (Error 29534)......
Time: 02/22/2007 08:29:50.134 KB Number: KB921896 Machine: TORCA8 OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790) Package Language: 1033 (ENU) Package Platform: x64 Package SP Level: 2 Package Version: 3042 Command-line parameters specified: Cluster Installation: No
********************************************************************************** Prerequisites Check & Status SQLSupport: Passed
********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID
********************************************************************************** Product Installation Status Product : Setup Support Files Product Version (Previous): 2047 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlSupport.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Database Services (MSSQLSERVER) Product Version (Previous): 2047 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 29534 Error Description : MSP Error: 29534 Service 'MSSQLSERVER' could not be started. Verify that you have sufficient privileges to start system services. The error code is (1067) The process terminated unexpectedly.
---------------------------------------------------------------------------------- Product : Analysis Services (MSSQLSERVER) Product Version (Previous): 2047 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixOLAP9_Hotfix_KB921896_sqlrun_as.msp.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Reporting Services (MSSQLSERVER) Product Version (Previous): 2047 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRS9_Hotfix_KB921896_sqlrun_rs.msp.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Notification Services Product Version (Previous): 2047 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixNS9_Hotfix_KB921896_sqlrun_ns.msp.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Integration Services Product Version (Previous): 2047 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixDTS9_Hotfix_KB921896_sqlrun_dts.msp.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : SQL Server Native Client Product Version (Previous): 2047 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_sqlncli.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Client Components Product Version (Previous): 2047 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : MSXML 6.0 Parser Product Version (Previous): 3890 Product Version (Final) : 6.10.1129.0 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_msxml6.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : SQLXML4 Product Version (Previous): 2047 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_sqlxml4.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Backward Compatibility Product Version (Previous): 1704 Product Version (Final) : 2004 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SQLServer2005_BC.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Microsoft SQL Server VSS Writer Product Version (Previous): 2047 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlWriter.msi.log Error Number : 0 Error Description : ----------------------------------------------------------------------------------
********************************************************************************** Summary One or more products failed to install, see above for details Exit Code Returned: 29534
Now SQL Server service won't restart.....
2007-02-22 10:16:31.28 Server Microsoft SQL Server 2005 - 9.00.3042.00 (X64) Feb 10 2007 00:59:02 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)
2007-02-22 10:16:31.28 Server (c) 2005 Microsoft Corporation. 2007-02-22 10:16:31.28 Server All rights reserved. 2007-02-22 10:16:31.28 Server Server process ID is 2056. 2007-02-22 10:16:31.28 Server Authentication mode is MIXED. 2007-02-22 10:16:31.28 Server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'. 2007-02-22 10:16:31.28 Server This instance of SQL Server last reported using a process ID of 576 at 2/22/2007 10:16:15 AM (local) 2/22/2007 3:16:15 PM (UTC). This is an informational message only; no user action is required. 2007-02-22 10:16:31.28 Server Registry startup parameters: 2007-02-22 10:16:31.28 Server -d E:SQLDatamaster.mdf 2007-02-22 10:16:31.28 Server -e C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG 2007-02-22 10:16:31.28 Server -l F:SQLLogsmastlog.ldf 2007-02-22 10:16:31.28 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2007-02-22 10:16:31.28 Server Detected 4 CPUs. This is an informational message; no user action is required. 2007-02-22 10:16:31.28 Server Cannot use Large Page Extensions: lock memory privilege was not granted. 2007-02-22 10:16:31.40 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. 2007-02-22 10:16:31.42 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. 2007-02-22 10:16:31.50 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 36200, committed (KB): 104760, memory utilization: 34%. 2007-02-22 10:16:33.45 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. 2007-02-22 10:16:33.45 Server Database mirroring has been enabled on this instance of SQL Server. 2007-02-22 10:16:33.47 spid5s Starting up database 'master'. 2007-02-22 10:16:33.47 spid5s SQL Trace ID 1 was started by login "sa". 2007-02-22 10:16:33.48 spid5s Starting up database 'mssqlsystemresource'. 2007-02-22 10:16:33.48 spid5s The resource database build version is 9.00.3042. This is an informational message only. No user action is required. 2007-02-22 10:16:33.48 spid5s Error: 5173, Severity: 16, State: 1. 2007-02-22 10:16:33.48 spid5s One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup. 2007-02-22 10:16:33.48 spid5s Error: 5173, Severity: 16, State: 1. 2007-02-22 10:16:33.48 spid5s One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup. 2007-02-22 10:16:33.48 spid5s Log file 'F:SQLLogsmssqlsystemresource.ldf' does not match the primary file. It may be from a different database or the log may have been rebuilt previously. 2007-02-22 10:16:33.48 spid5s The log cannot be rebuilt when the primary file is read-only. 2007-02-22 10:16:33.48 spid5s Error: 945, Severity: 14, State: 2. 2007-02-22 10:16:33.48 spid5s Database 'mssqlsystemresource' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. 2007-02-22 10:16:33.48 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
Tried reinstalling SP 2 in quiet mode using sapwd parameter.....now everything is showing the correct SP2 version but SQL Server Service won't start.......anyone????????
Every so often I get an error when I pull up an ASP.NET 2.0 site using SQL Express. It tells me that the login failed. If I go into the server's administrative tools > services and restart SQL Express and then refresh the site, it works just fine. Is this some sort of bug or memory issue? Does the application need to connect every so often or end up falling out somewhere?
I asked this question before but never received a decent answer. When a restore fails, what are the steps to re-start the restore? This should be a very common issue and for the life of me I have been unable to find it in BOL or the MS site! Please let me in on the secret!!
Hi I have problem when trying to resotre my DB from sql server 2000 to sql server 2005. You have to know also that my DB witch i want to restore with sql server 2005 maded with sql server 2000 and the message shown with attached pictures show the message detailes http://www.arabmoheet.net/forum/Members_Upload_Pics/1/sqlerror.JPG
Hi, I am trying to restore a production copy. I have only the .bak file with me. While restoring, i m facing the following error. can u please help me... thanks in advance.
"MODIFY FILE encountered operating system error 112(There is not enough space on the disk.) while attempting to expand the physical file."
I have placed the data files(52GB) in D: drive(140GB free space) and transaction log file(100GB) in F: drive(465GB free space). Still i am facing this error...
Hi, i need help about restore a DB I did a backup of a database using SQL Server Management Studio, but when i try to restore my database now, i get this error:
TITLE: Microsoft SQL Server Management Studio ------------------------------
Restore failed for Server 'Athenas'. (Microsoft.SqlServer.Smo)
System.Data.SqlClient.SqlError: The media set has 2 media families but only 1 are provided. All members must be provided. (Microsoft.SqlServer.Smo)
What do i doing so bad?? Thanks for ur opinions and help. Regards ------------------------------------------
Hi all, I have SQL server 2005 enterprise edition on windows server 2003 machine. when i took the back of the database from this sytem and try to restore the backup on SQL server 2005 R2 enterprise edition on client machine. it is giving me following error
" Restore failed for Server '10.112.12.229'. (Microsoft.SqlServer.Smo)
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: The operating system returned the error '5(Access is denied.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFX_Global_backup_200805141500.mdf'. (Microsoft.SqlServer.Smo)
"
Please tell what is the error about? Can it be possible to restore a back up of different operating system machine to other ?
I am moving my data base from one computer to a new one. I placed the .bak file in the backup folder on the new computer (Windows Vista). I keep getting these errors I have checked the security settings and my user account has full privledges. I added my windows login to the SQL Administrators as well.
Here is the error msg.: TITLE: Microsoft SQL Server Management Studio Express ------------------------------
Restore failed for Server 'laptopsqlexpress'. (Microsoft.SqlServer.Express.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476
System.Data.SqlClient.SqlError: The operating system returned the error '5(Access is denied.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLPRM - 6009757.mdf'. (Microsoft.SqlServer.Express.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&LinkId=20476
------------------------------ BUTTONS:
OK ------------------------------ What am I missing?
I have seen this before. A 2000 restore fails, leaving the database thinking it is being restored but the restore job failed and errors when it is restarted. EM is clueless. I believe there is a proc to reset some flag. Can you share it with me???
System.Data.SqlClient.SqlError: The operating system returned the error '5(Access is denied.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLAlamoDB.mdf'. (Microsoft.SqlServer.Express.Smo)
--------------------------------
Hi,
I got this error while trying to restore my database (which was running on SQL Server 2005 Express Edition) onto another machine's SQL Server 2005 Express Edition.
I got this system error log in the event viewer every time I start the SQL Server cluster resource:
The Microsoft Clustering Service failed restore a registry key for resource SQL Server when it was brought online. This error code was 2. Some changes may be lost.
Even though the SQL seems to be working fine now, I won't know if something drastic will happen later. :confused:
Searching the Internet for resolution, I saw this article. The Microsoft Knowledge Base Article - 307469 (http://support.microsoft.com/default.aspx?kbid=307469) requires using the Windows Server 2003 ClusterRecover utility to reset the server cluster check points.
I've not tried it because I don't know if this is the correct solution or if it will work or not.
Can I even solve the error without using the above utility? I also cannot afford to reinstall the clustering or SQL server. :mad:
I'm working on SQL 2012 Box, which is having Logshipping failed on secondary database, the secondary database was in stand by mode right now but no more restore operation performed on this database since 2 weeks! We checked in the SQL error log and found the error code 14421, severity 16, stat: 1
How to reset the logship back to normally, do I need to disable the jobs before proceed any operation!
I backed up a database to drive f:, then did restore and set options to move the .mdf and .ldf files to different HDs (f: for .mdf and d: for .ldf).
During restore I got a disk IO error. The restore terminated abnormally. Now I have no DB but the .mdf and the .ldf have been moved to the HDs that I specified in the restore options.
I cannot move the .bak file from the f: it gives me an IO error when I try this. It did allow me to copy the .mdf from f: to d:
I need to know how to recover the db frm the .mdf and .ldf files. I have tried using sp_attach_db and got the following error:
An error occurred while processing the log for database 'MyDB'
Hello, I have a database backup taken from SQL Server 2005. I originally had placed the backup into a file in My Documents, but when I went to locate the backup file there (C:/Documents and Settings...), the folders would not expand. So I moved the backup to the C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBackup directory and was able to select the file there. When I try to restore this file into SQL Server 2005 Express using the Management Studio, I get the following error message:
Restore failed for Server 'DELL670DESKTOPSQLEXPRESS'. (Microsoft.SqlServer.Express.Smo) ------------------------------ For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476 ------------------------------ Program Location: at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv) at Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseOptions.RunRestore() =================================== System.Data.SqlClient.SqlError: The operating system returned the error '5(Access is denied.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLsequoia.mdf'. (Microsoft.SqlServer.Express.Smo) ------------------------------ For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&LinkId=20476 ------------------------------
Can you please help me figure out what I am doing wrong?
I just restored a database on a new server with a backup(complete backup stored in backup device) from another database on another server using the "with move" option. In fact here was my process:
Alter database ngauge SET SINGLE_USER WITH ROLLBACK IMMEDIATE
restore database ngauge from disk = 'C:Program FilesMicrosoft SQL ServerMSSQLBACKUPgauge1.BAK' with move 'NGAUGE' to 'C:Program FilesMicrosoft SQL ServerMSSQLDatagauge_Data.MDF', move 'NGAUGE_Log' to 'C:Program FilesMicrosoft SQL ServerMSSQLDatagauge_Log.LDF'
Alter database ngauge SET READ_WRITE
it worked.
But it did not move the 98 or so users/logins...from the source database what is going on??? what am I doing wrong??!!
I created log shipping btw two servers using maintenance plan.
maintainanace plan taking the log backups and copying those backups in the standby server but unable to restore thos log backups
i am getting the following error ( for the Log Restore job) Executed as user: NT AUTHORITYSYSTEM. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
In the logshipping monitor history i found the follwing error [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4305: [Microsoft][ODBC SQL Server Driver][SQL Server]The log in this backup set begins at LSN 4830000001442600001, which is too late to apply to the database. An earlier log backup that includes LSN 4828000001884200001 can be restored. [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.
I have a two SQL 2012 databases in Development Environment as below:
1. LT_MSCRM (Main Development Database; Same database name is used across Testing and Live servers) 2. LTTEST_MSCRM (Just Created to practice something)
I have take the database back of LT_MSCRM from Testing server and want to restore it on LTTEST_MSCRM in Dev. Its failing because of the following error.
System.Data.SqlClient.SqlError: The file 'C:Program FilesMicrosoft SQL ServerMSSQL11.MSSQLSERVERMSSQLDATALT_MSCRM.mdf' cannot be overwritten. It is being used by database 'LT_MSCRM'. (Microsoft.SqlServer.SmoExtended)
The following failed in EM (or whatever it is called now managementstudio I think) and I scripted it out and ran it in a query window toget more info. This works fine in SQL 2000 but not in 2005. I also triedto 'create' the database first then ran this command below but with the'force restore over existing database' checked on but this failed alsowhich is odd as well. Any ideas. This is my very first play with 2005 soit is not off to a great start although to be fair, i seem to have gorlucky on the install as it all went OK. BTW, is there a more approriatenewsgroup for this query?ThanksRESTORE DATABASE [bob] FROM DISK = N'C:BigFujiCopiesBob.bak' WITHFILE = 1,MOVE N'bob_Data' TO N'c:Program FilesMicrosoft SQLServerMSSQLDataob_Data.MDF',MOVE N'bob_Log' TO N'c:Program FilesMicrosoft SQLServerMSSQLDataob_Log.LDF',NOUNLOAD, STATS = 10GOMsg 5122, Level 16, State 1, Line 1Directory lookup for the file "c:Program FilesMicrosoft SQLServerMSSQLDataob_Data.MDF"failed with the operating system error 3(error not found).Msg 3156, Level 16, State 3, Line 1File 'bob_Data' cannot be restored to 'c:Program FilesMicrosoft SQLServerMSSQLDataob_Data.MDF'.Use WITH MOVE to identify a valid location for the file.Msg 5122, Level 16, State 1, Line 1Directory lookup for the file "c:Program FilesMicrosoft SQLServerMSSQLDataob_Log.LDF" failed with the operating system error3(error not found).Msg 3156, Level 16, State 3, Line 1File 'bob_Log' cannot be restored to 'c:Program FilesMicrosoft SQLServerMSSQLDataob_Log.LDF'. Use WITH MOVE to identify a validlocation for the file.Msg 3119, Level 16, State 1, Line 1Problems were identified while planning for the RESTORE statement.Previous messages provide details.Msg 3013, Level 16, State 1, Line 1RESTORE DATABASE is terminating abnormally.*** Sent via Developersdex http://www.developersdex.com ***
I'm trying to restore my DB to a new server and also a new instance of SQL 2005 SP2+ hotfix KB934458.
I've successfully restored my MSDB database and everything seems to be working fine, but now when I'm trying to do a restore of my Database RMc to the attached SAN,
I'm getting the error:
System.Data.SqlClient.SqlError: The path 'H:' has invalid attributes. It needs to be a directory. It must not be hidden, read-only, or on a removable drive. (Microsoft.SqlServer.Smo)
the H: is the Drive letter for my attached SAN.
The path I'm trying to give is H:\DBData for the MDF-file and the H:DBLog for the LDF-file.
I have the DB running on another server also with a SAN attached and there are no problems.
I also moved the MSDB to another drive on the SAN - a G-drive without any problems.
Has anyone ever experienced the SQL Server unexpectedly rebooting?
Yesterday my SQL Server 7 installation rebooted itself and the error log seemed fine as did the restart. The only evidence I can find was a message in the event viewer's application log stating the the MSSQLServer service terminated unexpectedly. Any ideas are appreciated.
I've a SQL server that intermittently restarts itself mostly during. Its a SQL Server 6.5 SP4 running NT 4.0 SP6. It really has no rhyme or reason to it happening. The are no indications in either the SQL or the Nt events logs. Has anyone heard of this?
I have a linked server set up to a proprietarty temporal DB through an OLEDB provider. From time to time and for various reasons the OLEDB provider crashes with "Error 7302 Could not create an instance of OLE DB Provider 'IhOLEDBProvider.iHistorian.1'. OLE DB Trace [Non Interface Error: CoCreate of DSO for IhOLEDBProvider.iHistorian.1 returned 0x80070008"
Up till now, to re-initilize the connection we have just restarted the SQL Server service. However, some automated processes are now feeding data into this server and more users and have started coming online so restarting for this issue has become a big deal.
Getting the OLEDB provider sorted out isn't an option at present so my question is:
Is there a way to re-initalise a failed linked server other that restarting the SQL Service?
I have SQL server running on windows Adv Server 2000. Since last couple days whole computer restart every one hours. Only thing I remember doing was to shrink database db size is 200+GB.
I've got a table with a column that contains the status of available licenses to the user, i.e. they are either in use or are available. If the server goes down, then when it is restarted I need to make sure all the rows in this column describe each license as being available.
So the question is how can I ensure data in a table is, if you like, initialized, each time the server is restarted? Is there a system defined stored proc or trigger than is executed when a server is restarted?
i hv a database (sql server 2000) where i got locking on many tables and my application was down.
I restarted the sql server and the application was fine but after five minutes the same locking issue started happening. I did a index rebuild the next time on all indexes and everything was fine.But i cannot relate how locking occured and why it was not after index rebuild.Can anyone shed some light on this or anyone had similar experience... cos i cannot figure out a way on this.
