Viewing 15 posts - 20,311 through 20,325 (of 22,219 total)
Here's Microsoft's Life Cycle Support page. Here's the SQL Server 2005 page. We've got to 2011. Which isn't that far off.
"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
May 29, 2008 at 5:15 am
You can't. SQL Server doesn't support cross-database referential integrity enforcement through the DRI statements. You can set up a triggers, one to check the child table in the event of...
"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
May 28, 2008 at 12:24 pm
Do you mean something like this:
SELECT...
FROM...
WHERE...
ORDER BY CASE WHEN @MyVariable = 52 THEN Column1
WHEN @MyVariable =...
"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
May 28, 2008 at 11:44 am
It doesn't sound like you need to worry about page splits.
I've seen situations where dropping the index and recreate it work better and I've seen places where it made things...
"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
May 28, 2008 at 8:58 am
Short answer, it depends. If the data comes in ordered the same was as the index you'll minimize the amount of work the index has to do as it inserts...
"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
May 28, 2008 at 8:38 am
You should look to use the TOP (1) with an ORDER BY statement. You can modify the ORDER by to get a descending value, going from highest to lowest, by...
"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
May 28, 2008 at 5:49 am
Native speakers of any language talk much faster than non-native speakers. Ask him to slow down a bit too. That usually helps.
"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
May 28, 2008 at 5:24 am
Do you mean delete data from the column? You don't mean the end-users of the app have DDL privileges?
Assuming you want to protect the column... Only allow the users access...
"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
May 27, 2008 at 1:35 pm
Unfortunately, that can be a serious problem. I know we've passed up on bringing in consultants because their English was so bad that we couldn't understand them.
"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
May 27, 2008 at 9:30 am
The key question would be, is he using slang or technical jargon? If he says that something is "cool" then he's using slang to imply that it's good or acceptable...
"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
May 27, 2008 at 8:22 am
Writing twice is writing twice. I've found the OUTPUT clause to be a bit more flexible in some ways than a trigger and it has the added value of 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
May 27, 2008 at 7:02 am
Open the configuration manager. Click on "SQL Server 2005 Services" on the left side of the screen. You should see a list of services include "SQL Server" or "SQL Server...
"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
May 27, 2008 at 6:57 am
Have you run Profiler to watch the code come across? You can at least see what procedure calls are being made with what parameters and then test those same calls...
"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
May 27, 2008 at 6:42 am
Since 2008 hasn't been released yet, I wouldn't suggest making that migration now. But since it's supposed to be released in August (assuming they don't slip again), if you 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
May 27, 2008 at 6:34 am
It is possible for the RI checks to be performance hit, sure. But if you've set up your tables & indexes appropriately, they shouldn't be. Doing an RI read on...
"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
May 27, 2008 at 6:29 am
Viewing 15 posts - 20,311 through 20,325 (of 22,219 total)