http://www.sqlservercentral.com/Content tagged Administering, Visual Basic 6, Strategies, SQL Server 7, 2000 posted on SQLServerCentral.comen-us360sjones@sqlservercentral.com (Steve Jones)Andy has been busy lately on a project you'll be hearing more about soon (!), but he did manage to get part four of his managing jobs series done. This article discusses ideas for patterns to follow when building jobs, including writing to the console, setting errorlevels, and how to get them installed on the server. DBA's, if you're not developers, look at this article - this is stuff you can take to your development team and get better/more manageable jobs. http://www.sqlservercentral.com/articles/Administering/managingjobspart4/1037/2003/06/25http://www.sqlservercentral.com/articles/Administering/managingjobspart4/1037/This week Andy looks at where, when, and how jobs should be run and why you need to think about those items before you build the job. Part of this is deciding what runs on production servers and what doesn't. http://www.sqlservercentral.com/articles/Administering/managingjobspart3/936/2003/03/11http://www.sqlservercentral.com/articles/Administering/managingjobspart3/936/Version control for stored procedures isn't always popular and certainly isn't easy. Or can it be? Andy discusses a technique he used on a recent project that you might find interesting. http://www.sqlservercentral.com/articles/Administering/versioncontrolforstoredprocedures/681/2002/05/10http://www.sqlservercentral.com/articles/Administering/versioncontrolforstoredprocedures/681/Ever have a large batch of scripts you need to run? It takes a while if you have to open each one in Query Analyzer and execute it. One of our readers proposed an alternative - take a look the small app Andy Warren wrote to make doing this task a breeze. http://www.sqlservercentral.com/articles/Administering/scriptrunner/292/2001/06/14http://www.sqlservercentral.com/articles/Administering/scriptrunner/292/