Viewing 15 posts - 8,791 through 8,805 (of 22,232 total)
I'm pretty sure it has the same requirements as distributed replay. You can see the events and columns you'll need to capture here.
"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 5, 2014 at 10:22 am
yuvipoy (3/5/2014)
So u mean to sayDelete from main_table where id=some_input;
Delete from Child_table1 where id=some_input;
Delete from Child_table2 where id=some_input;
Delete from Child_table3 where id=some_input;
Commit tran;
Nope, you have to do it 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
March 5, 2014 at 10:12 am
hlsc1983 (3/5/2014)
Sean Lange (3/5/2014)
hlsc1983 (3/5/2014)
In my database i wanted to include a...
"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 5, 2014 at 8:33 am
RBarryYoung (3/5/2014)
Hey folks. so what's I miss?😀
All the questions on the site have suddenly become well researched an insightful explorations of the deeper meaning of data, databases, disaster recovery...
"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 5, 2014 at 8:29 am
RBarryYoung (3/5/2014)
Grant Fritchey (3/5/2014)
"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 5, 2014 at 8:23 am
yuvipoy (3/5/2014)
Grant Fritchey (3/5/2014)
"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 5, 2014 at 5:59 am
You already seem to have a decent list. But, to provide a means for validation, Jason Strate maintains a monthly checklist that he updates regularly. You can see the latest...
"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 5, 2014 at 5:52 am
It depends on how you're marking the event. Use a severity of "INFORMATIONAL" or "WARNING" instead of "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
March 5, 2014 at 4:23 am
Cascade delete is pretty dangerous. I don't know of many people that use it. It tends to create very large transactions that lead to lots and lots of blocking. 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
March 5, 2014 at 4:20 am
Sure you can. The connection string is a little funky. This is my "server name" for connecting to one of my databases vx6jxrb86b.database.windows.net, well almost. I modified that a little....
"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 5, 2014 at 4:14 am
How about, instead of GeneralInformation, we think of those things as what they are, People. You can then create a People or Person table and there you can locate 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
March 4, 2014 at 8:37 am
I have never had to do this before, so I could be very wrong, but, based on my understanding of replication, you're going to have to rebuild the entire thing....
"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 4, 2014 at 8:35 am
Yep, it includes all the changes made within a database, both structure and data, so no worries.
"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 4, 2014 at 8:31 am
You need to check all the hardware and configurations. If you've never done that, I strongly recommend getting an expert in the door. Hardware configs, especially I/O, can be extremely...
"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 4, 2014 at 8:30 am
Assuming it's getting backed up on a regular basis, I'd just access it's backup to do the restore. You can restore from a file share using "\\myfileshare\myfilename.bak" just fine.
"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 4, 2014 at 8:17 am
Viewing 15 posts - 8,791 through 8,805 (of 22,232 total)