Viewing 15 posts - 20,641 through 20,655 (of 22,219 total)
If the query is really long and it's creating and loading huge temporary tables, it won't complete the transaction and clear the log of those temporary tables until the context...
"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
April 16, 2008 at 6:37 am
The problem is, executing a dynamic query like that is creating a different execution context. As soon as that context clears, which happens when the execution finishes, the temporary 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
April 16, 2008 at 6:30 am
Also, for what its worth, you're doing unecessary work, selecting into the temporary table and then selecting from the temporary table. Instead, just use the select statement that would load...
"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
April 16, 2008 at 6:25 am
Suspended means waiting. Something interrupted the process and it's in a wait state. I'm not that familiar with Access, but from what you're describing, Access is in some manner holding...
"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
April 16, 2008 at 6:16 am
Either way you go, to ensure that you're getting the exact same result set you need to use ORDER BY to ensure that the 1000 rows you get is 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
April 16, 2008 at 5:44 am
Everything Gail said and look at your execution plan (I'm getting sick of typing that. Anyone have a macro?) to see which indexes have a positive affect and which have...
"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
April 15, 2008 at 1:49 pm
This looks like a fun one to pile on to
1) A bit field, all by its lonesome, can be a horrible choice for an index (although in rare circumstances as...
"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
April 15, 2008 at 1:45 pm
Some like this would work. Instead of just the SELECT statement, use that statement with an INSERT statement into the auditing table of choice.
DECLARE @SqlString NVARCHAR(MAX)
DECLARE @DbName NVARCHAR(MAX)
DECLARE MyDatabases CURSOR...
"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
April 15, 2008 at 7:53 am
Thanks for the reply. Yes, ORM, in this case, meant Object Relational Mapping.
We are talking about new projects and new databases. Although actually, we've had databases and projects running, but...
"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
April 15, 2008 at 7:43 am
Nice. Much better, and I'm sure it performs a lot better.
"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
April 15, 2008 at 7:34 am
Or, you can have a procedure call itself. That too is recursion. Triggers can call themselves too. That's usually referred to as "an error."
😀
"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
April 15, 2008 at 6:52 am
Check your structure. I created a structure like this:
CREATE TABLE dbo.FileName
(
tipcon INT
,data DATETIME
,field1...
"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
April 15, 2008 at 6:51 am
Johann Montfort (4/15/2008)
I have a complex stored proc, which I inherited from the previous developer, and I wish to fine tune it a bit, because its taking 1.36 mins...
"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
April 15, 2008 at 6:45 am
Mahesh Bote (4/15/2008)
ALTER PROCEDURE [dbo].[sp_getpageidsforedb]
@projectid int
AS
Set Nocount On
Begin
create table #ebdindex (
[indexid] [int] IDENTITY (1, 1) NOT NULL ,
[stringid]...
"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
April 15, 2008 at 6:29 am
First, having an index on a table won't slow down reads of that table assuming the reads use a different index. Second, get an execution plan for the query 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
April 15, 2008 at 6:27 am
Viewing 15 posts - 20,641 through 20,655 (of 22,219 total)