http://www.sqlservercentral.com/Content tagged Strategies, Database Design posted on SQLServerCentral.comen-us360sjones@sqlservercentral.com (Steve Jones)New Author! Don Peterson writes his first article for us and explores why he considers XML to be...bad! There are some interesting points made here and if you've haven't thought about what XML means to you as a DBA, it's a subject worth spending some time on. http://www.sqlservercentral.com/articles/Miscellaneous/isxmltheanswer/1147/2008/05/02http://www.sqlservercentral.com/articles/Miscellaneous/isxmltheanswer/1147/How many DBAs need a solution to track those changes made for multiple systems? Auditing is becoming more and more prevalent in all systems and having a good solution can really make your DBA job interesting. New author Keren Ramot brings us his technique that works indepedent of the database structure. http://www.sqlservercentral.com/articles/Security/2773/2007/12/26http://www.sqlservercentral.com/articles/Security/2773/How many DBAs need a solution to track those changes made for multiple systems? Auditing is becoming more and more prevalent in all systems and having a good solution can really make your DBA job interesting. New author Keren Ramot brings us his technique that works indepedent of the database structure. http://www.sqlservercentral.com/articles/Security/2773/2007/12/26http://www.sqlservercentral.com/articles/Security/2773/As your SQL Server applications grow, chances are that you have more and more objects, especially stored procedures that you need to keep track of. An organized environment is key to being able to prevent the duplication of code and effort. Joe Sack brings us a look at how he names stored procedures to easy identification. http://www.sqlservercentral.com/articles/Naming+Standards/storedprocedurenamingconventions/2054/2005/10/03http://www.sqlservercentral.com/articles/Naming+Standards/storedprocedurenamingconventions/2054/New Author! Don Peterson writes his first article for us and explores why he considers XML to be...bad! There are some interesting points made here and if you've haven't thought about what XML means to you as a DBA, it's a subject worth spending some time on. http://www.sqlservercentral.com/articles/Miscellaneous/isxmltheanswer/1147/2008/05/02http://www.sqlservercentral.com/articles/Miscellaneous/isxmltheanswer/1147/Having a good set of naming conventions for your SQL Server objects is one of the most vital things to a company. In the long duration of a business, it saves money and time as programmers are transferred internally and don't need to relearn object names. As learning curves lower, cost lowers. This article covers some of the conventions that Brian Knight uses and why he uses them. http://www.sqlservercentral.com/articles/Naming+Standards/sqlstandards/176/2005/02/25http://www.sqlservercentral.com/articles/Naming+Standards/sqlstandards/176/Last week Andy launched a new series about Worst Practices by talking about why the Hungarian naming convention is bad for column names. This week he's at it again, declaring that the practice of having objects owned by anyone other than dbo is BAD! Agree or disagree, we think you'll enjoy reading this article and adding your thoughts to the discussion! http://www.sqlservercentral.com/articles/System+Development+Life+Cycle/worstpracticesobjectsnotownedbydbo/480/2004/11/12http://www.sqlservercentral.com/articles/System+Development+Life+Cycle/worstpracticesobjectsnotownedbydbo/480/This short article looks at some mistakes developers should avoid when they also have the task of designing the database, database objects, or TSQL used to access it. http://www.sqlservercentral.com/articles/Miscellaneous/bestpracticesinanadhocenvironment/1228/2003/12/16http://www.sqlservercentral.com/articles/Miscellaneous/bestpracticesinanadhocenvironment/1228/New Author! Don Peterson writes his first article for us and explores why he considers XML to be...bad! There are some interesting points made here and if you've haven't thought about what XML means to you as a DBA, it's a subject worth spending some time on. http://www.sqlservercentral.com/articles/Miscellaneous/isxmltheanswer/1147/2008/05/02http://www.sqlservercentral.com/articles/Miscellaneous/isxmltheanswer/1147/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/Most databases designs nowadays seem to have at least a few if not many lookup or reference tables. This article helps you define a strategy in how to design, approve, and deploy them. http://www.sqlservercentral.com/articles/Basics/lookupstrategy/921/2003/02/20http://www.sqlservercentral.com/articles/Basics/lookupstrategy/921/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/Last week Andy launched a new series about Worst Practices by talking about why the Hungarian naming convention is bad for column names. This week he's at it again, declaring that the practice of having objects owned by anyone other than dbo is BAD! Agree or disagree, we think you'll enjoy reading this article and adding your thoughts to the discussion! http://www.sqlservercentral.com/articles/System+Development+Life+Cycle/worstpracticesobjectsnotownedbydbo/480/2004/11/12http://www.sqlservercentral.com/articles/System+Development+Life+Cycle/worstpracticesobjectsnotownedbydbo/480/New columnist Gregory Larsen used to not care what his objects were called until recently when he began to become concerned with the system generated constraint names. This short article tells you why. http://www.sqlservercentral.com/articles/Naming+Standards/sysgenconstraintnames/765/2002/08/16http://www.sqlservercentral.com/articles/Naming+Standards/sysgenconstraintnames/765/This article briefly discusses SQL Server's data and procedure cache and shows you the common Transact-SQL statements/command and system tables that you can use to interact with the cache through Transact-SQL. http://www.sqlservercentral.com/articles/Administering/cache/766/2002/08/15http://www.sqlservercentral.com/articles/Administering/cache/766/In this article by Jamie Voss, he shows the methodology he used to develop his task management database. http://www.sqlservercentral.com/articles/Basics/designingaflexibletaskdb/688/2002/05/20http://www.sqlservercentral.com/articles/Basics/designingaflexibletaskdb/688/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/Andy says it's not the greatest book for preparing for the 70-100 exam, but the case study is worth reading for it's explanation of the Microsoft Solution Framework. Read the full review! http://www.sqlservercentral.com/articles/Miscellaneous/analyzingrequirementsanddefiningsolutionarchitectu/561/2002/01/02http://www.sqlservercentral.com/articles/Miscellaneous/analyzingrequirementsanddefiningsolutionarchitectu/561/Should you use this book to prepare for the 70-100 exam? Read the review and find out! http://www.sqlservercentral.com/articles/Miscellaneous/70100mcsdarchitecturesexamcram/562/2001/12/26http://www.sqlservercentral.com/articles/Miscellaneous/70100mcsdarchitecturesexamcram/562/Identity columns are last years news. Have you experimented with uniqueindentifiers - better known to programmers as GUID's? Guaranteed to be unique in the world, they offer a powerful alternative to identity columns. http://www.sqlservercentral.com/articles/Basics/usinguniqueindentifierinsteadofidentity/439/2001/09/17http://www.sqlservercentral.com/articles/Basics/usinguniqueindentifierinsteadofidentity/439/Learn the key basics of writing quality Transact-SQL code. http://www.sqlservercentral.com/redirect/articles/393/2001/09/07http://www.sqlservercentral.com/redirect/articles/393/Having a good set of naming conventions for your SQL Server objects is one of the most vital things to a company. In the long duration of a business, it saves money and time as programmers are transferred internally and don't need to relearn object names. As learning curves lower, cost lowers. This article covers some of the conventions that Brian Knight uses and why he uses them. http://www.sqlservercentral.com/articles/Naming+Standards/sqlstandards/176/2005/02/25http://www.sqlservercentral.com/articles/Naming+Standards/sqlstandards/176/The type of datatypes that you use in your schema could impact the performance and the accuracy of your database. http://www.sqlservercentral.com/articles/Miscellaneous/datatype/173/2001/05/07http://www.sqlservercentral.com/articles/Miscellaneous/datatype/173/