SQL Backup Hangs, Server Freezes
Feb 28, 2007
We have SQL 2000 running on Server 2003. The server has 4 GB RAM, RAID 1 and has the /3GB switch in Boot.ini. We have 6 databases, the largest is about 14 GB. Until recently I could use Enterprise Manager to perform database backups to a folder on the same server but now the operation fails. After selecting the location for the backup and clicking OK, the hard drive light comes on but goes out after 15 - 30 seconds. The progress bar does not move. I've waited and waited but nothing further happens and the server doesn't respond. The only solution is to push the power button and let the server re-boot. Very occasionally the backup will run for a minute or two and the progress bar might get to about one third of the way across, (in which case the destination file will show up with more than 0 bytes), but it never completes. I can find nothing in the event log relating to this problem. As far as I am aware, nothing has changed since the last successful backup. Backups to tape using Retrospect appear to work fine but I haven't done a test restore. Does anyone have any ideas as to what I can try to get the backups working again?
View 14 Replies
ADVERTISEMENT
Nov 29, 2014
Have a server running 14 production databases, 12 of which are replicated (transactional replication) to a second server for reporting. Distributor on same machine as publishers. All set to 'SyncWithBackup' = true, distribution set to Full recovery mode, log backups every 30 minutes, full backup nightly. This generally runs just fine.
Occasionally, the process 'hangs' indefinitely (has gone 12 hours or more before being caught) and I need to stop the backup job, stop one or more of the log reader agents, and restart everything, and it proceeds just fine. Annoying, but not fatal, and not very often.
This time, no matter what, the backup job hangs when it runs. This is true whether it is the FULL backup or just a Transaction Log backup. It hangs on the stored procedure sp_msrepl_backup_start, at the point where it is attempting to update the table 'MSrepl_backup_lsns'. When it is hung like this, all of the log reader agent jobs are also hung, blocked by this stored proc. I've tried stopping ALL of the log reader agents prior to starting the backup, but the backup process still hangs up at the same spot and never ends.
I can run the select statement in that SP that gathers the data for the databases 'manually' in a query window and it finishes in about 10 seconds. It actually seems to be hung up on the 'UPDATE' statement. When it is hung, I cannot SELECT from MSrepl_backup_lsns unless I append WITH (NOLOCK) to the statement. Nothing else I can find indicates that there is anything else locking that table. DBCC OPENTRAN shows that there is a lock on that table held by that stored proc -- but I can't see any reason why it won't update the table (17 total records) and move on.
As I said, normally this runs just fine. Totally baffled by what may be causing this at this time.
View 1 Replies
View Related
Oct 6, 2007
HELP!
For the past several weeks, I have been trying to install SQL Server 2005 on a Win XP SP2 PC. Regardless of the options I choose (SQL Engine + Client Tools, Client Tools only, etc.) when the installation gets to the end of the Client Tools setup and the setup status displays "Removing Backup Files", my PC appears to hang.
For a period of time, there is a fair amount of HD activity which gives me the impression that files are in fact being deleted, but then there is no HD activity and the installation appears to hang. Finally I give up and kill the setup process and reboot.
After reboot, it appears that the client tools have been installed (the icons appear and I can open the Management Studio, but when I try to connect to an existing instance of SQL, that hangs. This occurs for either Windows or SQL authentication.
Has anyone experienced this behavior and determined the root cause? What EXACTLY is happening during the "Removing Backup Files" phase of the installation?
Thanks for any help in advance,
Marc Mueller
View 3 Replies
View Related
Feb 1, 2001
I have a scheduled task that runs backups on our prodcution database at midnight - it usually takes five minutes to run - but the last two nights it has been running for hours and never completing. It ran for 3 hours last night - until i was paged by the database that the transaction log backups were failing (with error 3023) to run because the backup (Backup Database db to db1_nightly with init) job was still running.
The night before our European users could not reach the database - the machine was locked up when I got in in the morning - needed a hard boot to get it back up.
I ran the backup job last night at 8:30 pm and it succeeded - but when it ran at 12:00 AM for the last two days - it runs and never completes. When I tried to kill the process in Enterprise Manager at 3:00 AM, it wouldn't stop. I tried stopping the SQLAgent Service and MSSQLSERVER service to stop the process, with no luck. Finally an early morning drive and a hard boot killed the process.
Any thoughts? There were no new jobs scheduled in the last couple of days. There is no error in the logs (the step never completes - so it's not recorded). The backup works fine if run earlier in the day.
I am running SQL 7.0 with SP2.
Thanks you for any ideas - I'm hoping not to have to drive in at 3 AM this morning - so any thoughts would be great.
View 2 Replies
View Related
Oct 21, 2004
SQL Server 2000
Backup database command hangs. The command I am using is:
BACKUP DATABASE @DBName TO DISK = @filename WITH INIT
Size of the database is 140GB and we have 210 GB free disk space.
sp_who status shows runnable.
Any help would be appreciated.
Thanks.
View 11 Replies
View Related
Oct 11, 2006
I'm experiencing a very annoying failure when trying to do a backup - I hope you can help where others (including me) have failed.
The setup is a SharePoint Portal Server 2003 version 11.0.8126.0 running on Windows server 2003 Standard edition Service pack 1; it has a SQL-server 2005 version 9.0.2047 running on Windows server 2003 Standard edition Service pack as a back-end.
When I issue a backup of the SharePoint database XXX_SITE which holds round 4 gb. of data (mainly documents) the backup process hangs with a Wait Type 'MSSEARCH', it makes no difference whether I issue it as a single job, or through a maintenance plan.
I tried to stop the MsSearch service on the SharePoint-server, and disabled the Full-Text search on the database but it makes no difference.
The only way I can get a backup is to reboot the server on which SQL-server resides (restarting the SQL-server makes it rather unstable), and do a manual back-up shortly after.
View 9 Replies
View Related
Mar 15, 2008
My Vista system hangs immediately after I insert the second blank DVD. I'm doing a simple backup of my user files. I'm using Vista Premium, fully up to date with patches, minimal software installed because this system is 100% used as a Media Center. Hardware is off the shelf HP Media Center m8067n.
I checked Microsoft knowledgebase and no other similar cases popped up. Is anyone else experiencing this?
View 1 Replies
View Related
Jul 24, 2007
We're running the Microsoft product SMS 2003 SP1 for software deployment, patching, hardware inventory, etc. The back-end is SQL 2000 Enterprise SP4 which is installed on the same box as the SMS 2003 SP1 product, and the DB is 145GB's.
We started noticing that the server would freeze every minute or so for 30 seconds. We started logging stats via perfmon and saw that the average disk queue length for the physical drive of F: would skyrocket between 400 - 500 for 30 seconds at the same time the freezing occurred. I have determined that this is occurring during the checkpoint. The recovery interval option is set to the default of 0 on SQL, when I changed the setting to every 5 minutes, the average disk queue length for the physical drive of F: would skyrocket between 400 - 500 every 5 minutes and would subside after 2 minutes. I understand the need for the checkpoint / recovery interval option, but don't believe this high average disk queue length should be occurring.
Does anyone know why this is happening and how to fix this ? The freezing of the box while checkpointing is killing me.
Thanks
View 6 Replies
View Related
Oct 18, 2015
I'm trying to restore a database using SSMS GUI. In "Select backup devices" window if I click the Add button there the window and the whole process hangs like it will never work.
I tried to clear backup history, but that didn't solve it.
I tried with a couple of other databases, but same thing. It was working fine!
View 9 Replies
View Related
Apr 4, 2008
Hi, I'm using SQL2005 v9.00.3042.00 (SP2) on Windows 2003. I have a situation, when I turn on and begin to trace a database using the "SQL server Profiler", that particular VB application that uses the databases freezes (hourglass) when user click on anywhere that require a data query (download list, etc.) until I either pause or stop the trace, what gives? Thanks in advance.
View 2 Replies
View Related
Mar 7, 2008
Set up - windows server 2003 - SQL server 2000 + tools installed
Not sure why its happening but recently when running some scripts onto one of the databases held on the server windows crashes.
I say crashes - it is non responsive but the mouse cursor can be moved.
these scripts are not being run from the server but from one of many machines on our companies network.
Any suggestions would be great
View 1 Replies
View Related
Sep 15, 2004
When I select All Actions>Backup Database and then click the ... button to choose a location on the hard drive, SQL Enterprise Manager Hangs and I have to kill it from Task Manager.
All other areas of EM browse the disk drive without a problem. (DTS, File Groups, etc.)
Anyone ever run into a similair problem?
Thanks
View 2 Replies
View Related
Dec 19, 2005
Hi,
The SQL Server Database hangs overnight and also consumes high disk space on one of our servers. This has been recurring for quite a few weeks and occurs daily.
Can somebody assist me in trouble-shooting the same
Thanks in Advance
Deepak
View 3 Replies
View Related
Feb 27, 2001
Ok,
My SQL Server production DB freezes for 20 minute periods about 3 times a day, during
this time no-one can do anything. I checked the perf. monitor counters (all
the ones there at default), the scary part is that they ALL fall to 0 during
the freeze, then rise to normal. Yes, that's zero %!
I checked the ID's connecting, there are no common ones that connect just
before a freeze, and there are no hardware issues. It's only a 400Mb DB,
with a trans log of 120Mb. Between 200-400 users are connected during
business hours, both from the LAN and off. Some users are running some
fairly heavy reports, but there's no correlation between these and the
freezes. The biggest table only has 1.5 million rows, and the average query
time is 232 milliseconds.
This whole mess has been going on since the 15th of Jan, we searched high
and low for any alterations made, but the client swears blind that no
changes were made. Any ideas anyone?
Thanks in advance all,
Jaishel.
View 2 Replies
View Related
Oct 9, 2007
Hi,
the SQL DB freezes and no one can access the DB for 5 or 10 minutes. Even select queries don t execute, nothing is displayed.
Until we kill the process id that s blocking in the sql activity monitor, only then the DB is released and people can work again.
What does it mean that no query executes until we kill the processes ID? what could it be?
Also, recently we created indexes and ran tuning adviser, is it possible that the creation of indexes cause the freeze of a DB? is that possible?
Thanks a lot for your help
View 6 Replies
View Related
Nov 15, 2004
Hi all !
Hi have a package with 3 steps :
1 - import data from flat file into a temp table
2 - copy selected data from the temp table to permanent tables
3 - truncate temp table
The task #2 is a SQL statement
INSERT INTO MODELS (MODEL_ID)
SELECT DISTINCT MATNR
FROM STANDARD
WHERE MATNR NOT IN (SELECT MODEL_ID FROM MODELS)
where STANDARD is the temp table and MODELS a permanent one. My problem is this simple task freezes all the time. It stalls on 'Starting' and stays in this state forever when I execute the package.
Any idea why ?
View 3 Replies
View Related
Feb 24, 2004
I am installtion MSDE on a Windows XP Pro. The install gets through to 5 seconds and freezes. THis sits for about an hour and nothing happens. The Microsoft SQL Server folder is created, but the services are not created. We tried to reinstall many times and removed the registry key before each reinstall (after uninstalling and rebooting). Any ideas about what could be wrong?
View 9 Replies
View Related
Mar 5, 2008
Hi all
I have a master table, with ID Column int, and Description column Varchar
And another details table, with MasterID Int, and Detail id INT
If i use this query:
SELECT * FROM table1 a INNER JOIN table2 b ON a.id_col=b.id_col
Never returns data, and get freeze, and i have to kill process on Managment
But if i use this:
SELECT * FROM table1 a INNER JOIN table2 b ON a.id_col=b.id_col+0
It returns data i Want, is this a Bug? Or i have an error?
The 2 columns is the same data.
But if I run this,
SELECT * FROM table1 a INNER JOIN table2 b ON a.id_col+0=b.id_col
Nothing happens,
What could it be?
View 5 Replies
View Related
Jun 24, 2002
SQL server freezes my machine.l'm running sql2000 and sp2.Every now and then it freezes my machine as if its running a process in the background. How can l sort this out its slowing my machine down.
l've got 512mb of ram and l don't see why l should have problems with memory .Please help
View 2 Replies
View Related
Feb 27, 2004
Hi
We are repeatedly having the trouble of our publisher database becoming unresponsive during network problems.
We have publisher in carribean, distribution agent in canada and subscribers all over. The problem comes when publisher cant deliver to distributor due to network outages.
We are planning on moving the distributor to the carribean ultimately but that will take a while, and our application repeatedly needs to be restarted due to these freezes.
Does anyone know of this problem & possible ways to fix it in the short term (short of changing our replication topology).
is this a bug in replication?
ps.database is merge & transactional pubs. (some tables merge/some trans)
help much apprec,
des
View 6 Replies
View Related
Apr 9, 2008
I am trying to move data from a transactional database to a data warehouse using a slowly changing dimension. The transactional data comes from a view in SQL server that takes <60 seconds to run and returns about 60k rows. The warehouse table is currently 80k rows long (and growing), and contains 7 historical (type 2) dimensions. When I execute the package in BIDS the DataFlow Task begins to execute, and shows that between 20k and 30k rows have been pulled from the data source into the SCD Transform in the first hour before it simply stops doing anything. This is not to say execution stops; it continues. There is no error thrown. No warning given. System resources are 98% free. The database is not being hit at all. And yet, I have let the package sit 'still' as it were for over 8 hours, and nothing ever happens.
Here is a copy of one log:
starttime endtime message
4/8/2008 9:36 4/8/2008 9:36 Execute phase is beginning.
4/8/2008 9:36 4/8/2008 9:36 PrimeOutput will be called on a component. : 1715 : Union All
4/8/2008 9:36 4/8/2008 9:36 A component has returned from its PrimeOutput call. : 1715 : Union All
4/8/2008 9:36 4/8/2008 9:36 PrimeOutput will be called on a component. : 2912 : Staged Queues
4/8/2008 9:36 4/8/2008 9:36 Rows were provided to a data flow component as input. : : 2970 : DataReader Output : 70 : Slowly Changing Dimension : 81 : Slowly Changing Dimension Input : 9947
4/8/2008 9:37 4/8/2008 9:37 A component has returned from its PrimeOutput call. : 2912 : Staged Queues
4/8/2008 9:37 4/8/2008 9:37 A component has returned from its PrimeOutput call. : 2912 : Staged Queues
4/8/2008 9:59 4/8/2008 9:59 Rows were provided to a data flow component as input. : : 1718 : New Output : 1715 : Union All : 1716 : Union All Input 1 : 3825
4/8/2008 9:59 4/8/2008 9:59 Rows were provided to a data flow component as input. : : 1688 : Historical Attribute Inserts Output : 1682 : Get End Date : 1683 : Derived Column Input : 645
4/8/2008 9:59 4/8/2008 9:59 Rows were provided to a data flow component as input. : : 1702 : Derived Column Output : 1692 : Update End Date : 1697 : OLE DB Command Input : 645
4/8/2008 10:01 4/8/2008 10:01 Rows were provided to a data flow component as input. : : 1759 : OLE DB Command Output : 1715 : Union All : 1758 : Union All Input 2 : 645
4/8/2008 10:01 4/8/2008 10:01 Rows were provided to a data flow component as input. : : 2970 : DataReader Output : 70 : Slowly Changing Dimension : 81 : Slowly Changing Dimension Input : 9947
4/8/2008 10:24 4/8/2008 10:24 Rows were provided to a data flow component as input. : : 1718 : New Output : 1715 : Union All : 1716 : Union All Input 1 : 3859
4/8/2008 10:24 4/8/2008 10:24 Rows were provided to a data flow component as input. : : 1688 : Historical Attribute Inserts Output : 1682 : Get End Date : 1683 : Derived Column Input : 641
4/8/2008 10:24 4/8/2008 10:24 Rows were provided to a data flow component as input. : : 1702 : Derived Column Output : 1692 : Update End Date : 1697 : OLE DB Command Input : 641
4/8/2008 10:26 4/8/2008 10:26 Rows were provided to a data flow component as input. : : 1759 : OLE DB Command Output : 1715 : Union All : 1758 : Union All Input 2 : 641
4/8/2008 10:26 4/8/2008 10:26 Rows were provided to a data flow component as input. : : 2970 : DataReader Output : 70 : Slowly Changing Dimension : 81 : Slowly Changing Dimension Input : 9947
4/8/2008 10:49 4/8/2008 10:49 Rows were provided to a data flow component as input. : : 1718 : New Output : 1715 : Union All : 1716 : Union All Input 1 : 3969
4/8/2008 10:49 4/8/2008 10:49 Rows were provided to a data flow component as input. : : 1688 : Historical Attribute Inserts Output : 1682 : Get End Date : 1683 : Derived Column Input : 662
4/8/2008 10:49 4/8/2008 10:49 Rows were provided to a data flow component as input. : : 1702 : Derived Column Output : 1692 : Update End Date : 1697 : OLE DB Command Input : 662
4/8/2008 10:49 4/8/2008 10:49 Rows were provided to a data flow component as input. : : 1793 : Union All Output 1 : 1787 : Get Start Date : 1788 : Derived Column Input : 9947
4/8/2008 10:49 4/8/2008 10:49 Rows were provided to a data flow component as input. : : 1814 : Derived Column Output : 1797 : Insert Destination : 1810 : OLE DB Destination Input : 9947
4/8/2008 15:34 4/8/2008 15:34 The pipeline received a request to cancel and is shutting down.
4/8/2008 15:34 4/8/2008 15:34 Thread "WorkThread1" received a shutdown signal and is terminating. The user requested a shutdown or an error in another thread is causing the pipeline to shutdown.
4/8/2008 15:34 4/8/2008 15:34 Thread "WorkThread1" received a shutdown signal and is terminating. The user requested a shutdown or an error in another thread is causing the pipeline to shutdown.
4/8/2008 15:34 4/8/2008 15:34 The pipeline received a request to cancel and is shutting down.
4/8/2008 15:34 4/8/2008 15:34 Thread "WorkThread1" has exited with error code 0xC0047039.
4/8/2008 15:34 4/8/2008 15:34 Thread "WorkThread1" has exited with error code 0xC0047039.
Notice the time difference between the last OnPipelineRowsSent event and the first OnError event (when I clicked the stop button): 5 hours! In all that time, SSIS did not log a single event, or use more than 2% of my processor or exceed 1GB page file or hit the database even once! I am assuming this means it is simply not doing anything. It is not failing, nor is it executing, it is just sitting there.
Has anyone experienced a similar problem? Does anyone know how I might troubleshoot this? Thanks in advance for any help, and let me know if I need to clarify. Also, I am new to SSIS, so if I am missing something obvious, go easy on me! Thanks.
Mitch Connors
View 6 Replies
View Related
May 29, 2007
Hi Everybody,
I am having a very weird problem, and I was wondering if you have any idea about what I could do to fix this.
In a nutshell:
* I have this application that uses ADODB and ODBC to connect to an SQL database.
* We have two installations: one running SQL 2000 sp 3, and the other SQL 2005 sp 1.
* The one that runs on SQL 2000, my app performs 8,500 transactions a day with no problem.
* The one that runs on SQL 2005, my app performs 200 transactions a day, and goes down at least once a day.
Trying to figure this out, I noticed that, from time to time, when working with SQL 2005, the application kind of freezes when it tries to read or write to the database, and after a while (say 20 seconds or more), it continues as if nothing had happened. Trying to debug this issue, I noticed that this wait time period is ended if I close one of the other open connections that I have (say, I close the query analyzer)
As people may say, ADODB and ODBC should no longer be used... however, I have noticed this same kind of behavior with other tools, like the query analyzer from the SQL 2000 client tools when connecting to the SQL 2005 server.
I suspected a Licensing issue... however, I haven't been able to replicate this problem by opening several query analyzer instances.
Any help is greatly appreciated!!!!!
Best Regards,
Manuel
View 5 Replies
View Related
Feb 12, 1999
My client is using SQL Server 6.5 on NT 4.0. They have recently began to have their SQL server session freeze intermittently.
I have determined that only users that are accessing one particular database are freezing which leads me to a locking problem.
What is the best way to determine the locking problem (i.e. event logs, sp_lock, ....)?
View 2 Replies
View Related
May 15, 2007
Hi ppl
I have a DTS that is loading 6 text files into respective tables. Before loading this files the tables are emptied using SQL tasks with the following code:
DELETE
FROM Table1
WHERE (OMC=?)
OMC is a PK from table1 and ? is a parameter within the DTS.
Occasionally the system hangs executing these delete statements for one of the tables (not always the same!)
I’m forced to reboot and then DB goes trough a recovery process.
Any idea what might be wrong?
Thanks in advance
View 1 Replies
View Related
May 7, 2007
I have a problem where a SQL 2005 server in the morning will deny all connections do to a time out error. Sytem has 4 CPU's in it and sqlservr.exe is utilizing 85% of all CPU's. If I run filemon it does not show activity to any of the SQL databases. I get a login timeout message when I try to connect via the enterprise manager or from a command prompt, even if I bump the timeout delay to 5 minutes. If I restart the SQL Server services all is fine for a few days.
View 4 Replies
View Related
Jun 8, 2007
On random occasions, our SQL Server instance will just hang and the users will not be able to use the application until we restart the SQL Server 2005 Service. Anyone have any ideas what we might do to figure out what is going on? The server hung up at 8:00 AM this morning. There was nothing after our midnight backup in the log until we rebooted the server at 8:05 AM.
Any suggestions would be greatly appreciated. Thanks! - Eric-
View 1 Replies
View Related
Aug 18, 2006
After I change a fairly complex stored procedure and I run a reportagainst it, crystal hangs at "assesing database". I have verified thedatabase. When I run a trace on SQL is shows repeated cachemiss overand over. I let it run for 30 minutes and nothing.Anyone?
View 5 Replies
View Related
Nov 20, 2007
To the Moderator:
I am not sure if this thread needs to go into this forum or there is one for C# stored procedures/CLR Database Objects.
To All:
Is this a known issue that when debugging CLR stored procedures the VS 2005 freezes even before reaching into the stored procedure? I can restart my computer and debugging works for a while and then it starts to take forever when I step into (F10) during debugging. I am running only one instance of sql server, and even that of my local machine as I have never been able to debug on a remote server.
This random and unstable behavior of the debugger is proving very unproductive and costly. Is there a microsoft update/fix/patch to make debugging CLR stored procedures a smooth process?
Thanks.
View 13 Replies
View Related
Dec 12, 2013
I'm trying to use SSIS in MSSQL 2012 to extract data from MAS90 database.The connection string is tested to be working, because I can extract successfully using the same one in Excel.I follow the wizard of import data in management studio, but after selecting the tables and mapping all those things, when clicking finish, the management studio always freezes.
View 6 Replies
View Related
Jul 23, 2013
I need to import several million records into a SQL table from a pipe-delimited text file. I have tried SSMS 'Import/Export' which is slow so I tried bcp from the command line.Importing records into an empty table with no indexes worked a dream. However..Tried to import 13 million records into an indexed table. After almost 50% of the import (6721000 records) bcp appears to have hung and the Server disk is flashing continuously.
View 7 Replies
View Related
Mar 19, 2004
Forgive my lack of knowledge on SQL here...
We have a SQL server, version 7, that has 4 CPU's. Some of our staff have reports that must be run at random times before cutting checks etc. and these reports bog down the servers CPU's big time, enough so that we can not access the server via Enterprise Manager and at times not even through Query Analyzer. During this time of course other users can not do standard work of saving or accessing the database. Our Processor queue length never seems to go over 1 now. (We recently went from 2 to 4 CPU's do to a 1.4 average queue length).
I have heard that is is possible to limit the number of CPU's that certain query's or events can use. What is the proper terminology for this and can a person do this with limited knowledge? If this can be done during "working hours" so that during off hours query's can use all CPU's, even better.
Thanks,
Mike Gilbert
View 3 Replies
View Related
Nov 23, 2005
I wonder if anyone can help.I have a scheduled job running overnight to delete old records for aparticular Db table.The table contains more than half million records and the scriptsimply uses the date field to delete any of the records which have adate older than 7 days. My guess is that there will be some 100,000records which need to be deleted.The job takes ages to run and whilst it is running sql server iscompletely locked and the associated website is effectively offlinebecause of it.I think I know where the problem lies but I don't know why.Whoever created the Db table created a varchar 255 field as theprimary key. The field is then filled with a string of 40 charactersgenerated within the webserver script to have a 'unique' string.Those are the facts. The following is my interpretation.I think the server is unable to cope with not only a character fieldas primary key but also one with so many characters in it. In such alarger table presumably in order to delete the old records it must dosome sort of ordered sort on the Primary Key and it is this that iscausing the problem.I would like to introduce a new field called 'id' make it autonumberedand primary and make the errant field non-primary.So my question is this:Is my analysis correct but more importantly, why? Can anyone give meclear reasoning for it.Also is the solution sound?Table looks like this:clientID intrefID varchar 255 Primary KeyfieldA varchar 512creationDate datetimefieldB varchar 255field C varchar 32Job script:delete from myTable where creationDate < [7daysAgo]Thanks in anticipationBill
View 2 Replies
View Related
Jul 20, 2005
Hi,The SQL server 2000 Server hangs some times. It is not periodic. It isnot specific in any queries, which are taking more time to execute.Because, it is occurring for different types of applications on thesame server on different machines. For the same applications when wehad the SQL Server 7.0 we didn't have any problem.O/S: Windows 2000 advanced serverServer: Dell power edge 2600 4 way server with 2 GB RAMDB: SQL 2000 - Enterprise edition (Normal default installation)- Noservice packs.Are there any server settings to be done...?Thanks in advance..RegardsSeni
View 3 Replies
View Related