CELKO (4/22/2015)

---

Please read any book on basic data modelling and look at the chapters on scales and measurements....

Orlando Colamatteo (4/22/2015)

---

ScottPletcher (4/22/2015)

---

Orlando Colamatteo (4/22/2015)

---

I'll second the point: definitely store your dates and times in a column of type DATETIME. If you make that a non-negotiable starting point the...

Eric M Russell (4/22/2015)

---

ScottPletcher (4/22/2015)

---

Eric M Russell (4/22/2015)

---

ScottPletcher (4/22/2015)

---

With an existing table, you already know what the length of the columns will be, whether varchar or not. The formula...

Eric M Russell (4/22/2015)

---

ScottPletcher (4/22/2015)

---

With an existing table, you already know what the length of the columns will be, whether varchar or not. The formula provides you with the...

With an existing table, you already know what the length of the columns will be, whether varchar or not. The formula provides you with the additional overhead SQL requires...

It has to be the pointy-haired boss types that hire Celko. No one who actually knew any practical implementations would ever change obvious numeric values to character. There'd...

SELECT

crtdte,

ISNULL(CAST(NULLIF(minutes_ago / 1440, 0) AS varchar(5)) + ' days, ', '') +

ISNULL(CAST(NULLIF(minutes_ago % 1440 / 60, 0)...

Books Online has very specific formulas for how to do that, under:

"Estimating the Size of a Nonclustered Index"

This should definitely be faster. I've tested it for ASC sort but not for DESC -- I believe I've coded it to correctly handle DESC sort, I just haven't...

Orlando Colamatteo (4/22/2015)

---

I'll second the point: definitely store your dates and times in a column of type DATETIME. If you make that a non-negotiable starting point the rest of this...

As an aside, if possible, TRUNCATE the table rather than use DELETE to reduce logging.

Mark Finnie (4/21/2015)

---

Thank you Scott. I had to replace TableName with TblName becuase some audit tables had columns with that name, resulting in ambiguous column name errors. The query then...

Code below could perform better, esp. if table2 and table3 don't have an index that directly supports the lookup/comparison being done.

Edit: And performance could be worse with this code ......

Another perfect situation for a tally table. You can create an in-line table using CROSS JOINs or create a physical tally table and use that. Unfortunately I can't...

I used CASE rather than ORs ;-).

SET NOCOUNT ON

--Temp table DROP/CREATE, in alpha order--------------------------------------------------------------------------------

IF OBJECT_ID('tempdb.dbo.#CheckTables') IS NOT NULL DROP TABLE #CheckTables

IF OBJECT_ID('tempdb.dbo.#Results') IS NOT NULL DROP TABLE #Results

CREATE TABLE #CheckTables...