Viewing 15 posts - 931 through 945 (of 2,840 total)
I would suggest you to try running a trace and see if there is anything running. You do not want to be in position where something is running on the...
August 12, 2010 at 12:16 pm
Ian, It does help with performance. What you gain by doing this is reduce the contention of tempDb. But make sure that all the files are of equal size. As...
August 12, 2010 at 11:57 am
Instead of having one big TempDB file, you could use multiple TempDB mdf files. One for each CPU you have in your server. That should help the TempDB.
Your User...
August 12, 2010 at 10:16 am
How did you set up the Max memory option? Did you use the GUI or did you use sp_configure?
August 12, 2010 at 9:44 am
With minimum downtime you want to bring Server A (primary) back online, Set the log shipping from Server B to A. And then do a No recovery. After that you...
August 11, 2010 at 1:05 pm
When you look at the properties of the DB, what is the initial size for the Log file? You could try to create a log back up to another directory...
August 10, 2010 at 8:28 am
You cannot make transaction log file constant size. The size depends on how many transaction were done between the time you made the last transaction log. When you mean that...
August 10, 2010 at 7:03 am
I must have mistaken. The graph just shows the memory utilization. I thought it was just SQL Server memory that was being showed on the pic. I could not open...
August 10, 2010 at 6:52 am
Keep us posted how it went this time.
August 10, 2010 at 6:50 am
Thanks for sharing that. It will be a good reference when our replication set up blows apart... 🙂
August 9, 2010 at 3:08 pm
SQL Server replication is quite robust. It wont matter which server goes down first. But if you want to be safe, you can stop the log reader agent and restart...
August 9, 2010 at 3:04 pm
I would like to know that as well... We have 325 Plus tables being replicated to two subscribers. These articles are published by using 10 publications.
August 9, 2010 at 2:25 pm
Since every developer has sys admin rights on the development DB, you cannot keep one job away from them. You could always delete that job or disable it so that...
August 9, 2010 at 8:52 am
The subscriber itself cannot do that. You should maybe look at Peer to Peer replication. Then you can update both subscriber and publisher.
August 9, 2010 at 8:48 am
Seems like you have given almost every bit of memory to SQL Server. It would be a good idea to leave atleast 1 to 1.5 GB for the OS. Or...
August 9, 2010 at 8:44 am
Viewing 15 posts - 931 through 945 (of 2,840 total)