http://www.sqlservercentral.com/Content tagged T-SQL, Strategies, SQL Server 7, 2000, Programming posted on SQLServerCentral.comen-us360sjones@sqlservercentral.com (Steve Jones)As Chris points out, in most applications these days you end up having to go with optimistic locking, which presents a few challenges. Chris works through the list of options. If you're building web/disconnected apps and need anything besides last update wins, this one is for you. http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/dealingwithchangingdata/1233/2003/12/19http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/dealingwithchangingdata/1233/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 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/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/This one is pretty interesting, Andy discusses a few things he sees in comments that not only fail to add value, they end up costing extra time. There's room for discussion here, but definitely a discussion worth having - comments can make you or break you, here's a chance to think about what you think is important in commenting and pass that on to your development team. http://www.sqlservercentral.com/articles/Miscellaneous/worstpracticebadcomments/893/2003/01/23http://www.sqlservercentral.com/articles/Miscellaneous/worstpracticebadcomments/893/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/