Rajat Jaiswal-337252 (8/18/2010)

---

george sibbald (8/18/2010)

---

its available because its something you might have to do if space is a problem. there is a command to drop a database also, doesn't mean...

no probs.

FILE =1 should not be necessary. If you are always backing up to the same backup file name ensure you use the init clause in the backup, otherwise it...

It is as long as you also include the 'with replace' clause

could be the fill factor is too low or the clustered index is on a column with lots of inserts\updates and the values are random (nonconsecutive)

or the table could be...

its available because its something you might have to do if space is a problem. there is a command to drop a database also, doesn't mean you should as a...

nope. you cannot go backwards in versions. you would have to do 'logical' restores on a object by object basis.

suggest you make your DR version the same as the live.

the size of the backup will be equivalent to the space used within the database. But the database also contains information on the sizes of the files that make up...

oops.just seen this thread is 2 years old.................

original code by rbarry young..................

SELECT SCHEMA_NAME(tbl.schema_id) as [Schema]

, tbl.Name

, Coalesce((Select pr.name

From sys.database_principals pr

...

interesting stuff on sa but i thought the question was on the service account!

The OP seems to have backed out as well.

Andrew, a google of that error suggests permission issues. Are the SQL services on the secondary running under a domain user account that has sufficient privileges on the primary server?

not through the GUI install. Its a bug.

a possible way to do this is to get the ID of the table, and then see if the spid holds any locks on that object by querying on sys.dm_tran_locks...

both mirroring log shipping are replaying all transactions on the secondary, so if it CHANGES data that is held in the primary database, it has the same affect on the...

according to SQL2008 BOL notruncate and truncateonly are not applicable to log files. So in fact what is happening is notruncate and truncateonly are ignored when it is a log...