Auditing is becoming more and more important in many SQL Server environments. DBAs are being tasked with setting up, maintaining, and reporting on audit data. Author Leo Peysakhovich brings us one of his solutions to automatically generate an audit trail for your data.
There have been quite a few impressions of the PASS conference from our blogs, but here's another from Haidong "Alex" Ji, oneo f our longtime authors and a guest of SQLServerCentral.com at the Summit.
If a hacker sets sights on your SQL Server, there are four primary methods he can use to take control and carry out unauthorized, malicious activity. I will look at each of these: Password compromise, Account compromise, SQL injection, Buffer overflows
It just ended, but Chris Hedgate filed a report from the airplane as he sped home at 30,000ft across the Atlantic.
Steve Jones takes a moment to talk about the SQLServerCentral.com reception at the Summit last week. And a few pictures as well. Whether you were there or not, see what you missed and what you can look forward to next year.
That certainly is a mouthful, but it boils down to author Michael Coles implementation of a sound matching search for SQL Server 2005. Another mouthful, but if you are interested in getting close matches because your clients cannot spell, you might want to read this one.
Throughout this and other of my series, we have examined parameterization and parameter picklist support. While my focus has often been support of picklists using datasets generated through MDX queries against the cube under consideration, I have often found myself in client engagement scenarios where differing reporting requirements, as well as various "exceptions," drive a need to extend picklist support beyond the capabilities of the basic MDX queries that we have examined.
Auditing SQL Server, or any system, is not an easy task and with new regulations like Sarbanes-Oxley, it is becoming a full time job in some environments. Chad Miller brings us a way that he developed with Excel and some scripting to automate some of the security information for a large installation of SQL Servers.
When most DW designers begin developing a data warehouse, the Time dimension is the first dimension reviewed with the users. There are usually two or three different persectives on what the Time dimension should represent but, for the most part, it will be used for such calculations as Year-to-date Sales, Monthly Inventory Churn, etc. What most users are actually describing is a Date, or Calendar dimension.
As your SQL Server applications grow, chances are that you have more and more objects, especially stored procedures that you need to keep track of. An organized environment is key to being able to prevent the duplication of code and effort. Joe Sack brings us a look at how he names stored procedures to easy identification.
By Steve Jones
I coach volleyball and I do a lot of stat stuff on paper. I...
By Steve Jones
dolorblindness – n. the frustration that you’ll never be able to understand another person’s...
By Steve Jones
I had a customer ask about analyzing their Test Data Manager (TDM) usage to...
Is there a good syllabus for reading these two together? (Yes, it's called the...
Comments posted to this topic are about the item GPX distance and time analysis...
Comments posted to this topic are about the item The DBA is Dead; Long...
In SQL Server 2025, if I want to remove an IP from a listener, what do I do?
See possible answers