Viewing 15 posts - 21,091 through 21,105 (of 22,224 total)
Database design and indexing design is a tough topic and it takes time to get it right. Two books that you might want to add to your library are Inside...
"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
February 7, 2008 at 11:31 am
Nope. The one issue that we've had, and believe me the developers have howled, is that they can not simply add procedures (or drop them either). They have to let...
"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
February 7, 2008 at 8:40 am
To capture the rows moved have a look at the OUTPUT clause.
"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
February 7, 2008 at 7:01 am
It's simply scanning an index along the logical chain of the index instead of along the storage chain, an allocation scan. This is usually from an ORDER BY, but can...
"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
February 7, 2008 at 5:59 am
I'm pretty sure I'm old fashioned, but I still use OUTPUT parameters in some situations. Let's say you have a situation where the application normally creates a row in a...
"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
February 7, 2008 at 5:44 am
Oops. Hit the "Post Reply" button too soon.
And no, this isn't a problem, depending on how you apply it. Multiple varchar fields of length 3000 would be a really poor...
"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
February 6, 2008 at 9:24 am
You mean "compound" primary keys right? Because you can only have one primary key per table.
Although, you can have multiple unique constraints and refer to those as "alternate" keys...
"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
February 6, 2008 at 9:21 am
Nope. That isn't possible.
What you can do, although it is VERY strongly not recommended, is pass the table name in as a string and then use dynamic TSQL to use...
"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
February 6, 2008 at 8:45 am
Just remember that Books Online (BOL), the doucmentation installed with SQL Server, is your best friend in the world. Don't be a afraid to open it up and read up...
"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
February 6, 2008 at 8:41 am
This is a decent overview.
"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
February 6, 2008 at 8:32 am
Sorry Sandy, not a clue. I've only seen MySQL once or twice. I'm just not terribly familiar with 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
February 6, 2008 at 6:50 am
After you get the truncate working, you'll want to look at the query plans for the views to ensure that good indexes are in place.
"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
February 5, 2008 at 12:38 pm
That is odd. Did you try taking off only part of it? Remove the parenthesis? Remove the ON [Primary]? Remove one of the WITH clauses?
I'm just not sure. I've run...
"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
February 5, 2008 at 9:09 am
We've used LiteSpeed for quite a while. Nothing spectacular to report. The tools is pretty solid. Quest has been adequate as a vendor. I've also tested RedGate's tool and found...
"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
February 5, 2008 at 8:44 am
You've got a second problem as well, you need to make sure that you have the security settings to allow you access to that file. Once you've addressed that...
Can they...
"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
February 5, 2008 at 6:38 am
Viewing 15 posts - 21,091 through 21,105 (of 22,224 total)