Viewing 15 posts - 21,421 through 21,435 (of 22,219 total)
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
I love the missing index DMV's. They're not a panacea either, but they sure can help you spot something simple quickly.
"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 12:34 pm
Just to toss in a contrarian view point, I've never had DTA recommend a single index that was worth the trouble it took to run a series of scripts through...
"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 10:47 am
If you're not already cycling your error log, you should.
Daily seems a bit high. We cycle ours once a week.
"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 10:43 am
Boy. I don't know where I've been. I sure thought it was that way. Maybe I'm channeling some old bit of knowledge from a different system. Damn. I hate being...
"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 7:09 am
You have to start from a concurrency model. It's either pessimistic or optimistic. You seem to be assuming an optimistic model, there are unlikely to be very many or any...
"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 7:02 am
That's about as open ended a question as it's possible to ask.
Obviously, the Books Online would be a great place to start. I'd also suggest perusing Itzik Ben Gan's TSQL...
"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 6:50 am
If it's possible, format the delimited list as XML and use XQuery to retreive it from there. We've started to find this a more optimal approach than the old one...
"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 6:34 am
Viewing 15 posts - 21,421 through 21,435 (of 22,219 total)