It does not lock objects, but does mark each page - no disruption will
occur from a coding standpoint.
But the server I/O will be impacted slightly.

I have a developer - that always wines about "I had an application
crash, were you running a backup..."
And it bugs the crap out of me. I have never seen a backup cause an
application issue, UNLESS, the appliation queries were at the brink of
failure due to timeouts, and the overall server load was too high to
meet the query demands in < 30 seconds.

But then that is not a backup problem - it's a resource problem - or a
query/system design problem.



-----Original Message-----
From: Theodore Andrew
[mailto:mssqldba-ezmlmshield-x52314469.[Email address protected]
Sent: Thursday, June 28, 2007 5:47 PM
To: LazyDBA Discussion
Subject: SQL Backup question
Importance: Low

When running a full database backup, does it create and exclusive locks
on objects in the database or is it mainly shared locks? Reason for
asking is would this cause connectivity errors through ODBC connections
while this is running?


Andrew Theodore
Database Administrator


---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY To post a
dba job: http://jobs.lazydba.com To subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html



MS Sql Server LazyDBA home page