I suggest adding a computed column to the table to determine the value: then the definition is only one place, and is thus very easy to change everywhere:

ALTER TABLE dbo.tablename...

The code's not really ready to be used in dev or QA either.

NO reason to search the same table multiple times, esp. not once per column.

Instead, should do a single...

Here's T-SQL code to generate the full @decode_string:

DECLARE @decode_string char(2055)

;WITH

cteDigits AS (

SELECT 0 AS digit UNION ALL SELECT 1 UNION ALL SELECT 2 UNION ALL SELECT...

The @decode_string needs a slight adjustment, moving the decode value for "255" to the end of the string.

As there's really no need to recompute the string every time, let's just...

I don't think it's really that complex.

I suggest a single lookup/"decode" string, with eight bytes per ip code; I'd also use a leading 7 "filler" 🙂 bytes, just to make...

dr.mannhattan (4/9/2013)

---

ROUND(ISNULL ((SL2.Importe - SL2.Propina - SL2.ScAmt) -((SL2.Importe - SL2.Propina - SL2.ScAmt)/ 1.16),0), 2, 1) As ImpIVA, --the final ", 1" on the ROUND function "tells" it to truncate,...

SQL will automatically cast the result to the receiving data type; cast will automatically round.

To prevent rounding, you can explicitly use the ROUND function yourself (kinda ironic):

ROUND(ISNULL ((SL2.Importe - SL2.Propina...

Turn on trace flag 1222:

DBCC TRACEON ( 1222, -1 )

Then when a deadlock occurs, SQL will put detailed info about the deadlock into the SQL error log.

Rebooting will not help...

rarascon (4/9/2013)

---

One more thing, I did wind up having to add a new column, because as Sean mentioned the original column as varchar is always going to be a thorn...

STUFF(TheDate, 3, 0, '/01')

Would convert 'mm/yyyy' to 'mm/01/yyyy'. You could then use it as a date, either implicitly (somewhat risky) or explicitly, 100% safe but you have to use...

I don't think that's true. If it is, it violates...

In SQL Server, temporary tables start with # or ##, such as #table or ##table.

IIRC:

SQL will automatically destroy # tables when the connection ends.

For ## tables, under SQL 2005 and...

Lynn Pettis (4/4/2013)

---

ScottPletcher (4/4/2013)

---

Lynn Pettis (4/4/2013)

---

Not saying I am right or wrong. I wanted a straight answer to a straight question: Is it a problem to lose the data...

Lynn Pettis (4/4/2013)

---

Not saying I am right or wrong. I wanted a straight answer to a straight question: Is it a problem to lose the data if there is...

Lynn Pettis (4/4/2013)

---

ScottPletcher (4/4/2013)

---

Lynn Pettis (4/4/2013)

---

ScottPletcher (4/4/2013)

---

You're vastly more likely to lose a single connection than have the entire instance go down, which would kill a temp table from that...