SQL Server includes a great auditing tool: Profiler. It's not the easiest tool to use, however, and it's one that takes some getting used to. Our resident security export, Brian Kelley looks at a simple example of using this tool to audit logins.
2007-10-02 (first published: 2004-09-01)
35,411 reads
2004-08-30
2,365 reads
2004-08-25
2,357 reads
2004-08-24
2,273 reads
2004-08-23
2,321 reads
2004-08-20
2,211 reads
2004-08-19
2,240 reads
Part 2 of Steve Jones' series on beginning SQL Server from the perspective of a system administrator or someone not used to working with SQL Server. If you've been designated the new administrator, take a look at this series for some help in coming up to speed on this product.
2007-10-02 (first published: 2004-08-19)
36,220 reads
2004-08-12
2,059 reads
2004-08-11
2,288 reads
By Vinay Thakur
I wrote about TempDB Internals and understand that Tempdb plays very important role on...
By Vinay Thakur
continuing from Day 1 where we covered the history of AI and GPT family,...
Comments posted to this topic are about the item A Quick Restore
Comments posted to this topic are about the item Guarding Against SQL Injection at...
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers