SSIS Package Configuration in SQL Server 2005
SQL Server 2005 allows DBAs to set configurations for SSIS packages outside the package to facilitate a smooth transition between different environments.
Stop SQL Injection Attacks Before They Stop You
This article discusses: How SQL injection attacks work, Testing for vulnerabilities, Validating user input, Using .NET features to prevent attacks, and Importance of handling exceptions
Getting The Most Out of SQL Server 2005 UDTs and UDAs
The CLR integration in SQL Server 2005 greatly expands on the capabilities of the SQL Server platform. One new area is the ability to build user-defined types and user-defined aggregates. Solomon Rutzky brings us a way to get around some of the limitations in this area with his SQL# toolkit.
Opening Day
Today is the opening day for the PASS conference here in Denver and it's kind of exciting. As many of you read this, I've hopefully gotten Simon Galbraith, owner of Red Gate software, and my boss, out here at the ranch shoveling manure. He's anxious to get on the ATV for a ride, so maybe I can work out a deal to reduce my workload 🙂
Close These Loopholes - Testing Database Modifications
In the latest in their popular series on 'Unit Testing' database development work , Alex K and Alex S give some examples of unit testing Database Modifications
Upgrading to SQL Server 2005: A dozen must-have tips
We've compiled a list of our dozen most popular tips in the area of upgrading to SQL Server 2005 and they run the gamut.
From DBA to DWA
Everyone wants to know what a DBA does and it is becoming a hard question to answer as the responsibilities and capabilities of database platforms increase. Longtime author Vincent Rainardi brings us the proposition of a new type fo DBA, one that focuses more on data warehousing.
Indy Tech Fest
There's a free event in Indianapolis for SQL and .NET developers. It's on October 13th and it's jointly sponsored by the .NET and SQL users groups. If you're in the area reigster and support this group.
Oh Lawd, it's the end of the world
There have been some strange things that have happened in this world that I would never have expected. The Red Sox winning the World Series, Macs with Intel processors, and are things I never thought I'd see. But none of the them seems as strange as this to me.
Unethical or Just Sneaky
One of the fundamental rules of a stable, controlled production system is that you apply updates singly, after they've been tested, and you document the change. This way you can ensure that if a problem occurs, you can do some backtracking to see what might have caused instability.
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