Viewing 15 posts - 46 through 60 (of 166 total)
If you can reproduce it, maybe in a development environment, it would be useful to run a trace to see what is actually occurring.
December 15, 2011 at 1:32 pm
We're getting ready to do this for a clustered instance with very large databases and replication and the steps to do this were developed along with support from Microsoft. ...
November 10, 2011 at 2:45 pm
That's a good idea since I'm sure that's how these publications are set up anyway. We have to take the databases offline and make sure everything has been processed...
November 2, 2011 at 1:03 pm
This will show you if it is still an active trace.
SELECT @@ServerName, * FROM :: fn_trace_getinfo(default)
These are both required to stop it completely.
October 7, 2011 at 11:24 am
We use a VB script and xp_cmdshell. You have to get this from Windows one way or the other.
October 6, 2011 at 12:59 pm
That's probably more complicated than it needs to be. You could use the import/export wizard by right-clickig on the source database and choosing Tasks > Export Data. It...
October 5, 2011 at 2:38 pm
I was just getting ready to send the same link.
October 5, 2011 at 2:25 pm
You also have to enable the profile on the SQL Agent properties, Alert System screen and restart the service.
September 29, 2011 at 1:36 pm
When we moved to a new data center and upgraded from SS 2000 to 2005, I had to develop a custom log-shipping solution because the built-in could not be set...
September 23, 2011 at 10:09 am
There are a number of links in this post that may be applicable.
September 22, 2011 at 4:16 pm
It appears to be prios to CU1 for SP2. You may be able to determine the KB # from the installed programs list in Windows, by checking the option...
September 19, 2011 at 4:45 pm
I'd run a trace and see what user/login is used to connect and run xp_cmdshell on that fourth server from the terminal services session.
September 19, 2011 at 4:36 pm
We use a sanpshot for a weekly CheckDB of a very large production database. We capture the snapshot size before and after the CheckDB process using this query. ...
September 19, 2011 at 2:21 pm
I'd look at security. When we first saw that error at my last job, it was because the SQL Agent account wasn't a sysadmin and didn't have read rights...
September 19, 2011 at 2:11 pm
It might help to enable additional logging so you might get more information. Take a look at this,
September 19, 2011 at 2:02 pm
Viewing 15 posts - 46 through 60 (of 166 total)