Viewing 15 posts - 20,281 through 20,295 (of 22,224 total)
This works, but be careful, it will cause data loss to open transactions.
ALTER DATABASE [dbname]
SET SINGLE_USER --or RESTRICTED_USER
WITH ROLLBACK IMMEDIATE;
GO
DROP DATABASE [dbname];
GO
"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
June 2, 2008 at 8:20 am
What about a constraint or a rule? Something seems to be affecting the PK or reaching out to these other tables. I just did a couple of tests. I 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
June 2, 2008 at 7:34 am
In addition to the trigger, are any of the columns affected by the update statement (or by the trigger) part of the primary key of the table? If so, you're...
"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
June 2, 2008 at 7:01 am
Are you running more than just SQL Server on the box? That will likely lead to problems later. SQL Server tends to use quite a lot of memory and processor....
"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
June 2, 2008 at 6:53 am
I'd work on making adjustments to the code or the application server so that it doesn't make these types of calls. They shouldn't be required and there's probably a way...
"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
June 2, 2008 at 6:49 am
As Jeff and the others have already said, no, you don't need to put these abbreviations, or any others, in front of the views and stored procedures. However, I'll give...
"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
June 2, 2008 at 6:42 am
SQL Prompt does take some practice to get used to it being involved with your TSQL. I've gotten rather good at hitting the 'Esc' key when I know it's just...
"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
June 2, 2008 at 5:26 am
Really, never?
I find the percentage of the batch to be a pretty useful guide most of the time. Not all of the time, no, but more often than not.
"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
June 2, 2008 at 5:20 am
Transactions on databases are generally short. Actually they should be as short as possible most of the time. That means a small entry in the log. That log gets truncated...
"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 30, 2008 at 12:34 pm
Not as such, no. I was just trying to get an understanding of how things were configured. If you're truncating on checkpoint, uh, I mean, in simple recovery mode, then...
"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 30, 2008 at 11:14 am
I have nothing, but everyone around here enjoyed yours.
"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 30, 2008 at 11:11 am
Purists are going to say at the database. I've mostly seen it done at the application level. You just have to make sure that the developers are with it enough...
"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 30, 2008 at 10:27 am
Gail, you're just too good.
"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 30, 2008 at 7:34 am
Everything Jack said plus...
Have you defragmented or rebuilt your indexes in recent memory? If not, I'd do that.
Have you examined the execution plan to see where the bottlenecks in 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
May 30, 2008 at 7:33 am
Well, if you're going to build it out... probably more than one table, even several. I say this because I know that blocking information, deadlocks, and trace/profiler, data are all...
"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 30, 2008 at 6:51 am
Viewing 15 posts - 20,281 through 20,295 (of 22,224 total)