I have a MUCH better idea: Use WITH SCHEMABINDING on EVERY object you ever create in SQL Server where it is allowed. I hope you will find that this will...

Key point here is to avoid putting INSERTED data into VARIABLES!! This is a CRITICAL FLAW because triggers fire once per BATCH, not PER ROW! Very common mistake.

I actually...

Review Books Online for sp_executesql. BOL is a GREAT resource!!!

If you don't have to guarantee that each powershell script fires off the EXACT moment you start it, nor that everything be in some kind of huge distributed transaction, then...

Visio works, but IIRC in the more recent versions it can no longer do reverse-engineering, which TOTALLY sucks!!

My favorite tool for database (and all other DEV/IT Pro modeling) BY FAR...

bcatty13 (1/7/2016)

---

I have a 2-Node SQL 2014 cluster running on (2) Server 2012R2 nodes. These are virtual machines sitting on a 2-node ESX5.5 cluster (vSphere5.5). Each node has 16GB RAM...

No worries. Send me a PM and I will get you my email address and we can get something set up. We can start with Common TSQL Mistakes and hopefully...

Ed Wagner (1/5/2016)

---

benjamin.reyes (1/5/2016)

---

This is the nifty old utility talked about in this article.

http://www.sqlservercentral.com/blogs/chadmiller/2010/05/15/sql-agent-visual-job-schedule-viewer/

It seems the company and the website no longer exist. Through replacement of several desktops...

Wayne West (1/5/2016)

---

TheSQLGuru (12/25/2015)

---

Jason A. Long (12/25/2015)

---

TheSQLGuru (12/25/2015)

---

How about I do a remote presentation of my Common TSQL Mistakes session? I have presented it somewhere around 100 times now for...

Not even for Check Constraints since you can get bad data. Search for sql server udf check constraint bug and you can go here: http://sqlblog.com/blogs/tibor_karaszi/archive/2009/12/17/be-careful-with-constraints-calling-udfs.aspx

Addressing someone else's comment about...

lucien.jacquet (1/4/2016)

---

My point is not to contradict your assertion that scalar functions "can be" expensive, but to suggest that your example is a worst-case scenario. Is it possible that your...

1) UDFs existed at least as early as SQL 2000: https://technet.microsoft.com/en-us/library/aa175085(v=sql.80).aspx

2) This article fails to mention an EXCEPTIONALLY important flaw (among many others that aren't covered such as preventing the...

Scalar UDFs are HORRIBLY HORRIBLY BAD!!! Take the logic out and either inline it in your SELECT or make it an INLINE Table Valued Function and go with that. I...

Jeff Moden (1/2/2016)

---

This could actually be a pretty simple thing to solve using either a self-joined re-enumerated table or the difference between two ROW_NUMBER()s. My recommendation is that you...

I am going to address what could be a root flaw here WAY more important than (re)compilations: if you are using Scalar or Multi-Statement UDFs THEY MUST GO!!! There is...