Connect Digest : 2009-10-30

Light helping this week.  I am busy closing out a few projects (or at least chapters within projects) in preparation for PASS next week. ======================================== #506453 : Lock escalation no longer kicks in for INSERTs in SQL Server 2008 Adam found a nasty lock escalation bug in SQL Server 2008.  […]

Connect digest : 2009-10-25

Here is your weekly helping of Connect goodness.  I added two items from the Connect connection, and an item from the Visual Studio connection. ================================================= #500228 : Default Data Location Not Being Written To Registry I was affected by this issue just yesterday, where I had set my default data […]

Run into me at PASS, and you could win a prize!

If you're planning on attending PASS, you should consider playing Twitter Bingo (put on by Quest).  Basically, you will get a randomized card with names and avatars of 25 Twitter users who post about or are otherwise involved with PASS and/or SQL Server.  In order to mark off a square, […]

New Cumulative Updates for SQL Server 2005 SP2 / SP3

Some new updates just posted by SQL Server Release Services: For SQL Server 2005 SP2, build 9.0.3355: For SQL Server 2005 SP3, build 9.00.4266: On first glance, it does not appear that the security updates last week were included in the hotfix for SP2.  (See Jonathan's post.)

Connect digest : 2009-10-17

I've been fairly distracted this past week with my "Bad habits to kick" series, so apologies for being so late with the Connect digest.  I stumbled upon a few pretty interesting items from the past two weeks; I hope you find them interesting as well. #498082 : Allow direct usage […]

Bad habits to kick : mis-handling date / range queries

In my last post in this series, I talked about using user-defined data types (alias types).  Today I wanted to discuss many of the ways in which people subject their date and time columns to very inappropriate query methodologies.  UPDATE February 13, 2015: Webucator, a provider of SQL Server training, […]

Bad habits to kick : using alias types

In my last post in this series, I talked about using the visual designers in SSMS.  This time, I wanted to treat the use of alias types. To clarify what I am talking about here, alias types used to be called "user-defined data types."  Then, when CLR came around in […]

Bad habits to kick : using the visual designers

In my last post in this series, I talked about abusing triggers.  This time I thought I would focus a bit on using the visual designers in SSMS.  Table Designer My biggest problem with the Table Designer : many changes you make can force SQL Server to rebuild the table.  […]

Bad habits to kick : abusing triggers

In my last post in this series, I talked about choosing inappropriate data types.  This time, I want to touch on a few ways that I see triggers being misused.  Using a trigger at all A lot of people think that they need a trigger.  They allow direct access to […]

Bad habits to kick : choosing the wrong data type

In my last post in this series, I talked about the assumptions many people make about IDENTITY columns.  In this post, I want to focus on choosing data types.  There are several areas where I see frequent mistakes in data type choice, and I'll mention a few here. Using CHAR […]

Bad habits to kick : making assumptions about IDENTITY

In my last post in this series, I talked about inconsistent naming conventions.  This time I want to talk about a few of the assumptions people make when using IDENTITY columns, and what kind of trouble they can cause. IDENTITY will prevent gaps A lot of people choose IDENTITY as […]

Bad habits to kick : inconsistent naming conventions

In my last post in this series, I talked about using the schema prefix, with particular focus on dbo-only systems.  In this post, I want to treat the use of inconsistent naming conventions. Stored Procedures In one of the systems I've inherited, we have stored procedures written by different people […]