Your initial query was impossible:

WHERE (table.FID IN (359890) OR

(table.FID IN (N'19508e3b-0595-41cf-88f2-c13141e0bc40')

but the query plan cleared it up: the second column is a different column from the first one.

Don't forget the other side of the issue.

Have you compressed large indexes when useful?

Have you reviewed that you have the best clustered index on each table? After that, have...

ramana3327 (12/11/2014)

---

I am re-framing my requirement.

We have a team working as DBA (Offshore). We have 5 user databases. One database has the secure data and doesn't to reveal the data...

You could build a concatenated string containing all the executions, then EXEC() that string. The issue would be if errors occurred during processing.

Yes. It's easy, just like it sounds: create the...

Please list all indexes on [BuildTable].

Also, shouldn't the SecondApply query have a condition based on FirstApply value, something like:

WHERE [BuildTable].[rownum] > [FirstApply].[rownum]

?

Edit: Added "WHERE" for clarity.

My approach below. I added a phone_id to the phone#s in the tables so I could join and show the expected output in the same query as the original...

Not necessarily. It depends...

SELECT DISTINCT m1.*

FROM Matches m1

WHERE

EXISTS(

SELECT 1

FROM Matches m2

...

SELECT time_int, CAST(DATEADD(MINUTE, time_int / 100 * 60 + time_int % 100, 0) AS time) AS time

FROM (

SELECT 0 AS time_int UNION ALL

...

If you (almost) always do lookups on the table based on "businessid", then cluster the table on businessid. If you need to keep the PK, make the PK nonclustered...

BWFC (12/4/2014)

---

ScottPletcher (12/3/2014)

---

BWFC (11/27/2014)

---

You're welcome.

One other thing, be careful using BETWEEN for date range queries. You're usually better using

where

[Date] >= @startdate

and

[Date] <= @enddate

Have a look at...

If you're not using service broker any more, then it's 100% safe to run this:

ALTER DATABASE msdb SET NEW_BROKER

which should clear that table and allow you to release the space.

BWFC (11/27/2014)

---

You're welcome.

One other thing, be careful using BETWEEN for date range queries. You're usually better using

where

[Date] >= @startdate

and

[Date] <= @enddate

Have a look at this...

To avoid rows already being modified, you can use the READPAST hint. That's often used for work-queue-type processing. If you can use that, there's no good reason to...