Data Warehouse Quality Assurance Best Practices
Collaboration between IT and the business will help identify the reasonable issues versus the issues that cannot be resolved for the current release of the data warehouse.
Compliance
The Sarbanes-Oxley act has become a four letter word to many IT people in the US. Thankfully I only had to deal with it for about 9 months before I left to go work on my own, but it was a long 9 months. Especially since I did half the work with JD Edwards and then did it again with Peoplesoft 🙁
Monitoring Disk Space and Sending Alerts with TSQL
Haidong discusses the importance of monitoring disk usage over a period of time and has some great TSQL code to help you do the monitoring!
Working Your SOX Off
The Sarbanes-Oxley act has drastically changed the jobs of many DBAs with the audit and reporting requirements this act entails. Brandie Tarvin brings us some hints about how you can go about complying with the new requirements.
SqlCredit – Part 9: Message Authentication Codes
This month's installment of "Developing a Complete SQL Server OLTP Database Project" covers searching encrypted data, dictionary attacks, and look-ups by hashed value.
The Puzzle of 'Rating Decomposition'
When reading rating information, how do you you knew how many points each separate voter gave if you only know the average rating and the number of votes? Well, you might be surprised to learn that you can figure it out using SQL
Conditional Statements in WHERE Clauses
T-SQL is a powerful language, enabling you to handle many different types of set based operations. But having flexible WHERE clauses isn't something that many DBAs deal with on a daily basis. New Author Sotiris Filippidis brings us an article on how you can structure a WHERE clause to handle all types of strange business logic without using dynamic SQL. Read on to learn more about his technique.
Moving the SQL 2005 System Databases
Most SQL Server instances are installed with the default values, but that's not always the way it should be. Often there is the need to "move" databases to comply with standards, free up disk space, or some other reason. Moving the system databases can be a little tricky, but author Vince Iacoboni brings us his code and technique for easily doing this for SQL Server 2005 databases.
Isolation Levels in SQL Server 2005
Isolation levels are used to prioritize the acccess to a resource. SQL Server 2005 extends upon the support for isolation levels in 2000 with several new features including an additional level.
Blogs
From Planning to Practice: Setting Up Your FinOps Framework
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
“We love to debate minutiae”
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
Advice I Like: Knots
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Forums
Restoring On Top II
Comments posted to this topic are about the item Restoring On Top II
SQL Art 2: St Patrick’s Day in SSMS (Shamrock + Pint + Pixel Text)
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Breaking Down Your Work
Comments posted to this topic are about the item Breaking Down Your Work
Question of the Day
Restoring On Top II
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers