Viewing 15 posts - 19,816 through 19,830 (of 22,226 total)
Or go up to the Search window just about here and type in TSQL and "SQL Server 2008" or "SQL Server 2005." You can filter by article then. There are...
"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
August 6, 2008 at 11:00 am
Last I heard, they were still releasing in August. I haven't seen any definite release dates, but I haven't seen anything that said it was slipping.
Here's a post from...
"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
August 6, 2008 at 10:56 am
Unwise, poorly worded, incomplete, untested, filled with mistakes, rebuttal!
"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
August 6, 2008 at 6:01 am
Oooh, that's a lovely one Steve. There's a product to stay away from.
I'll bet these are the very same developers that are in full-throated howl against using stored procs...
"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
August 6, 2008 at 5:50 am
That's a pretty standard approach. Not necessarily the most accurate since you're only capturing what's different, not specifically what needs to be moved. At some point, depending on your development...
"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
August 2, 2008 at 3:06 pm
Marios Philippopoulos (8/2/2008)
Grant Fritchey (8/2/2008)
"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
August 2, 2008 at 11:15 am
It heppens to us all. That second set of eyes can work wonders sometimes.
"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
August 2, 2008 at 11:13 am
The thing to remember is, to all intents and purposes, the clustered index, is the table.
"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
August 2, 2008 at 3:46 am
You'll have to use dynamic SQL. Put everything into a string and concatenate the table name.
Here's an example (uncompiled, so test it):
DECLARE @mystring nvarchar(max)
SET @mystring = 'CREATE TABLE dbo.' +...
"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
August 2, 2008 at 3:42 am
Why would you need a cursor? It sounds like a simple INSERT... SELECT DISTINCT... will do the job nicely in a single step. Avoid cursors any where and every where.
"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
August 2, 2008 at 3:37 am
Well, not to give competition to Steve... OK, it won't, but there is
"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
August 2, 2008 at 3:29 am
And that's why we've only had to do the FULL SCAN in a few places and on a somewhat irregular basis. Most indexes, most of the time, if they were...
"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
August 2, 2008 at 3:21 am
Sweet. Nice security. No one will ever know that we're running everything off an Access DB
"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
August 1, 2008 at 12:25 pm
Now that I'm thinking about it (and I'm also asking around) unless the database is only a single filegroup, it's unlikely that it would show up as an actual locked...
"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
August 1, 2008 at 11:51 am
Ooh. I hadn't thought of that.
It wouldn't show up as a database lock though, would it?
"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
August 1, 2008 at 10:31 am
Viewing 15 posts - 19,816 through 19,830 (of 22,226 total)