Viewing 15 posts - 18,406 through 18,420 (of 22,219 total)
I'm sorry, but you can't create temporary tables in CE. Since you know this, why are you asking the question?
BTW, you can nest queries in 3.5 & above, does that...
"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 12, 2009 at 6:06 am
No, you can't. You can execute the proc and get a result set within another proc:
EXEC spGetCarList @Parm1 = '42'
You could insert the output of the procedure into a temp...
"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 12, 2009 at 6:00 am
You might not want to go down that road, and I don't blame you, but you might have to. Are you doing full scans on the statistics or just using...
"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 12, 2009 at 5:57 am
Why would you want to do something like that?
"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 12, 2009 at 5:50 am
Follow Stephen's advice. Use the MAX data type and keep working with sp_executesql if you have to do dynamic queries.
"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 12, 2009 at 5:44 am
Can you post the query and an execution plan? That would help. Also, can you show the STATISTICS IO and STATISTICS TIME for the query?
"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 12, 2009 at 5:34 am
Nice to know you figured it out. Thanks.
"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 11, 2009 at 11:52 am
OK. I'm stuck. I assume you've run a consistency check? Can you query the table through the INFORMATION_SCHEMA.TABLE view?
"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 11, 2009 at 11:34 am
How about a refresh? Was it created recently?
"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 11, 2009 at 11:05 am
Two possibilities come to mind. First, there's some sort of security issue, the object is in a different schema which you don't have access to, but the TSQL is logged...
"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 11, 2009 at 10:31 am
No, not really. Without a log backup of some sort, there's nothing to restore from for point in time recoveries. You have to set up maintenance.
"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 11, 2009 at 9:09 am
Dan Colbert (2/11/2009)
Sorry for the delay, here's the connect link https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=410537.
Michael,
Try connecting to the 2005 SSIS in SSMS 2005. I think you'll find it connects to the proper version....
"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 11, 2009 at 9:03 am
Yep, it's like Lowell says. Most of the time temp tables are so small that even putting indexes on them and getting the index used in the execution plan doesn't...
"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 11, 2009 at 8:22 am
I would go with a single Address table and then join tables to the different entities that use it. This allows you to have a single source for address validation...
"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 11, 2009 at 8:21 am
Ah, SQL Server 2000, you need to follow Steve's advice then.
BTW, this is the SQL Server 2005 forum that you posted in. You will get different answers to questions depending...
"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 11, 2009 at 6:46 am
Viewing 15 posts - 18,406 through 18,420 (of 22,219 total)