Indeed, you will need to install two updates - the latest SP and the latest CU.  For SQL Server 2017 and later it's more simple - there are no SPs,...

Work your way through this, and post back if there's anything in particular you don't understand.

John

Yes, write a query to identify any such duplicates.  Put it in a job and use Database Mail to notify the user if duplicates are found.

I have to ask, would...

A trigger on the table - would that work?

John

Which analytic function has violated your restriction?  What is the reason for the restriction?  If, as I suspect, it's because this is a homework question, please show us what...

I can't see why that wouldn't work.  But don't take my word for it - have you actually tried it?  Bear in mind that sp_MSForEachTable is an undocumented stored procedure. ...

Yes, the constraint prevents orphaned rows in the child table - in other words it stops children having their parent deleted.  What it doesn't do is stop a parent having...

I think you have two choices: (1) you can't delete any row in the parent table while related rows exist in the child table, or (2) you create the foreign...

What have you already tried?  The FIRST_VALUE function may help you here.

John

Have you read the documentation, and was there anything in particular you didn't understand?

John

Depending on your precise requirement, you might also consider Change Data Capture and Temporal Tables.

John

Really?  You've been asking questions on here for about nine years.

How did your production database come to be more updated than the development one? ...

Q1 You can use Extended Events, but there's a ready-baked SQL Audit feature that it would be easier for you to use.

Q2 Are you talking about a particular database, or...

Audit is indeed available in Standard Edition, going all the way back to (at least) SQL Server 2008 R2.  Granted, it's only for server-level events, but I think that will...

• This reply was modified 5 years, 9 months ago by John Mitchell-245523. Reason: Crossed out what I said, because it's wrong. Audit was only available in Enterprise Edition when it was first introduced

Alternatively, stop using the errorlog to capture login events and use SQL Audit or an Extended Events session instead.  That way, you can control with fine granularity what you keep...