Please post table definitions, index definitions and execution plan, as per http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Why do you want a sample resume?

My guess is that you have parameter sniffing problems. Post the proc?

Why are you asking?

SAP's not dedicated to Oracle. It runs on SQL Server too.

Unrelated, other than they are both NTFS features.

Alternate streams: http://msdn.microsoft.com/en-us/library/ms810604.aspx (long document)

Sparse files: http://msdn.microsoft.com/en-us/library/aa365564%28VS.85%29.aspx (there's also info on sparse columns in the previous doc)

devesh.v19 (11/20/2009)

---

In reality I have over 10-15 of columns per table and I have over 30 of such tables in the database. Unfortnately the primary key indexing was done on...

That's a temporary fix. The create and drop publications is needed for a permanent fix if this is what I think it is (an imprperly cleaned up transactional replication publication)....

DISTINCT TOP 100 PERCENT .... ORDER BY????

Is the distinct really necessary?

Why the top 100 percent?

Please post table and index definitions.

Carolyn Stern (11/19/2009)

---

Now I think I discovered that if there is a primary "KEY" defined - and there is, then this becomes a clustered index. That's what I just...

Well, when you run that the table will be unavailable until that has completed. Is that what you were asking?

I'm obviously explaining badly.

What columns the primary key is on...

That's log...

http://sqlinthewild.co.za/index.php/2008/09/04/comparing-date-truncations/

It has nothing to do with the primary...

Then you just can't use the 'sync with backup' option. The replication itself will work.