This month marks the 72nd T-SQL Tuesday. Adam Machanic’s (b|t) started the T-SQL Tuesday blog party in December of 2009. Each month an invitation is sent out on the first Tuesday of the month, inviting bloggers to participate in a common topic. On the second Tuesday of the month all the bloggers post their contribution to the event for everyone to read. The host sums up all the participant’s entries at the end of the week. This month I’m the host and the topic is …
Data Modeling Gone Wrong
The purpose of SQL Server, is to make sure that the databases are kept safe and run as optimally as possible. The problem is, if the data model is flawed, or not maintained, then no matter how optimally the SQL Server is configured, the database won’t be able to function efficiently.
I would like to invite you to share some data modeling practices that should be avoided, and how to fix them when they do occur.
Rules for T-SQL Tuesday Blog Party
Rule 1: Make sure that you include the T-SQL Tuesday image at the top of the post which will help identify your post as a T-SQL Tuesday blog post. Please include a link back to this invitation too.
Rule 2: Publish your post sometime next Tuesday using GMT. Here’s a link to a GMT time convertor. For example, in California, that would cover 5 pm Monday to 5 pm (PDT) Tuesday.
Rule 3: Come back here and post a link in the comments so that I can find all the posts for the round up.
Rule 4: Don’t get yourself fired. Make sure that you either generalize your post or get permission to blog about anything from work.
Rule 5: If you roam the Twitterverse, then don’t forget to Tweet about your blog post with the hashtag #tsql2sday.
Rule 6: Go read someone else’s blog on the subject!
Final Rule: Have fun!