Hello everyone.<BR><BR>I Have an application that creates some form of log in a SQL table that has an identity column.<BR><BR>An auditor checked these logs and found some gaps in the identity ...

I've got this view defined on two tables, one of which has an identity field that auto increments. There seems to be no way to insert into this view. If I leave the auto-increment field blank it ...

SQL Server has come a long way in the past 5 years, though the history seems to linger. Let's look at the recent history and see what the story is with database vulnerabilities.