Not generally. But CASE WHEN conditions are always evaluated serially (as far as returning a result is concerned), so in that...

Also, be sure the relevant non-DBAs properly enable IFI and other local/policy/Windows permissions that are needed for SQL accounts, proxy accounts, etc..

Yes, you can create a non-clustered index w/o a clustered index, but you (almost) never should.

The cluster key does not have to be defined as unique (SQL will internally make...

Honestly the DBA should have admin access to the server to have maximum effectiveness.

If you don't, and in particular if you don't have direct directory access/control, be extraordinarily careful before...

You can't have a

GO

within a stored procedure. The first GO ends the stored procedure definition.

Don't use a simple UNIQUE constraint. You have to define a primary key, and the only way it's really useful to your query is if the first column in...

I'd strongly urge you to use a character-based method rather than simply trying to CAST to numeric, which is almost certain to cause a non-numeric data exception.

SELECT valid_id, SUBSTRING(valid_no, PATINDEX('%[^0]%',...

Table variables don't ever get statistics.

Be sure to specify the appropriate clustering key on either table variables for temp tables. Than can make a vast difference in the performance...

rquest7 (6/22/2014)

---

While we were trying to purge the data in our SQL Standard database files ,the rows are not getting dropped or deleted from the NDF files and the transaction...

If you have time, add a rebuild step to your process:

1. I remove very old records:

DELETE FROM ArchiveDB..a_tblLog WHERE PKID < ?

1B. Rebuild a_tblLog table WITH ( FILLFACTOR =...

No, it does...

Taking a higher-level view, what's most important for performance of very large tables is making sure the clustered index is based on the best column(s). That can often eliminate...

Are you just trying to determine the relative Saturday# within the month? If so, there are methods with vastly less difficulty and overhead.

Does the read query use "WITH (NOLOCK)"?

Is snapshot isolation in use?

Minor correction:

t.TransactionDate >= 'Apr 2014' AND

t.TransactionDate < DATEADD(mm,1,'Apr 2014') --"<" rather than "<="