Viewing 9 posts - 1 through 9 (of 9 total)
Don't switch to using NOLOCK. Instead follow the items that David listed. Also, you need to investigate the deadlocks to determine why they are deadlocking. In the...
June 19, 2013 at 10:59 am
You can get most of the answers from this post - http://www.jasonstrate.com/2011/07/july-monthly-sql-server-checklist
July 6, 2011 at 11:27 pm
With the given information, there really isn't any way that this could be determined. The number/type of CPUs, memory available, disk throughput, and the width of the rows will...
February 23, 2011 at 11:55 am
No, not while it is in STANDBY mode. You can recover the database, but then that will break the log shipping configuration.
February 22, 2011 at 3:08 pm
You can configure the log shipping to leave the database in STANDBY mode which allow all of the querying and troubleshooting that you need. You won't be able to...
February 22, 2011 at 2:55 pm
Interesting idea... I would lean towards applying this type of functionality as a business component of an application versus applying it at the database level. I'm also the guy...
August 8, 2006 at 1:23 pm
I have a template that I put together for CodeSmith that I use. It works for a single or multiple tables. Though I should probably update it for...
August 2, 2006 at 12:38 pm
My god... I have to agree with the previous posts. This type of trigger is a wholly bad idea. Besides the massive amounts of overhead in splitting each...
August 2, 2006 at 10:01 am
Try...
update A
set fedref = [Fed Ref Number],
fedrefdatetime = convert(datetime,'[date sent]' + ' ' + [time sent])
from empower.U_wire_info A
join ncenfedrefs on empower.u_wire_info.lnkey = ncenfedrefs.[loan id]
Jason Strate
October 11, 2005 at 8:38 am
Viewing 9 posts - 1 through 9 (of 9 total)