Comprehensive Backup Script

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss content posted by Simon Facer » Comprehensive Backup Script

Comprehensive Backup Script

Rate Topic

Display Mode

Topic Options

Author

Message

Simon Facer

Posted Wednesday, January 30, 2008 12:47 AM

SSCommitted

Group: General Forum Members
Last Login: Today @ 10:58 AM
Points: 1,566, Visits: 607

Comments posted to this topic are about the item Comprehensive Backup Script

Post #449212

Howard Perry

Posted Wednesday, September 09, 2009 8:27 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, June 04, 2013 10:54 AM
Points: 150, Visits: 231

In file cleanup job on sqlserver 2005, I get the following error
Executed as user: NT AUTHORITY\SYSTEM. Conversion failed when converting datetime from character string. [SQLSTATE 22007] (Error 241).

Any help appreciated
Howard

Post #785010

vikash.mca

Posted Saturday, November 21, 2009 1:35 PM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, January 12, 2011 6:57 AM
Points: 2, Visits: 51

A well crafted masterpiece, however I need a similar for use with linked servers, would be highly obliged to get help.

Post #822935

mcvilbar

Posted Wednesday, December 21, 2011 10:15 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, November 07, 2012 12:32 AM
Points: 110, Visits: 119

Hope that the naming convention when creating stored procedure must not be sp_ it should usp_ or whatsoever, but not sp_. What is the implications? It might have a performance degradation due to systems stored procedures name will start also sp_. SQL server will try to look first on the systems stored procedure first before users created procedure. But maybe the stored procedure that you created has some reasons why you do it that way. Smile

Post #1225543

« Prev Topic | Next Topic »

Permissions