http://www.sqlservercentral.com/Articles tagged Administering, SQL Server 7, 2000, Programming, Strategies posted on SQLServerCentral.comen-us360sjones@sqlservercentral.com (Steve Jones)One of our favorite authors is back with a great how-to on log shipping. This isn't the baked in log shipping, this is a code your own solution that gives you a starting point for your situation. Even if you don't need it now, it's worth looking at to gain a better understanding of how shipping works. http://www.sqlservercentral.com/articles/Administering/customlogshipping/1201/2003/11/26http://www.sqlservercentral.com/articles/Administering/customlogshipping/1201/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 article by Simon Galbraith (from Red Gate software, maker of SQL Compare) discusses migrating changes from development to staging, QA, and on to production. If you've never seen the need for a schema compare tool (Steve Jones!), this is worth reading.http://www.sqlservercentral.com/redirect/articles/982/2003/05/06http://www.sqlservercentral.com/redirect/articles/982/This article looks at change management from the perspective of the DBA, including how to use source control to your advantage and planning for 'self-healing' apps.http://www.sqlservercentral.com/articles/Administering/changemanagement/939/2003/03/18http://www.sqlservercentral.com/articles/Administering/changemanagement/939/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/Jobs are pretty basic aren't they? They are until you get a couple hundred, or a thousand. Andy continues talking about managing jobs by standardizing how you handle notifications and failures, and talks about an interesting idea to monitor jobs separately from SQL Agent. Worth reading! http://www.sqlservercentral.com/articles/Administering/managingjobspart2/919/2003/02/14http://www.sqlservercentral.com/articles/Administering/managingjobspart2/919/How many jobs do you have? 10? 100? 1000? Andy makes the point that what works to manage for a small number of jobs doesn't work when that number doubles or triples (well, unless you only had 1 job to start with!). In part one of two, this article looks at ideas for using categories and naming conventions to get things under control. http://www.sqlservercentral.com/articles/Administering/managingjobspart1/906/2003/01/31http://www.sqlservercentral.com/articles/Administering/managingjobspart1/906/Andy had a semi-disaster similar to the one he wrote about last year. Interesting to see the kinds of problems that happen to other people. This article raises some interesting points that are outside the scope of basic disaster recovery, looking at how/when to move databases to a different server and how to reduce the server load dynamically. http://www.sqlservercentral.com/articles/Administering/anotherdisasteralmost/881/2003/01/14http://www.sqlservercentral.com/articles/Administering/anotherdisasteralmost/881/In this follow up to one of our most popular articles, Andy responds to comments posted by readers and discusses how to manage SQL logins effectively in your applications. http://www.sqlservercentral.com/articles/Administering/thecaseforsqlloginsparttwo/780/2002/08/19http://www.sqlservercentral.com/articles/Administering/thecaseforsqlloginsparttwo/780/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/