Jeff Moden (11/20/2014)

---

Sounds mean but my suggestion is that anyone that doesn't...

We're current users. If you have any questions about their software (or any other similar products) I'd prefer to answer privately for a number of reasons.

Well, I can guarantee you that no one hands over their Outlook data files because they're...

Hi...

Do you have your own,...

Luis Cazares (11/13/2014)

---

And there's another alternative based on "best practices" 🙂

DECLARE @PrVers NVARCHAR(128)

, @PrVersNum DECIMAL(10,2)

, @command NVARCHAR(4000)

SET @PrVers = CAST(SERVERPROPERTY('ProductVersion') AS NVARCHAR(128));

SELECT @PrVersNum = SUBSTRING(@PrVers, 1,CHARINDEX('.', @PrVers) + 1...

Eirikur Eiriksson (11/13/2014)

---

How about this

😎

USE tempdb;

GO

SET NOCOUNT ON;

DECLARE @PrVers NVARCHAR(128)

, @PrVersNum DECIMAL(10,2)

, @StageTable NVARCHAR(1024) = N''

SET @PrVers = CAST(SERVERPROPERTY('ProductVersion') AS NVARCHAR(128));

SELECT @PrVersNum = SUBSTRING(@PrVers, 1,CHARINDEX('.', @PrVers) + 1 )

PRINT...

Eirikur Eiriksson (11/13/2014)

---

Quick suggestion, not as elegant as Luis's but should work

😎

USE tempdb;

GO

SET NOCOUNT ON;

DECLARE @PrVers NVARCHAR(128)

, @PrVersNum DECIMAL(10,2)

, @StageTable NVARCHAR(1024) = N''

SET @PrVers = CAST(SERVERPROPERTY('ProductVersion') AS NVARCHAR(128));

SELECT @PrVersNum ...

Luis Cazares (11/13/2014)

---

What about creating the table and adding or dropping columns as needed?

Here's an example dropping the column to preserve the order and prevent confusing the Intellisense.

DECLARE @PrVers NVARCHAR(128)

,...

Alvin Ramard (11/13/2014)

---

g.britton (11/13/2014)

---

The temp table in the dynamic sql is created in a different context and not available to the calling context. e.g.

DECLARE @sql nvarchar(4000) = N'create...

Eirikur Eiriksson (10/25/2014)

---

sqldriver (10/25/2014)

---

Eirikur Eiriksson (10/25/2014)

---

You are on the right track there, a simple solution would be to "UPPER" the values before hashing. SHA1 is quite a lot cheaper computationally...

Eirikur Eiriksson (10/25/2014)

---

You are on the right track there, a simple solution would be to "UPPER" the values before hashing. SHA1 is quite a lot cheaper computationally than MD5 and...

Eirikur Eiriksson (10/25/2014)

---

An alternative solution which doesn't require any joining. It scales well for large sets but has a weakness of returning false positives although fairly unlikely with this type...

ChrisM@home (10/24/2014)

---

Sure. Have a good look at the actual...

Would you mind explaining some more about this part?

Thanks