Viewing 15 posts - 18,421 through 18,435 (of 22,226 total)
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
Based on the structure and the statement, this sounds like homework. What have you tried so far that hasn't worked?
"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:43 am
dbo is a system schema. It can't be changed. You just need to add a schema and then make it the default.
"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 5:52 am
Do you mean you have 500 stored procedures that all have the same parameter and you want to change the data type? That's a pretty odd configuration.
Best bet would be...
"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 5:50 am
Just a question, it says "SQL Server 200" is the last digit there a "0" or a "5"? If it's 2005, you can use TRY/CATCH to catch the deadlock 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
February 11, 2009 at 5:43 am
sp_msforeachdb is a cursor.
You can use the INFORMATION_SCHEMA system views. Specifically INFORMATION_SCHEMA.TABLES. These are common between SQL Server 2000, 2005 and 2008, so are a much better place to program...
"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 5:39 am
As Lowell and I both said... No.
"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 5:21 am
OK. So you want to pre-aggregate the data. This is an operation that is best done in the off hours. I'm not sure why you're so obsessed with the amount...
"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 5:20 am
Great. Glad to hear it. It gave me a little blog post, so it's all 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
February 10, 2009 at 5:06 pm
Viewing 15 posts - 18,421 through 18,435 (of 22,226 total)