Slight error in that previous code section...... This is correct

DECLARE @RangeDivisor FLOAT

SET @RangeDivisor = 1609.344;

DECLARE @MyLatitude NUMERIC(9, 6), @MyLongitude NUMERIC(9, 6)

Set @MyLatitude = 42.430883;

Set @MyLongitude = -82.923642;

create...

Thanks

But I found another way.... The answers that I am getting are different when I do your way vs this way. I think I will go with the...

if exists

(

select *

from sys.objects

where

...

Ahhh....

Found it ....

http://www.sqlservercentral.com/articles/T-SQL/66987/

I looked in my past posts and a person by the name of LOWELL had sent me a reply.

Yep this works, I used this already.

But yes, that script ( Actually I had someone from this forum send it to me sometime in the past ) does the job...

No help needed ..

figured that.... YEP using GOOGLE services.. Works well! Great Stuff!

No responses needed....

Please ignore this...

The above syntax works perfectly.... I looked closely and found a field that had different values.

So we are good to go...

No need

Found answer....

DECLARE @id INT

SET @id = 0

UPDATE accounts2

SET @id = id = @id + 1

GO

Let me start fresh here....BTW-- I commented out the first query

Lets forget the first query.. That takes only taking 90 milliseconds.. Ignore that for now.

This is what is taking 4...

Ahh I found a way to reduce the time...

1.) Remove the DISTINCT ... Why ? The UNION operator always will return the distinct rows. I ran a little...

Now sure what spilling sort means ?

But yes the second returns 4719 rows...

Time taken by first query = Anywhere from 13 to 52 milli seconds. ( I hit the execute button a several times )

Also the hinstp has only 479 records......

USE [EDITransferICD10]

GO

/****** Object: Table [dbo].[HINSTP] Script Date: 10/2/2015 12:02:53 PM ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

SET ANSI_PADDING ON

GO

CREATE TABLE [dbo].[HINSTP](

[ADMDT] [decimal](8, 0) NOT NULL,

[FORMN] [varchar](8) NOT NULL,

[MBRNO]...

Need some help here... I am new to the finetuning business..

I have attached the stored proc code...

The entire stored proc gets run under 3 seconds.. I am in the...

Not clear what you mean ?

Should I drop the PRIMARY key and CREATE AGAIN ?