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.
Thanks,
- D
how can I configure the SQL server to automatically restart selected services on a regular basis?
View 1 Replies View RelatedI'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?
Thanks inadvance
Hi,
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?
Thanks,
Eamon.
Hi,
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.
How can I fix this problem.
Any help will be highly appreciated?
Thanks.
Samir
Hi,
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?
Thanks.
Hi...
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.
Thanks in advance
hello,
View 1 Replies View RelatedI acciently change the locale id of my sql server using sp_configure. After i stop the server it now can not be re-started. Any help is appreciated.
View 1 Replies View RelatedHello everybody
I setup Sql agent for autostart with sql server and autorestart if stoped
but after rebooting NT or after stoping SQL server it never starts ,I have to start it manualy
Where to look for problem ?
I have an old application to maintain that uses CDatabase to connect to SQL Server. If SQL Server is stopped and restarted, such as in a cluster failover (i.e. move group), then the CDatabase connection needs to reconnect. It seems that it's not capable of doing this on it's own so I need to check the state some how. Various methods, such as IsOpen, seem to be useless as far as determining if I have a "good" connection.
Any thoughts?
@@servername sometimes returns NULL depending on how you have been messing around with replication and various other settings.
The simple solution offered to fix this is to delete the entries in the system tables and sp_addserver 'servername','local' and then restart the SQL service.
This is fine but what do you do in the situation where the SQL server is a 24/7 production box ? Does anyone know of a method / hack to fix this without stopping the service ?
Thanks
s
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.
----------------------------------
Hi All.
Our inhouse app used to run on a SQL2000, but we've recently moved it to 2005.
The move was done by way of backup and restore (it was on a whole new server).
After the move, an odd problem showed up: once in a while, the server seems incapable of finding/using its indexes: everything starts working slowly, until I run a maintenance plan that rebuilds its indexes etc.
In the database/server all relevant options seem to be ok (auto update statictiscs etc.), and my conclusion that it doesn't use its indexes comes from the fact that:
* it gives the results from certain select statements in a totally different order (although the set of rows is the same),
* performance is (all of a sudden) very slow (seconds turning to minutes!!)
This happens:
* at least after a reboot of the server
* sometimes just in the middle of the day
The only way I've found to solve the matter, is by running the maintenance plan to rebuild the indexes, but sometimes this only seems to work the second time.
Does anybody share this experience, or know what to do about it?
Thanks,
Nick.
I am unable to login to the sql server as I would like to reboot the server, please let me know how I can do the following remotely in such a scenario:
1. Reboot the sql server
2. Restart the mssqlserver and sqlserveragent services
Thanks.
I've installed an SSL certificate via IIS. I stopped sql server and agent but cannot restart them. I'm getting the following message in the error log:
2007-10-31 21:24:53.63 Server Error: 17182, Severity: 16, State: 1.
2007-10-31 21:24:53.63 Server TDSSNIClient initialization failed with error 0x2, status code 0x38.
2007-10-31 21:24:53.63 Server Error: 17182, Severity: 16, State: 1.
2007-10-31 21:24:53.63 Server TDSSNIClient initialization failed with error 0x2, status code 0x1.
2007-10-31 21:24:53.63 spid9s Starting up database 'model'.
2007-10-31 21:24:53.63 Server Error: 17826, Severity: 18, State: 3.
2007-10-31 21:24:53.63 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.
2007-10-31 21:24:53.63 Server Error: 17120, Severity: 16, State: 1.
2007-10-31 21:24:53.63 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've tried removing the SSL certificate but with no success.
Help! I'm starting to think that the only solution is to uninstall sql server 2005 and reinstall.
Hi,
We are running one shopping site for our organisation, which includes Tomcat 5.0.28 , IIS & SQL Server 2000 SP3 hosted on platform Microsoft Windows Server 2003 Enterprise Ed. , we are running jsp pages server side and site is hosted on internet,
but it is observed that after every 1/2 days , page will throw following exception, and site get blocked.
javax.servlet.ServletException: Network error IOException: No buffer space available (maximum connections reached?) : connect
Can anybody help please?
I am beginner with JDBC - SQL Server Connectivity ,
I am giving our configuration details:
Driver Used - Microsoft SQL Server Driver 2000 SP3
Protocol Used - TCP/IP which open socket connection on default port 1433
Authentication - Mix Mode Authetication ( using sa account login)
Even setting done within LOCAL instance running on server to allow max. connections i.e 32767
My observation is that some kind of virus threat may causing this error, because if server will be rebooted, we doesn't
get any error and everything works fine.
Waiting for your suggestions and advise.
Thanks a lot.
Regards,
Mandar Velankar
I am trying to install SQl Server 2005 SP2 but it was throwing an unexpected error when trying to install "setup support files".
O/s: Windows Server 2003 SP1
Product: SQL Server 2005 Standard Edition
Log file shows:
+++++++++++++++++++
=== Verbose logging started: 2/20/2007 16:05:42 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: F:SQL2005sp2hotfix.exe ===
MSI (c) (74:68) [16:05:42:635]: Resetting cached policy values
MSI (c) (74:68) [16:05:42:635]: Machine policy value 'Debug' is 0
MSI (c) (74:68) [16:05:42:635]: ******* RunEngine:
******* Product: C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi
******* Action:
******* CommandLine: **********
MSI (c) (74:68) [16:05:42:635]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (74:68) [16:05:42:635]: Grabbed execution mutex.
MSI (c) (74:68) [16:05:42:729]: Cloaking enabled.
MSI (c) (74:68) [16:05:42:729]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (74:68) [16:05:42:745]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (20:70) [16:05:42:792]: Grabbed execution mutex.
MSI (s) (20:68) [16:05:42:792]: Resetting cached policy values
MSI (s) (20:68) [16:05:42:792]: Machine policy value 'Debug' is 0
MSI (s) (20:68) [16:05:42:792]: ******* RunEngine:
******* Product: C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi
******* Action:
******* CommandLine: **********
MSI (s) (20:68) [16:05:42:792]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (20:68) [16:05:42:823]: File will have security applied from OpCode.
MSI (s) (20:68) [16:05:42:901]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi' against software restriction policy
MSI (s) (20:68) [16:05:42:901]: SOFTWARE RESTRICTION POLICY: C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi has a digital signature
MSI (s) (20:68) [16:05:43:151]: SOFTWARE RESTRICTION POLICY: C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (20:68) [16:05:43:151]: End dialog not enabled
MSI (s) (20:68) [16:05:43:151]: Original package ==> C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi
MSI (s) (20:68) [16:05:43:151]: Package we're running from ==> C:WINDOWSInstaller1348fe1.msi
MSI (s) (20:68) [16:05:43:151]: APPCOMPAT: looking for appcompat database entry with ProductCode '{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}'.
MSI (s) (20:68) [16:05:43:151]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (20:68) [16:05:43:167]: MSCOREE not loaded loading copy from system32
MSI (s) (20:68) [16:05:43:182]: Opening existing patch 'C:WINDOWSInstaller1553df86.msp'.
MSI (s) (20:68) [16:05:43:182]: Note: 1: 2203 2: C:WINDOWSInstaller1553df86.msp 3: -2147287038
MSI (s) (20:68) [16:05:43:182]: Couldn't find local patch 'C:WINDOWSInstaller1553df86.msp'. Looking for it at its source.
MSI (s) (20:68) [16:05:43:182]: Resolving Patch source.
MSI (s) (20:68) [16:05:43:182]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (20:68) [16:05:43:182]: User policy value 'DisableMedia' is 0
MSI (s) (20:68) [16:05:43:182]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (20:68) [16:05:43:182]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (20:68) [16:05:43:182]: SOURCEMGMT: Looking for sourcelist for product {EE92F683-5F5C-4970-BB0B-9AC591B60268}
MSI (s) (20:68) [16:05:43:182]: SOURCEMGMT: Adding {EE92F683-5F5C-4970-BB0B-9AC591B60268}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (20:68) [16:05:43:182]: SOURCEMGMT: Now checking product {EE92F683-5F5C-4970-BB0B-9AC591B60268}
MSI (s) (20:68) [16:05:43:182]: SOURCEMGMT: Media is enabled for product.
MSI (s) (20:68) [16:05:43:182]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (20:68) [16:05:43:182]: SOURCEMGMT: Trying source \TESTf$cff417a74df5a718124f2a95bdecdc32HotFixSqlSupportFiles.
MSI (s) (20:68) [16:05:43:213]: Note: 1: 2203 2: \TESTf$cff417a74df5a718124f2a95bdecdc32HotFixSqlSupportFilesSqlSupport.msp 3: -2147287037
MSI (s) (20:68) [16:05:43:213]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (20:68) [16:05:43:213]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msp
MSI (s) (20:68) [16:05:43:213]: SOURCEMGMT: Processing net source list.
MSI (s) (20:68) [16:05:43:213]: SOURCEMGMT: Trying source \TESTf$a81c0730a34f964148HotFixSqlSupportFiles.
MSI (s) (20:68) [16:05:43:213]: Note: 1: 2203 2: \TESTf$a81c0730a34f964148HotFixSqlSupportFilesSqlSupport.msp 3: -2147287037
MSI (s) (20:68) [16:05:43:213]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (20:68) [16:05:43:213]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msp
MSI (s) (20:68) [16:05:43:213]: SOURCEMGMT: Processing media source list.
MSI (s) (20:68) [16:05:44:245]: SOURCEMGMT: Resolved source to: 'SqlSupport.msp'
MSI (s) (20:68) [16:06:14:619]: Note: 1: 1314 2: SqlSupport.msp
MSI (s) (20:68) [16:06:14:619]: Unable to create a temp copy of patch 'SqlSupport.msp'.
MSI (s) (20:68) [16:06:14:619]: Note: 1: 1708
MSI (s) (20:68) [16:06:14:619]: Note: 1: 2729
MSI (s) (20:68) [16:06:14:619]: Note: 1: 2729
MSI (s) (20:68) [16:06:14:619]: Product: Microsoft SQL Server Setup Support Files (English) -- Installation failed.
MSI (s) (20:68) [16:06:14:619]: MainEngineThread is returning 1635
This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.
C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi
MSI (c) (74:68) [16:06:14:729]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (74:68) [16:06:14:729]: MainEngineThread is returning 1635
=== Verbose logging stopped: 2/20/2007 16:06:14 ===
+++++++++++++++++++++++
I have Visual Web Developer worked on my computer, but I can't make SQL Server work for data-driven. I have uninstalled and install VWD from http://msdn.microsoft.com/vstudio/express/downloads/default.aspx , the same Error message...... "..unexpected fail to install SQL server...", the copy of Summary.txt as below:
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Microsoft SQL Server 2005 Setup beginning at Sat Jul 28 06:54:25 2007
Process ID : 3324
c:8845baf7ee339eaf6setup.exe Version: 2005.90.3042.0
Running: LoadResourcesAction at: 2007/6/28 6:54:24
Complete: LoadResourcesAction at: 2007/6/28 6:54:24, returned true
Running: ParseBootstrapOptionsAction at: 2007/6/28 6:54:24
Loaded DLL:c:8845baf7ee339eaf6xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2007/6/28 6:54:25, returned false
Error: Action "ParseBootstrapOptionsAction" failed during execution. Error information reported during run:
Could not parse command line due to datastore exception.
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Wed Jun 14 16:30:14 2006
Function Name: writeEncryptedString
Source Line Number: 124
----------------------------------------------------------
writeEncryptedString() failed
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Wed Jun 14 16:30:14 2006
Function Name: writeEncryptedString
Source Line Number: 123
----------------------------------------------------------
Error Code: -2146893813
Windows Error Text: Key not valid for use in specified state.
Source File Name: cryptohelpercryptsameusersamemachine.cpp
Compiler Timestamp: Wed Jun 14 16:28:04 2006
Function Name: sqls::CryptSameUserSameMachine:rotectData
Source Line Number: 50
2148073483
Could not skip Component update due to datastore exception.
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "InstallMediaPath" {"SetupBootstrapOptionsScope", "", "3324"} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Running: ValidateWinNTAction at: 2007/6/28 6:54:25
Complete: ValidateWinNTAction at: 2007/6/28 6:54:25, returned true
Running: ValidateMinOSAction at: 2007/6/28 6:54:25
Complete: ValidateMinOSAction at: 2007/6/28 6:54:25, returned true
Running: PerformSCCAction at: 2007/6/28 6:54:25
Complete: PerformSCCAction at: 2007/6/28 6:54:25, returned true
Running: ActivateLoggingAction at: 2007/6/28 6:54:25
Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run:
Datastore exception while trying to write logging properties.
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupStateScope.primaryLogFiles
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
00D5CFC0Unable to proceed with setup, there was a command line parsing error. : 2
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
Class not registered.
Failed to create CAB file due to datastore exception
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "HostSetup" {"SetupBootstrapOptionsScope", "", "3324"} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupBootstrapOptionsScope.HostSetup
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Message pump returning: 2
I have a distributed environment with SQL Server 2005 SP2 (RTM) running on one server. This server holds the databases for SharePoint and Reporting Services. I then have SharePoint 3.0 (32-bit version) with the reporting services add-in installed on a second server. I installed the sharepoint object model (64-bit version) on the database server as suggested and have configured Reporting Services to use domain user accounts. The Reporting Services configuration tool is reporting that integration has been successfully set up but I am unable to access the "Set Server Defaults" page without an error. This is the error I receive:
An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode.
Please help.
Hi
We have been having a problem with on of our servers, applications connecting to it are experiencing poor performance, even though the server is only running at a peak of 50%.
The odd thing is that after a sql service restart we couldnt connect at all on the SQL port. We were only able to re-connect after rebooting the actuall box. Is there anything that can be done about this? Its strting to look like a network related problem instead of SQL
We changed the database maintainence plan, after changes do we have to restart the server in order to effect the new changes.
View 2 Replies View RelatedI have got the error “a network related or instance specific error occurred sql server 2012 “.I have enabled tcp/ip, restarted the services. The sql server service is getting stopped even after the manual restart. I have checked in event viewer and I noticed a error. Here is the error...The log scan number (43:456:1) passed to log scan in database ‘model’ is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication.
View 1 Replies View RelatedIs there a way to find the max number of sessions that were on a sql server since its last restart? I know how to get how many total connections there were since last restart, and the current number of sessions, but not the max number of sessions that were running since last restart. Also, opinion on the optinum number of allowable sessions, or a good way to figure out the balance?
View 0 Replies View RelatedI 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 have a simple update statement (see example below) that when runs, I expect to see the number of records updated in the Results tab. This information shows up in the Messages tab; however, what is displayed in the Results tab is (No column name) 40. From where the 40 is being generated. I have tried restarting SSMS 2012, restarting my computer, turning NOCOUNT on and off.
"UPDATE TableA
SET Supervisor = 'A123'
WHERE PersonnelNumber = 'B456'"
I have recently changed my NT password and since then one of my machines has not been able to start MSSQL server. When I re-boot the machine it lets me know that it was unable to start MSSQL server. If I right click on the SQL server group in EM and try to manually start the service, it tells me that I have a login failure. I don't understand how changing my NT password would affect one machine and not the others. When I right click on the "edit SQL service registration properties" tab, all of the machines are using the NT password selection as opposed to the SQL server authentication password. Any ideas would be greatly appreciated
View 1 Replies View RelatedWhen trying to open the log shipping status report, I get an error: user must be in the master database. The jobs appear to be running correctly.
View 0 Replies View RelatedI am going to apply SQL ServicePack 3 in our production Server . Is it possible to avoid restart ?
View 2 Replies View RelatedPlease forgive my ignorance, I am by no means a SQL Expert, but have encountered a strange issue.
I have 6 SQL Servers, Primarily SQL 2005 (one older SQL 2000) all loaded on Windows Server 2003 SP1.
We use the servers for a proprietary database that we created which is the backend to a software package we sell.
The issue I have is: We have added a Security account to the servers, and in one case we have granted rights for this account to the TempDB system database. However, whenever we restart this server SQL drops this user account, thus severing connectivity for the app that is relying on that account.
I have set the account as DB-Owner etc, but nothing sems to keep it on re-start.
Any input would be greatly appreciated.
Running SQL 2005 on a dedicated Dual Xeon 8MB RAM AND 6x 160GB HDDS RAID-5. Front end App Access 2002. I have to main concerns. 1. When users are enter data and saving all of a sudden all users get stuck upon saving and requires to reboot the server to operate again. Th eproblem is that this happens 3 to 5 times a day. Also searching records with one word takes very long time sometimes even minutes, but queries having two or more words come up fast. Also single word queries come up with erratic results, sometimes 200 titles and than a second search comes up with 31,000. *** Can anyone come up with any ideas "off the cuff" on how I canstart to resolve these issues. Can these issues be related?
View 5 Replies View RelatedWe are trying to quickly put together what needs to be accomplished to install a named instance of SQL Server 2000 on an existing production server (also running SQL Server 2000). It appears as if the install will require a reboot. Can the reboot be postponed until after-hours without impacting the default instance of SQL Server?
Also, I see that if certain services are stopped prior to installing sp4 that you can avoid a reboot. However, if we are unable to stop these services (DTC, for example) without impacting the default instance of SQL Server, will the default instance of SQL Server experience any issues if we postpone the post-sp4 reboot until after hours?
Thanks!
Michelle
Whenever I restart the Sql Server Agent, it causes SQL Server to restart also - is this correct ? I thought the dependency was the other way around i.e. restarting SQL Server would cause the agent to restart ? Any insights gratefully accepted.
View 5 Replies View Related