Viewing 15 posts - 7,201 through 7,215 (of 19,564 total)
Based on this being related to leads, how large are the tables involved?
Please provide the execution plan too!
January 10, 2012 at 8:18 pm
3graces (1/10/2012)
removing your question makes it very hard to help.
January 10, 2012 at 5:01 pm
2000 records should take very little time at all to update.
Please provide the trigger definition.
January 10, 2012 at 4:37 pm
GilaMonster (1/10/2012)
January 10, 2012 at 3:51 pm
This msdn article explains that.
http://msdn.microsoft.com/en-us/library/ms252109(v=vs.80).aspx
January 10, 2012 at 1:32 pm
SQL Kiwi (1/10/2012)
SQLRNNR (1/10/2012)
I am curious what you guys think makes 2008 AM worse than 2005 AMThe design, implementation, and performance mostly 😀
K - I see you on all three....
January 10, 2012 at 12:27 pm
SQL Kiwi (1/10/2012)
Gianluca Sartori (1/10/2012)
Don't mistreat it that way: it was almost usable in SQL 2005. Something went wrong thereafter.
Almost usable, perhaps, at a stretch. 2008 was a big...
January 10, 2012 at 12:06 pm
This should prove useful.
http://technet.microsoft.com/en-us/library/ms178310.aspx
In short - Cycle the log.
January 10, 2012 at 11:49 am
Ninja's_RGR'us (1/10/2012)
January 10, 2012 at 8:28 am
SQL Kiwi (1/10/2012)
January 10, 2012 at 8:22 am
The query in this article shows how to combine those in essence
http://www.sqlservercentral.com/articles/sp_who2/70222/
It uses the new dmvs and the tran_locks as suggested by Gail.
January 9, 2012 at 4:18 pm
I have seen that a few people have implemented mirroring for this. I have used logshipping or transactional replication to accomplish this.
January 9, 2012 at 2:19 pm
Viewing 15 posts - 7,201 through 7,215 (of 19,564 total)