Viewing 15 posts - 1 through 15 (of 56 total)
Thank you - that worked.
The correct syntax is
sp_trace_setstatus [ @traceid = ] trace_id , [ @status = ] status
September 13, 2013 at 11:28 am
Thanks for the suggestion. I had not heard of this utility, I will research it.
Thanks
September 11, 2013 at 9:51 am
Thanks for your replies.
The disk on the new servers are part of the server - not on a SAN. The current configuration has them on a SAN.
I'll try monitoring with...
September 11, 2013 at 6:25 am
You are so correct in there being no downtime. We will pick a time of day to minimize the impact to potential connections.
Sounds like log shipping is the easiest solution...
August 12, 2013 at 11:01 am
I've found this tool very helpful, in automating too many tasks, we've been doing manually or with a combination of tools. Having everything in one place is wonderful.
We also have...
May 23, 2013 at 11:09 am
Very thought provoking article. I also appreciate the the Microsoft links - I will follow up on them.
I usually enforce encryption in my SQL instances for my network connections, since...
March 8, 2013 at 6:40 am
Thanks everyone.
Gail's article was especially helpful.
February 6, 2013 at 11:26 am
I understand where you're going with these steps. Getting the window to do this on a prod server isn't always easy.
When I failed-over from Node B to A, the instance...
November 29, 2012 at 1:50 pm
In trying to repair or remove the node, I'm using the SQL Setup -> Maintenance options on the CD.
November 28, 2012 at 6:40 am
I configured the node to not automatically failover. Then I moved the instance from Node B to Node A. When SQL was in a failed state on Node A I...
November 28, 2012 at 6:38 am
Thanks for your replies. They are helpful.
Correcting the Select statement to populate the variables was the trick.
The information in the temp tables isn't sensitive, and I drop them at the...
January 24, 2012 at 6:17 am
Based on information I found in Gila Monster's initial respone - I followed the link to blogs.msdn..... 'Size of the Transaction Log Increasing and cannot be truncated or Shrinked due...
January 6, 2012 at 9:10 am
Error: Invalid column name 'originator_id'. (Microsot SQL Server, Error: 207)
January 6, 2012 at 8:59 am
Yes I am familiar with the log file structure. The good new is that my log backups are permitting some of the entries from being deleted & the space being...
January 5, 2012 at 3:04 pm
Viewing 15 posts - 1 through 15 (of 56 total)