For what it's worth, the @@ROWCOUNT system variable contains the number of rows affected by the immediately preceeding DML operation.

What is the first policy?

Especially for lower tier servers (ie: 4 CPU / 8 GB memory), or instances where the database engine is the only service running, it's hard to justify the OS memory...

comic_rage (11/16/2016)

---

was able to improve the query by moving the isnull to the select and adding the column to a filtered index. Was able to reduce query time from 9+...

comic_rage (11/16/2016)

---

Hi,

I have the following query that is returning 1.6 M rows and about 300 columns. I can't change this factor. Here is the current

query

select Column1 ... Column290

from dob.table1

where...

In T-SQL there is an IGNORE_DUP_KEY option that can be added to the primary key. Unlike MySQL's ON DUPLICATE keyword, it doesn't result in an update for a row with...

There are some good articles on this site related to event Auditing, including how to filter for specific types of operations and users. http://www.sqlservercentral.com/articles/Stairway+Series/130498/

You can also fall back to using...

Start with learning how to live up to your formal job description. Ask your immediate supervisor what's expected of you in terms of roles. You don't want to focus on...

When running sp_who2 or DMV queries from SSMS, rather than filtering on 'SA', perhaps excluding your own SPID is what you really want. It's entirely possible that another DBA (or...

When it comes to choice of database, it helps to understand that some platforms are much better suited for staging large amounts of data (ie: Hadoop or Cassandra), some databases...

This is a long shot, but assuming the user who executed the DELETE operation is still connection, and the last command they executed as the DELETE, then it should work....

https://mssqltalks.wordpress.com/2013/02/25/how-to-audit-login-to-my-sql-server-both-failed-and-successful/

Are the production staging tables to be entirely deleted (truncated), or will you delete only rows aged within a specific date range?

If you discover it to be a timing issue, and the job step can be repeated to completion, then consider going under Advanced properties of the step and setting it...

If MERGE isn't an option, then perhaps something like the following (pseudo-code of course). This way, if the row does happen to exist, then it's a single lookup.

UPDATE ... WHERE...