The table does not have an index that I can use to speed up the join and I have tried using a where in clause so there is no Cartesian...

Seems like the obvious answer is to filter out the days where a table has no records. You could just use LAG() to get the previous recorded day's record count....

Not totally sure I understand your question, but if you're wondering how to get the data from your stored procedure into Excel, it's pretty easy.

Go to Data tab, Get Data,...

Well, here's a start at least...

Pros and cons of six SQL table tools – SQLServerCentral

Okay, I feel stupid. I'm thinking I should be able to do this using a CTE and and update query. Would I have to convert this to a table-valued function...

You need to use CROSS APPLY for this... the standard way of doing it (I'm gonna cheat and use Products and SalesLineItems) is like this:

SELECT p.ProductName, ca.SalePrice, ca.SalesQty, ca.SaleDate

FROM Products...

Thanks Steve. Just wanted to geocode a bunch of addresses in my database.

Not 100% sure this works... but it should at least give you some ideas... If you use LAG(), you can get the "previous" record (in time order) and see if...

If you're trying to do an exact match, it's just:

WHERE [ColumnName] = 'LifeCare Amb MH'

Starts with and ends with is easy:

WHERE [ColumnName] LIKE 'LifeCare Amb MH%'

WHERE [ColumnName] LIKE '%LifeCare Amb...

Are you searching for an exact match or just records that contain "LifeCare Amb MH"?

Since you didn't provide any consumable data, it's hard(er) to figure out what the problem is....

Without CREATE TABLE and CREATE INDEX scripts and the actual execution plan, there's not much anybody here will be able to suggest, I don't think.

Did you not see Steve Collins' answer?

What's the point of reposting the question verbatim in as different thread?

sys.all_objects will give you tables and views, and sys.all_columns will give you column names and type info etc.

• This reply was modified 4 years, 6 months ago by pietlinden.

Okay this is confusing. You're using both a windowing function and GROUP BY.  I don't think that's right. If all you're doing is looking for duplicates, the simple pattern is...

well, when I ran the CREATE TABLE and INSERT scripts, nothing happened, so I couldn't reproduce the problem.