SQL Saturday #104 - Colorado Springs
Start your 2012 off right with a free day of training in Colorado Springs. Bring the kids as well, as the venue is very family friendly.
Start your 2012 off right with a free day of training in Colorado Springs. Bring the kids as well, as the venue is very family friendly.
The last Friday poll of 2011 has Steve Jones asking about what you want out of 2012.
Check out this tip to learn about the SELECT @@VERSION command in SQL Server.
SSIS features log-providers that can write to five different types of logging destinations; three of them are files, one is the 'dbo.sysssislog' table, and the last is the Windows Event Log.
There has been much debate over the need for the Lock Pages in Memory privilege, on 64-bit versions of SQL Server. Jonathan Kehayias presents a "warts and all" account of its history, the confusions surrounding its use, and why he believes it's still a good default configuration for 64-bit SQL Server instances, even when running Windows Server 2008 and Windows Server 2008R2.
Users often have a certain expectation of privacy about their data in applications, and as software engineers, Steve Jones thinks we need to respect that.
This blog, explores ideas for extending SQL Server with new, fast hash functions. As will be shown, the high speed, built in functions CHECKSUM and BINARY_CHECKSUM are not always optimal hash functions, when you require the function to spread data evenly over an integer space.
Be carefull when replacing a defective (FLASH) storage device, its sector sizes may vary without you knowing it.
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
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