Viewing 15 posts - 17,866 through 17,880 (of 22,219 total)
That's all right.
Pick up a copy of SQL Express. It's free and you can learn most of what you need there. When you want to expand into mirroring 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
March 31, 2009 at 4:20 am
iqtedar (3/30/2009)
"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
March 30, 2009 at 6:16 pm
Excellent. Thanks for letting us know it 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
March 30, 2009 at 6:10 pm
GilaMonster (3/30/2009)
Lynn Pettis (3/30/2009)
Just what do the users expect us to do???Read their minds, pull out a magic wand and make the nasty error go away, of course.
😉
You forgot quickly....
"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
March 30, 2009 at 5:59 pm
I agree with Paul. Do a FULL SCAN when you update the statistics.
"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
March 30, 2009 at 5:58 pm
Oh man, thousands... network connectivity, security, service shut down, changes to connection strings... Those are just the easy ones. It could be client configuration changes... It's really hard to say.
"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
March 30, 2009 at 1:28 pm
Actually I would have expected that to be a problem in 2000 as well. All 2000 is doing is an implicit convert, that you should get in 2005 as well....
"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
March 30, 2009 at 1:26 pm
Looks like you either have a connection error, or possibly your DTC process is down:
Microsoft.CommerceServer.Runtime.CommerceException: [highlight=#ffff11]Could not connect to datasource [/highlight]---> System.Runtime.InteropServices.COMException (0x8004D00A): [highlight=#ffff11]New transaction cannot enlist in the specified...
"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
March 30, 2009 at 1:17 pm
You could run DBCC UPDATEUSAGE. It's possible the allocation information is messed up because of dropped objects, large scale data changes, etc.
"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
March 30, 2009 at 12:42 pm
I would start on a problem like this down one of two paths. Either I feel like I know the query & indexes well enough that I'm going to look...
"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
March 30, 2009 at 12:33 pm
First, if you can define them, get foreign key constraints in place. As the last post said, you're looking at a loss of data integrity. That's worse than any performance...
"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
March 30, 2009 at 12:26 pm
I'd use the method of creating a new copy of the table with all the right structures, migrate the data over, then drop the other table and it's FK's,...
"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
March 30, 2009 at 12:23 pm
My memories of 6.5 are fuzzy (and painful) but I think you could backup directly to disk even then, but I could be wrong.
The one reason I can think of...
"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
March 30, 2009 at 12:10 pm
First disable the automatic affinity in the check box below.
"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
March 30, 2009 at 9:27 am
Did you run the Database Tuning Advisor against that system? That looks like artifacts from there. Statistics usually have look something like _WA_SYS_0000003_0425A276.
"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
March 30, 2009 at 9:24 am
Viewing 15 posts - 17,866 through 17,880 (of 22,219 total)