Are you mad? Not angry, more like crazy when it comes to designing databases in SQL Server? Don Peterson has met a few people he thinks are just that when it comes to building lookup tables. Does it stem from poor understanding of database design? Or do you disagree? Read Don's case against this particular design practice.
Gartner has stated in the past that "configuration management is at the very heart of IT service management." What do you mean by this?
There are a few upcoming SQL\SSIS\Developer events coming up in the next week. Andy Warren and Brian Knight will be speaking at Code Camp in Orlando (a free full day event) and Brian will be doing a SSIS event in Philadelphia. For more information, see this blog post.
You may be wonderfully up-to-date with an AJAX Web interface or the latest whizbang Windows user interface, but under the covers, you're probably still pumping data in and out of a database, just as we all did a decade or more ago. That makes it all the more surprising that developers are still making the same database mistakes that date back to those good old days of Windows 95 and before.
There are many changes in SQL Server with the release of SQL Server 2005, but none more telling than the client tool used to manage your servers. Check out this new e-book for learning about SQL Server 2005 Management Studio form SQLServerCentral.com.
It is an interesting question and one I hope every DBA can answer positively. New author Thomas LaRock brings us his method for ensuring that the backups have occurred and the files are still on disk.
One of the best programmers I ever met was referred to, in Essex jargon, as being ‘two stops short of Dagenham’ (Barking)*. This was once no obstacle to the world of work…the best development teams I’ve worked on embraced the whole gamut of humanity
Impressions of this new book from Brian Kelley.
Security support in the .NET Framework got a lot of love in version 2.0, and this column is going to take you on a whirlwind tour of the goodies you'll find there. I won't be able to cover everything, but you'll know where to start looking to stay on top of the new changes. I'll take this a namespace at a time.
Every DBA needs a few tricks up his/her sleeves to help them better manage their SQL Server 2000 environment. In this article I will explore a couple of such tricks. I will first explore how to cycle the SQL Server error log, and why you might want to do this. Secondly I will discuss backup history information and why you would need to periodically remove some of the older history information.
By Steve Jones
I come to Heathrow often. Today is likely somewhere close to 60 trips to...
By Brian Kelley
If your organization is spending money, then meaningful results are a must. Pen testing...
By HeyMo0sh
In my experience, FinOps success has never been just about tools or dashboards. It...
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