Viewing 15 posts - 33,406 through 33,420 (of 49,552 total)
dean gross (3/18/2010)
Thanks, the backup/restore worked.
Could you explain more what you did? A backup of a 2008 database cannot be restored on a 2005 server.
March 18, 2010 at 2:40 pm
Nik Desai (3/18/2010)
you can disable the constraintALTER TABLE 'table name' NOCHECK CONSTRAINT all
ALTER TABLE 'table name' DISABLE TRIGGER all
Disabling the constraint is not...
March 18, 2010 at 1:41 pm
Lynn Pettis (3/18/2010)
March 18, 2010 at 1:37 pm
GTR (3/18/2010)
March 18, 2010 at 1:32 pm
It is due to the read-only mode. The info on whether there has been a backup since the last break in the log chain is stored in the database header...
March 18, 2010 at 1:02 pm
Grant Fritchey (3/18/2010)
March 18, 2010 at 12:41 pm
No, bulk-logged retains tran log chain. That's why you can switch from full to bulk and back and the log's intact.
Full recovery = log retained, all operations fully logged
Bulk logged...
March 18, 2010 at 11:30 am
jpSQLDude (3/18/2010)
March 18, 2010 at 11:23 am
It's only teaching if the other person is willing to learn. At the moment he doesn't appear to be. Same person who spent 4 pages justifying why posting a solution...
March 18, 2010 at 9:42 am
jpSQLDude (3/18/2010)
March 18, 2010 at 9:19 am
Sorry Tom, one question.
You say there'll be 800 000 rows with the same batchID, but in the exec plan, actual row count was 0. Should it have been 0?
Also, if...
March 18, 2010 at 8:57 am
It's not particularly uncommon. I had a set of queries whose total cost added to 200% the other day. I think it's Kevin (TheSQLGuru) who has a plan somewhere with...
March 18, 2010 at 8:35 am
stefan.gustafsson 60897 (3/18/2010)
March 18, 2010 at 8:13 am
stefan.gustafsson 60897 (3/18/2010)
I find it is more helpful to suggest solutions rather than saying what not to do.
I'll be very happy to give a solution once the actual execution plan...
March 18, 2010 at 7:57 am
Viewing 15 posts - 33,406 through 33,420 (of 49,552 total)