Glad it worked..

Sometimes these things are sent to try us.. 🙂

Hi There,

Does the SQL Log give any more details?

If you now run the entire backup command from ssms does it complete?

Which user runs the Job and what permissions does it...

Hi,

If you run

BACKUP DATABASE [Resource] TO DISK = N'D:\SQL_Database_Backup\Resource_noinit.bak'

from within SSMS does it complete okay?

Hi kaplan71,

Run Sqlbuddy123's script it will tell you what is being used to back the database up. Run it on the same database as you provided the info for.

SqlBuddy123.. Mind If I grab that script..? I was just starting to write something like that.. 😀

Hi,

I don't think thats the one you are after, the backup I'm questioning is running at 19:00. what was in the SQL Server Logs at the date and time I...

Hi There,

I suspect your woes are being caused by these lines:

{77661EF0-2CBD-43C4-8E72-1E1CABD74B71}3 2 MB 20 Seconds 2014-03-17 19:00:31.000 77000000001600017 77000000002400001 Full MGHROSTOR3\RAYCLINICAL FULL

This is a FULL backup taken in the middle...

Just above the top of the script put the following:

USE MyDatabaseName

GO

MyDatabaseName is the name of your database

Hi,

Could you run that script on a database which you are backing up using FULL and DIFF backups.

One question about this resultset. what backup is causing this line:

master {77661EF0-2CBD-43C4-8E72-1E1CABD74B71}23 3...

I Can't remember where I got this script from, it's in my tool kit.

Run this on the database in question and look at the backup chain, something is breaking it....

Someone will be along with a neater way to do this, but this would work

SELECT soi.slord as ORDER_NO,

...

Hi,

Something to think about as a wider resolution to your issue is setting up SNAPSHOT ISOLATION which allows for optimistic locking. Kendra Little wrote a great post on it here:

Before you shrink the database..

Shrinking is not really a recommended practice for a number of reasons, have a read of this blog post:

http://www.sqlservercentral.com/blogs/steve_jones/2010/09/14/common-sql-server-mistakes-_2D00_-shrinking-databases/

The data file does not shrink...

Hi Michael, your solution is much more elegant than mine.. And quicker.. 🙂

I would do this:

Create a backup of your table, because backup is your friend.. 🙂

Select all archive rows into a temp table

Update the rows in the temp table with the...