Viewing 15 posts - 12,496 through 12,510 (of 49,557 total)
Since you've given no indication what the sp_executesql is executing or what proc_DeleteEventReceiver does, I have no idea. Why don't you investigate further?
July 3, 2013 at 1:02 am
Please note: 2 year old thread
July 2, 2013 at 12:42 pm
Should do. Plus allows for potentially better performance than the datediff you had.
July 2, 2013 at 12:36 pm
When restoring you have to specify the exact file name of the backup in the RESTORE statement
July 2, 2013 at 11:01 am
In that case '2013-06-03 00:00:00' as what you originally had ('2013-06-03 12:00:00') is noon, not midnight.
July 2, 2013 at 10:29 am
Mid day or mid night? Which are you calling '12:00 AM'?
July 2, 2013 at 9:58 am
WHERE [WorkForce_JobPosting].[Job Posting Create Date_JP] < '2013-06-03 12:00:00.000'
Why go complex when there's a simple method?
btw, 12:00:00 is mid day. That is what you want?
July 2, 2013 at 9:32 am
If you don't care about degrading performance for your users, shrink at peak time.
July 2, 2013 at 9:30 am
Excellent!
<Shameless self-promotion> There's a chapter on page restores in SQL Server MVP Deep Dives 2 </Shameless self-promotion>
July 2, 2013 at 8:50 am
Got nothing to do with the fact that it's a datetime.
http://sqlinthewild.co.za/index.php/2008/02/25/parameter-sniffing-pt-2/
July 2, 2013 at 8:29 am
Brandie, you can be sooo evil. 🙂
July 2, 2013 at 7:49 am
If you've already deleted the publication, then there's no information remaining as to what was replicated, that's defined in the publication.
July 2, 2013 at 7:42 am
It might be in the default trace, not sure though.
July 2, 2013 at 7:08 am
Viewing 15 posts - 12,496 through 12,510 (of 49,557 total)