Linchi Shea : Bad database practices

Bad database practices: allowing apps to connect to the server hostname

Linchi Shea — Mon, 28 Dec 2009 20:32:00 GMT

It’s common to see a client application referencing the hostname of a SQL Server instance in its connection string. For instance, assume that you have a server whose hostname is NYCSQL01, and you install a default SQL Server instance on it. Naturally,...(read more)

Bad database practices: abusing linked servers

Linchi Shea — Sat, 07 Nov 2009 00:56:00 GMT

In SQL Server, it is rather handy to retrieve data from a different SQL Server instance and use the result locally in another SQL statement for further processing. In theory and in the set purists’ fantasy land, it shouldn’t matter where you get your...(read more)

Bad database practices: moving data to procedures vs. moving procedures to data

Linchi Shea — Fri, 30 Oct 2009 04:00:00 GMT

Is it better to move data to procedures or move procedures to data? The answer is, of course, “it depends.” Let’s consider a scenario where you have two SQL Server instances: ServerA and ServerB, and you have a procedure on ServerB (call it procB), but...(read more)

Bad database practices: managing databases without a DBA central inventory

Linchi Shea — Tue, 20 Oct 2009 17:26:00 GMT

Aaron Bertrand has been writing an excellent series about Bad habits to kick , highlighting some of the bad practices, primarily, in the areas of T-SQL coding. I’m going to steal his idea and comment on the bad practices I have seen in managing databases....(read more)