January 17, 2008 at 12:37 pm
I've successfully tested and implemented the 3226 trace flag on several SQL Server instances across the enterprise. It appears to have no adverse affects on 32-bit 2K and 2K5 (clustered and non-clustered).
Unfortunately, I have yet to set up a 64-bit cluster for testing purposes. Before I start adding untested and undocumented flags to a production cluster, I would like to elicit information on the effects of this modification.
Are any of you running this trace flag on your 64-bit 2K5 cluster? If so, have you noticed any effects other than the successful backup messages not being sent to the error log?
I would expect there to be none, but I'd rather be safe than have to ask for forgiveness later.
Thanks in advance for the assist!
Kyle
March 19, 2008 at 11:44 am
Finally got the courage to plop this on the production cluster a few weeks back.
If anyone is interested, it behaves as expected and I have noticed no adverse effect.
Thanks!
March 19, 2008 at 12:42 pm
I have it running on 64 bit box and it is doing job without any problem.
[font="Verdana"]--www.sqlvillage.com[/size][/font]
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply