Viewing 15 posts - 21,421 through 21,435 (of 22,226 total)
Whoops. Assumptions will get you. Sorry.
BOL = Books Online. The documentation that comes with SQL Server.
If you can't modify the code directly, but you're getting this error, you may want...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 11, 2007 at 10:51 am
Well, see, I'm right!
😀
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 11, 2007 at 9:31 am
It's basically telling you that the procedure had a high enough cost that it thought parallel execution would help. When executing in parallel, it caused a deadlock. First one I've...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 11, 2007 at 9:28 am
SriSun (12/11/2007)
Actual process: I check for @geolevel (doesn't exist), call another procedure (proc1 which takes couple of parameters along with @geolevel) and...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 11, 2007 at 9:15 am
You only want to put that stuff in as a last resort, usually because of some sort of design error, bad index, or something else that you can't spend time...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 11, 2007 at 7:01 am
What Jason said.
But remember, it's going to force the optimizer to make other choices. Every so often those other choices might work better, but then it's because the HASH join...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 11, 2007 at 6:59 am
Connect with a user that has more restricted rights to the file.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 11, 2007 at 6:39 am
You wanted four rows instead of three, right? Try this:
select typeId, trypename, typeInfoDesc
from types t left join typeinfo ti
on t.typeId = ti.typeInfoId
AND typeinfoId2 = @infoNr
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 11, 2007 at 6:37 am
In a case like this, use the tool above or, if you want to roll your own, SMO (SQL Management Objects) allows you generate SQL scripts by object or for...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 11, 2007 at 6:05 am
But if you're using the GUI and you still need to change the schema, display the properties page from the table creation screen. You can change the schema there. Same...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 11, 2007 at 6:02 am
It can be useful if you're returning a large amount of data and you don't want to wait for all the rows to process prior to the data returning. You...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 11, 2007 at 5:58 am
If you're getting primary key violations, something else is up. You may also need to post the structure of the table you're inserting into.
Is that the complete procedure? Is there...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 11, 2007 at 5:50 am
We use just 1204. I'm wondering though if we shouldn't switch it over to 1222. The XML output looks easier to read. Anyone using that?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 11, 2007 at 5:27 am
Not stupid, you just needed a nudge.
I've been going around telling all & sundry that the bit data type wouldn't take a null. Then Gail just simply tells me I...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 11, 2007 at 5:19 am
Instead of VARCHAR, if you use NVARCHAR, that might address the issue.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 10, 2007 at 1:06 pm
Viewing 15 posts - 21,421 through 21,435 (of 22,226 total)