Viewing 15 posts - 1 through 15 (of 1,334 total)
I hope this answer is incorrect. BOL says that WORKGROUP EDITION as "If an instance of WorkGroup is used as a Publisher, it supports a maximum of 25 subscriptions to...
April 2, 2009 at 1:23 pm
This was really a very good question. We had the same problem in the past where a developer had a transaction open and we went into facing slowness in the...
March 19, 2009 at 8:20 am
I am looking for the following details
2. subsciptions for each publication
3. status of all the agents associated with them
November 20, 2008 at 8:39 am
I knew of those SPs but they dint help me giving details like how replication monitor gives. i wanted to get a script that will give almost near info of...
November 20, 2008 at 8:33 am
Try changing the log reader agent values particularly BatchSize and the QueryTimeOut option that should help you.
August 19, 2008 at 6:59 am
Do a DBCC CHECKDB with repair option.
August 3, 2008 at 6:40 am
The task was simple. I read an article and it asked me to use the change instaed of remove in Add/Remove Programs and that helped. Thanks for the help.
July 31, 2008 at 10:37 am
Hope i already explined that. Anyways saying again, there was a high value in the waittime column in sysprocesses table for the broker related processes. the broker service is not...
June 6, 2008 at 9:18 am
I just gave them for your reference. I have already given them as separate parameters only.
May 16, 2008 at 2:20 pm
You need to monitor few many things. Starting from the sql server services to the OS counters. Check for performance monitoring and tuning in SQL Server books online.
March 1, 2008 at 10:59 am
1. In 2000 we have SQLSTP.LOG in C:\Winnt\ directory for installation related error. where can I find such log file for 2005? Installation log is still under the very same...
March 1, 2008 at 10:57 am
You need to upgrade your workgroup version to enterprise edition. You need to start the sql installer of enterprise edition and follow the upgrade steps. Look at the microsoft website...
February 29, 2008 at 1:14 pm
Do you a trace to find out when the connections goes off and comes back this was an issue with SQL 2000 with connection pooling enabled.
February 29, 2008 at 1:13 pm
You need to restart sql server services. Also it would be good if you reboot the server so that it takes effect at that moment itself.
February 29, 2008 at 1:08 pm
Granting execute on xp_cmdshell won't work as sql server requires the user to be a member of OS admin.
February 29, 2008 at 9:48 am