don't join on names. try SSN and date of birth, or just SSN, and ignore names.

if you have nay otehr columns that uniquely idnetify a person(email, drivers license number, etc)...

Lowell (10/1/2014)

---

you are overthinking this if you think you need an app for that.

no "app" is needed for this, as the data entry for any app that tried to do...

Yes, I think it will be 2 options: use "smart" first name matching or by last name only

Jan Van der Eecken (6/18/2013)

---

May I humbly ask why you want to do this in the first place? My first name is Jan, which is both Dutch, Afrikaans and Polish...

Maybe its bug and we should notify Microsoft?

Can somebody at least reproduce issue?

Thanks guys,

Solution with "count(*) over" very nice

Alex.

We have single SQL instance on dedicated server. So recommended value is 8Gb.

Is there any possible issues can heppen if we keep it unchanged min =0 and max = 2147483647...

SQLkiwi (2/24/2011)

---

onixsoft (2/24/2011)

---

So now I have 2 choices: change Prod database to compatible mode SQL2005 and Parameterization = Forced or replace most used queries to use Stored Procedures instead dynamic...

Auto-parameterization work properly with Parm=Forced, and NonClustered Index for both your queries

but when I back to Parm=Simple both not work. It seems previously nothing worked because my database was...

SQLkiwi (2/24/2011)

---

I think I have a handle on this now, but I just want to be sure you see a successful auto-param in all cases (index, no index) for this...

And some more info:

1.

DB Compatible Level: SQL Server 2000

Parametereization: Simple

With NONCLUSTERED INDEX

Auto-param not work

DB Compatible Level: SQL Server 2000

Parametereization: Forced

With NONCLUSTERED INDEX

Auto-param not work

2.

DB Compatible Level: SQL Server...

If I understand you correctly, you are saying that auto-param worked fine until you created that non-clustered index. Is that correct? Auto-param works for me with and without...

Thanks Paul, I was able to recreate table structure and did some more research and found what following line turn autoparameterization off :

CREATE NONCLUSTERED INDEX [IDX_SSNHistory_IndID] ON [dbo].[SSNHistory] ([IndID]) ON...

SQLkiwi (2/24/2011)

---

If you run the IndId= GUID query from Management Studio, do you get an auto-parameterized plan? I would expect...