Viewing 15 posts - 13,141 through 13,155 (of 49,552 total)
More nolocks... I do hope your users are happy with potentially incorrect data. Nolock is NOT a go-faster switch.
See - http://blogs.msdn.com/b/davidlean/archive/2009/04/06/sql-server-nolock-hint-other-poor-ideas.aspx
May 17, 2013 at 7:00 am
Probably the table variable. Up to 6 million rows in an unindexed table variable without stats = bad idea. Try a temp table or permanent table with a useful index.
May 16, 2013 at 2:27 pm
RedBirdOBX (5/16/2013)
No idea?
The parameters are meaningless and never used.
May 16, 2013 at 9:01 am
RedBirdOBX (5/16/2013)
Thoughts?
The developers were smoking something.
May 16, 2013 at 8:05 am
Can't tell for sure, since you only posted part of the code, but the @Dummy parameter does nothing in the code you posted. Perhaps it's used elsewhere.
The 1 after the...
May 16, 2013 at 7:55 am
Mike Hinds (5/16/2013)
May 16, 2013 at 7:18 am
Mike Hinds (5/16/2013)
May 16, 2013 at 6:54 am
You need to do the usual testing to ensure that nothing in the app breaks on SQL 2008 R2.
May 16, 2013 at 4:06 am
SELECT INTO creates a new table and requires that the table specified in the INTO does not exist, hence I struggle to see how you've defined a trigger on a...
May 16, 2013 at 3:35 am
You can start by taking the nolock hints out.
See - http://blogs.msdn.com/b/davidlean/archive/2009/04/06/sql-server-nolock-hint-other-poor-ideas.aspx
Unless, of course, all the users know and accept that the data returned by the query can be wrong and...
May 16, 2013 at 2:59 am
1, 2, 4, 5. Yes. (don't know about 3)
May 16, 2013 at 2:55 am
In that case, since it's a single text page, deleting the doc may remove the corruption (or may not). CheckDB with repair will just remove that one document
May 16, 2013 at 2:46 am
Why do you want to remove (Principal, Synchronised)? It's telling you that's the principal database for a mirroring configuration and that the mirroring is in the synchronised state (principal and...
May 15, 2013 at 12:00 pm
The delete would probably fail.
Please run the following and post the full and complete output.
DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
May 15, 2013 at 11:59 am
Viewing 15 posts - 13,141 through 13,155 (of 49,552 total)