Viewing 6 posts - 16 through 21 (of 21 total)
We had a similar problem with a database mail stored proc, and it was solved when we realized that the owner of the msdb database was not correct. Verify...
March 25, 2009 at 5:54 am
the "properties" I was referring to is at:
Replication->Local Publications->right click on your publisher and go to "properties".
We think we found the error. The parameter "source_table" in the sp_addarticle procedure...
June 27, 2008 at 8:08 am
Hi Steve,
the "bulk_insert_test_user" is a SQL Login and a member of the BulkAdmin server role. It is a user in the database in question with execute rights to both...
May 9, 2008 at 10:33 am
Thanks for the suggestions!
Scott's suggestion presupposes that we are using the Litespeed activitiy monitor. We haven't done so until now, but this may be a reason to do so. I...
December 20, 2006 at 1:40 pm
Ok, halfway there!
I can now capture a non-zero error code and act on that. Now, is there any way to capture and save in a file the actual Litespeed error...
December 19, 2006 at 2:08 pm
Point taken! I've never wrapped the xp_backup_database into a stored proc, so I didn't know it takes parameters. Thanks!
December 19, 2006 at 1:03 pm
Viewing 6 posts - 16 through 21 (of 21 total)