Viewing 15 posts - 1,036 through 1,050 (of 1,192 total)
In this case, you have two instances of an UPDATE query deadlocking with each other.
Essentially, each process holds U locks (used to search for rows to modify, ironically precisely to...
June 3, 2015 at 2:28 pm
First, what are you planning on using this query to do? I'm just curious because you said the goal was to return NULL for new DBs that have not been...
June 3, 2015 at 1:31 pm
I've moved a few instances to 2014, and haven't really run into this sort of problem.
Having said that, one thing that is definitely different between the two is what maximum...
June 3, 2015 at 12:07 pm
What are normal CHECKDB times for that DB? That high number of reads isn't necessarily surprising, because there are more than that many pages in 800 GB.
There are some things...
June 3, 2015 at 7:14 am
mister.magoo (6/2/2015)
Well, of course it's obvious if you explain it clearly 🙂In my defence, I never said I knew anything about anything!
Thanks Jacob
No problem! Believe me, I've been embarrassingly perplexed...
June 3, 2015 at 6:49 am
Hmm...unless I'm missing something, that's not terribly surprising, is it?
READ COMMITTED only guarantees that you don't read data changed by uncommitted transactions. It doesn't prevent reading a row multiple...
June 2, 2015 at 8:02 pm
I would also add that you should be careful if you're going to use the SSD for a volume that does a lot of random writes and might be close...
June 2, 2015 at 9:26 am
It seems the value of one of those variables is resulting in the dynamically generated statement's containing a syntax error.
Without knowing the value of those variables, I couldn't really...
June 1, 2015 at 6:10 pm
Jeff Moden (5/28/2015)
May 29, 2015 at 3:01 pm
Joie Andrew (5/29/2015)
May 29, 2015 at 8:33 am
There is still some that is not clear. Assuming your weeks start on Sunday at midnight, does this mean that you would want a calculation run today to start with...
May 28, 2015 at 4:05 pm
This is a well-documented "feature" of TRY...CATCH. From https://msdn.microsoft.com/en-us/library/ms175976.aspx:
The following types of errors are not handled by a CATCH block when they occur at the same level of execution as...
May 28, 2015 at 2:53 pm
To follow up on this, you might still be a little unsure, since in this case the two collations seem to have the major properties in common (most obviously, they're...
May 28, 2015 at 9:41 am
You definitely can. You have to be careful, because not all of the transaction-related DMVs will record a start time for the SELECT-only transaction.
If you run the SELECT-only transaction in...
May 28, 2015 at 9:20 am
It seems to be due to deferred name resolution, and something only picked up by profiler. See Gail Shaw's answer on this thread: http://stackoverflow.com/questions/812522/how-to-find-what-caused-errors-reported-in-a-sql-server-profiler-trace.
You can confirm by including SQL:StmtRecompile in...
May 28, 2015 at 9:04 am
Viewing 15 posts - 1,036 through 1,050 (of 1,192 total)