2005 BACKUP LOG Process Goes To Suspended State For Every DB
Dec 4, 2007
Hello. We recently ran into extremely large transaction log sizes on our SQL 2005 box...turns out they were not being backed up. After doing some research, I found that they should be backed up very frequently in order to kee their sizes down. I kind of inherited the mess, but got three maintenance plans set up:
FULL Backup that runs weekly
DIFFERNTIAL Backup that runs nightly
TRANSACTION LOG backup that runs hourly
However, since I implemented the plans there has been high CPU utilization at all times. I finally figured out what was causing it today...the BACKUP LOG process is hanging in "Suspended" mode when I view processes. I have to manually kill them to release the CPU utilization.
How can I trace the cause of the hang? Is there a better way to backup/truncate the log files?
SQL Server 2008 r2 - 6 GB memory...I attempted a backup on a 500GB database but it was taking way too long. I checked the resources on the box and saw the CPU at 100%. I checked the SQL Server activity log and saw a hung query (user was not even logged on) that had multiple threads so I killed it and now the CPU utilization is back to normal.
Trouble is, now all of the threads in the activity monitor for the backup show 'suspended' and the backup appears to be not doing anything.
If I create an adhoc db backup that takes, say 30 miuntes to complete, should I suspend the tran log backups that run every 10 minutes, until the full backup is complete?
SP2 refuses to install for the Database Engine because €śthe previous upgrade did not complete€?, i.e. it detects a suspended installation. The same thing happened to me when I installed SP1. I then remember opening the maintenance dialog and completing the setup, after which SP1 installed just fine.
When I try to do the same thing this time, I€™m presented with the €?complete the suspended installation€? option, which when I run it reports the installation completed successfully. However, in reality the installation still remains in suspended mode for whatever reason. If I reboot and open the maintenance dialog, I€™m still presented with the €?complete the suspended installation€? option. I€™ve even tried to run it more than once, but it doesn€™t help. Needless to say, SP2 still refuses to install.
I don't know why the installation is in a suspended state. I know every part of SP1 installed successfully in the end, and the computer never crashed during the installation. I've been using it every day since then, without any problems. All other parts of SP2 did install successfully.
I created a feedback entry on Microsoft Connect, where you can find the log files created by Windows Installer. The URL is: https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=259606
When performing a tail log backup to an online database through SSMS, the database is placed in restoring state. Is there a proper procedure to take the database out of restoring state after the backup is completed?
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.
Hey guys. I have a question concerning the process a backup does.
Let's say i have MY_DB.mdf set to start at 1mb and unlimited growth by 1mb, and recovery mode is set to full. Let's also say the log file MY_DB.ldf is set to start at 1mb and unlimited growth by 1mb.
First Question: This means the more data is added past it's current size, the file for which data was entered will grow by 1mb, forever if left untouched, right?
Next Question: When I do perform a full backup, let's say a manual backup for now and that I'm using SQL 2005, does a full backup clean up the log file? What I mean by this is, if there are 10000 log entries in the log file, does a backup clean up some of those entries?
--- Reason for this forum:
I ask this because I have a test database I am working with in conjunction with ApexSQL Log (http://www.apexsql.com/sql_tools_log.asp) to test out the software. What I just ran across is that being just a test database I have not backed it up, rather have another copy of it from before I started adding data. It's properties are as described above. The ApexSQL software reads transactions logs allowing one to audit database activites and even reverse any transactions. Before I started using it, I decided to delete about 50 records. Then, a week later, I performed a backup (remember I have never done a backup before) and then I ran the software. The transactions shown in the software only dated back about 2 days earlier, not a week ago. I also looked at the size of my log file and it was only 1mb, and I expected it to be larger. i didnot, however, check the size before any of these steps. That is why I ask if in SQL 2005, does a full backup clean up and/or shrink the log file?
I have recently taken over looking after this machine & the previous guardian is unavailable. I've got to a point where I'm starting to think about looking into MSDB, but am not overly keen to start reviewing this db for obvious reasons... Can anyone please offer advise ?
Thank In Advance Suze.
Environment: Microsoft SQL Server 2000 - 8.00.760 (sp3) on Win2000 H/W Dell PowerEdge 2550
Issue: Discovered in the sql log that there is a second set of bkps occurring around 7:30am - the bkps we have setup, run at 2am & are also being logged to sql log as completing normally.
The 7:30am bkps appear to be backing up to a remote location using pipes... or at a guess an agent ?? (I don't know know what that looks like cos we don't use agents). We backup db's to disk and then let arcserve pick up those backup files later.
I assume that this has been occurring for some time, sql logs back to July 7 advise so... Unable to locate scheduled job / maintenance plan that runs at this time...
Last night I set up a trace to catch it but that hasn't helped me either, apart from telling me that its an internal process to the server, and that the process actually started at 6:50am.
SQL LOGS Entries between midnight & 8am in attached file:
I'm trying to backup a database of 330 GB more or less from my server to an external hard disk connected by optical fiber and I'm receiving the next error:
[SQLSTATE 01000] (Message 3211) Write on "H:sqlbackuppm_import" failed: 33(The process cannot access the file because another process has locked a portion of the file.) [SQLSTATE 42000] (Error 3202) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
My transaction log backup task for the production database which normally takes about 10 seconds has been running for almost about 2 hours now.
Is there any way to stop it without restarting sql services? The scheduled task was stopped from the jobs but spid is still in 'runnable' status. I should not kill 'backup log' or 'xp_sqlmaint' tasks.( It doesn't solve the problem anyway. the SPID goes in rollback status and stays like that until server is rebooted). Any way to find out what causes this problem and how to prevent it?
I occasionally receive the following error on backups to a disk backup device.
BackupDiskFile::CreateMedia: Backup device 'F:MSSQLBACKUPFull_Backup.BAK' failed to create. Operating system error = 32(The process cannot access the file because it is being used by another process.).
There are no other jobs running that access this file during the backup. So nothing else should be trying to touch the backup file.
Rerunning the backup again seems to work so it does sound like something is accessing the backup file, I just can't figure out what.
The backup proc reinitializes the backup file each time it runs with the init parameter and then appends remaining backups with noinit. This error occurs on several different servers. Could there be a problem reinitializing the same backup device? It seems like a previous backup has not let go of the device.
When i see the result of Sp_who2, i see the status of a process as "SUSPENDED" for some of the processes like logwriter, checkpoint etc. and also found the same status for "IF @@TRANCOUNT>0 COMMIT TRAN"
Please let me know what does it mean in the context of SQL 2005
Using SQL Server 2005 w/ SP2 I have a simple select query with a parameterized WHERE clause that in Management Studio runs nearly instantly, everytime. Using the same login, when I run the same query using SQL RS the results (only 6 rows) takes upwards of 5 minutes. If I look at the Activity Monitor, it shows the process as suspended and indicates a CXPACKET. Everything I have read on the forums about this indicate it is an issue with not having SP2 , which I do. Or a 64 bit version, I have 32. Or for large bulk updates, I am doing a very simple select. Does anyone have any clue on this?
I am having a problem with one package that attempts to do a join on two large tables. Within the data flow task control is the ole db source control which has the initial query that joins and filters the tables.
The total number of rows that should be returned are about 80-90million. Running this in debug mode shows the number of rows read/inserted into the ole db destination and it always hits the about the same number of records where it just stops/stalls/suspends around 75 million. I have read some possible solutions such as changing the max degrees of parrallelism but that has not worked.
I am currently using SQL Server 2005 64bit SP2 on a 64 bit platform. This is the only package that does anything like this and I am at my wit's end with this problem.
I have SQL 2005 mmirroring sucessfully working in an ASP.NET 2.0 web application. I also have session state being maintained in SQL Server using the built-in functionality in ASP.NET. The problem is, even with "allowCustomSqlDatabase=True" and specifying a failover partner in the DSN, it appears that ASP.NET does not work with the failover partner. It always tries to get the session info from the "data source" server specified in the DSN.
Is there a way to get the session state to fail over to the mirrored server without writing a custom session state provider?
I'm trying to find a solution to for a report i am building and was hoping that some of you will share your expertise with me. Basically, I need to work out how long an Incident Ticket was suspended (ie it's status is "on hold").
The data is stored something similar to the following...
Ticket Date Status ------ ---- ------ 333 14/03/2005 10:24:19 "to on hold" 333 14/03/2005 15:23:01 "from on hold" 334 14/03/2005 11:14:11 "to on hold" 334 14/03/2005 16:26:15 "from on hold" 335 15/03/2005 10:10:15 "to on hold" 335 15/03/2005 11:15:35 "from on hold" 335 15/03/2005 13:26:10 "to on hold" 335 15/03/2005 14:30:59 "from on hold" 335 16/03/2005 14:00:05 "to on hold" 335 16/03/2005 16:45:15 "from on hold" 336 16/03/2005 10:10:15 "to on hold" 336 16/03/2005 12:45:12 "from on hold"
I have an ASP.Net (C# 2.0) application that has been using SQL Server 2005 Standard Edition with Service Pack 1 to hold the session state in a testing environment. Currently, the session state is being stored in TempDB, rather than the ASPState database. This has worked very well for us until yesterday. We installed SQL Server 2005 Service Pack 2, as well as the Critical Update for Service Pack 2 (KB933508). Once the SQL server was rebooted, I got the following error message when I tried to access the web application. The SELECT permission was denied on the object 'ASPStateTempApplications', database 'tempdb', schema 'dbo'.The SELECT permission was denied on the object 'ASPStateTempApplications', database 'tempdb', schema 'dbo'.The INSERT permission was denied on the object 'ASPStateTempApplications', database 'tempdb', schema 'dbo'. In the web.config file for the application, I have a SQL username and password defined that can access the ASPState database. To correct this issue, I had to give this user db_datareader and db_datawriter access to tempDB.
Has anyone else run across this problem, and is it related to SQL Server 2005 Service Pack 2?
We are experiencing intermittent authentication errors "Error: 18456, Severity: 14, State: 10" on a customer's production server. This is a new server that has just been rolled out in the past several months. Rebooting the server appears to make the problem go away. We are using SQL authentication from a separate server that is running IIS. The application always uses the same username and password to connect.
Server info:
select @@version Microsoft SQL Server 2005 - 9.00.2047.00 (X64) Apr 14 2006 01:11:53 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)
select @@version SP1
Sample error from SQL Server errorlog:
Date 7/7/2006 10:53:24 AM Log SQL Server (Archive #2 - 7/7/2006 12:20:00 PM) Source Logon Message Error: 18456, Severity: 14, State: 10.
MSDN (http://msdn2.microsoft.com/en-us/library/ms366351.aspx) lists various states for this error message but 10 is not included, and it says "Other error states exist and signify an unexpected internal processing error."
Note: This was not a case of a transient error that occurs only when SQL Server is starting up - these errors occurred at a variety of times, two months after the server was last rebooted / SQL Server last restarted.
I was running a stored procedure it was suspended for about 11 hours so I decided to kill it now its in Killed/Rollback stage for 12 hours and when check the status of roll back it says "Estimated rollback completion: 0%. Estimated time remaining: 0 seconds." its using up CPUTIME 380000 and DiskIO 970000. How to do I stop this co.mpletely
I have checked my Production databases, both are went to Disconnected state, both are unable to connect to the application, i checked all the services and its working fine. and restarted the end points on Principal and Mirror, still issue not solved, after restart the witness server End point both the databases are working fine.
I have database with unlimited growth in Data with 2MB growth and Log File with 1MB growth. The continuous data is inserted with min 20KB per minute. We struct with following error and Log file size is too large (85GB) than Data file(20GB). Now server is not allowing to take backup as diskspace is not available.
Msg 9002, Level 17, State 2, Procedure DumpData, Line 10 The transaction log for database '%DB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
Please help me to resolved the issue and let me know hints to shrink LOG file. Data inserted are using ADO applications that uses some insert/select stored procedures that does not have begin transaction-Commit Transaction block as appliction issues the Commit over connection object.
I'm getting a specific error when i try to run a .sql script for a Custom TableProfileProvider ,when i Parse the .sql file Commands execute perfectly. But when i actually "Execute" the .sql script i get the following error. It will produce the table but with "Errors" which dosn't do anyone any good to have errors in the table. I even used the Sql Server Surface Area Configuration to add a new Administrator with the name listed below (WYATT-PCWyatt), that didnt help either..Here is part of the Sample Scheme the problem lies in the [YOURMACHINENAMEASPNET] Server = WYATT-PCSQLEXPRESS Computer Name = Wyatt-PC OS: Windows Vista Home Premium =========================================================== use TableProfileProviders go -- --grants on ASP.NET stored procedures and tables used by the custom providers -- grant EXECUTE on dbo.aspnet_Applications_CreateApplication to [YOURMACHINENAMEASPNET] grant EXECUTE on dbo.aspnet_Users_CreateUser to [YOURMACHINENAMEASPNET] grant SELECT on dbo.aspnet_Users to [YOURMACHINENAMEASPNET] grant UPDATE on dbo.aspnet_Users(LastActivityDate) to [YOURMACHINENAMEASPNET] go --drop table dbo.ProfileTable_1 --go create table dbo.ProfileTable_1 ( UserId uniqueidentifier not null Primary Key, FirstName nvarchar(50) null, LastName nvarchar(50) null, Age int null, LastUpdatedDate datetime not null) go grant SELECT,INSERT,UPDATE,DELETE on dbo.ProfileTable_1 to [YOURMACHINENAMEASPNET] go ================================================================================ Msg 15151, Level 16, State 1, Line 5 Cannot find the user 'WYATT-PCWyattASPNET', because it does not exist or you do not have permission.
Does anyone else have this error message pop up in SSMS when you try to parse sql statements:
.Net SqlClient Data Provider: Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
There was a thread back in March 2006 that mentioned this error, but the posted resolution was to install SP1. I have SP1 installed but I still get the error.
I only receive the error when I'm parsing statements, if I run the statement it's fine.
The 2.0 version of ASPSTATE is slightly different than the 1.1 version in that one table has one additional column and another table uses a different data type and size for the key. The 2.0 version also has a couple additional stored procedures.
We'd like to manage just one session state database if possible so we're trying to figure out if Microsoft supports using the new schema for 1.1 session state access (it seems to work, but our testing has been very light).
Is there any official support line on this? If not, can anyone comment on whether or not you'd expect it to work and why?
Hi, I am developing an application with vb.net and sql server 2005 express edition. If a user logs in (through the application), I want to query the computer host from sql server 2005 in which the user logs on. Is there any special table or procedure that I can use to achieve this? Thanks.
I have a question about blocked processes. My manager wants to know how you can know the following when a blocked process is encountered.
The job, program and the statement that is causing the blocking. I have figured out how to determine the database involved but not a lot else. Such as in the blocked process report there is a waitresource field. How to you decipher it? The report also tells you the client application, but in this case it just states the Micro focus Net Express as the client, not the job or program that is running.
I have an inputbuf listed but it just shows the database id, and the object id. And I am not sure how to locate the object id in this case, I am guessing sys.objects, but I do not seem to find that one.
I have read many things on MSN about the blocked process report, but it does not seem to go into great detail.
I seem to have all the pieces, but do not exactly know how to quickly tie them all together.
We have mirroring setup for 5 dbs, 4 of which are synchronized and 1 which is in "synchronizing" state on the principal and "restoring" state on the mirror. Mirroring for all dbs has been working fine for the past several months and we have a witness that has allowed automatic failover in the past without problems.
This database has several bulk inserts performed throughout the day and am sure there is some latency due to the size of these transactions.
Not sure as to why this is happening all of a sudden, but the db in question has been in this state for the past 12 hrs. I checked the mirroring status on the principal and it states that it is "synchronizing: data is being transferred from principal to mirror", but the mirror server states that db is in "restoring" state. Can anyone suggest as to how I can get the database on the mirroring server to get back to "mirror, synchronizing/restoring..." state? Or suggest on how I can troubleshoot this?
