Viewing 15 posts - 19,876 through 19,890 (of 22,219 total)
I can't recommend enough that you develop in 2005. Work you do on a 2000 box might not work in 2005 and there are a ton of things 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
July 28, 2008 at 7:00 am
Tons to learn then.
First, make sure you've got a good backup strategy in place. Before you worry about monitoring and all that stuff, protect your data.
Also, you should schedule 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
July 28, 2008 at 6:56 am
If you're trying to control locking through the procedure, it certainly could be the proc locking itself. Rather than try to put more and more locks on, I'd suggest putting...
"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
July 28, 2008 at 6:52 am
There's also a section in Books Online on OUTPUT PARAMETERS specifically. It not only talks about creating them within procedures, but the syntax on how to use them to call...
"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
July 28, 2008 at 6:44 am
If you absolutely MUST use dynamic SQL, make it parameterized instead of a concatenated string. You can then call sp_executesql and pass the appropriate paramters.
"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
July 28, 2008 at 6:40 am
I do believe that we're making buggy whips and at some point a horseless carriage is going to drive by, but it's not in sight at the moment, despite the...
"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
July 28, 2008 at 6:32 am
Just be sure that you're capturing them to a file and not using the GUI. If this causes your server to go down, you were already in severe trouble 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
July 28, 2008 at 6:26 am
From what you described, you're not necessarily seeing a table lock. Have you tried taking a look at sys.dm_tran_locks? That will give you a lot of information about what 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
July 25, 2008 at 8:23 am
And (broken record time) the execution plans for the queries that are causing you the most pain.
"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
July 25, 2008 at 8:20 am
I had never heard of that before, so I did some searching around. You're not the only one to see this. From what I can see out there, it's actually...
"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
July 25, 2008 at 8:15 am
Lookup Backup in the books online.
You might also look at this[/url].
"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
July 25, 2008 at 7:13 am
The pro to having a single table, and I see only one, is that you don't have to worry about JOIN statements in your queries. With decent indexes and appropriate...
"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
July 25, 2008 at 7:09 am
Make sure the other parts of the IF statement are also wrapped in BEGIN..END. You simply can't have multiple statements within an IF clause without wrapping 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
July 25, 2008 at 6:36 am
You only get one statement after an IF clause so your current code is hitting RETURN and exiting. Try this:
ELSE
BEGIN
--==== If The file does not exist...
"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
July 24, 2008 at 8:09 am
Thanks for that. I love these forums. I learn something new every single day.
"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
July 24, 2008 at 8:02 am
Viewing 15 posts - 19,876 through 19,890 (of 22,219 total)