If you make the decision to upgrade to 2008, there are a number of tools that make the process easier, but you still need to understand what things you should consider. We have a new article from Arshad Ali to help you understand the process and what you should consider.
This Friday Steve Jones wonders what types of bugs you find in software. Are there more prevalent because of design or coding?
Research firm The 451 Group coins "NewSQL" to categorize a new breed of database designed for distributed environments -- like the cloud.
Monitoring blocking can be problematic when you cannot catch it in the act. This article will show you an easy way to configure a SQL Server Profiler Trace to monitor blocking
Today we have a guest editorial from Andy Warren. Most people get an annual review that determines what their salary change might be for the next year. Does 3% make a difference? Andy Warren asks the question today.
SQL Server 2008 introduced many new functional and performance improvements for data warehousing, and SQL Server 2008 R2 includes all these and more. This paper discusses how to use SQL Server 2008 R2 to get great performance as your data warehouse scales up. We present lessons learned during extensive internal data warehouse testing on a 64-core HP Integrity Superdome during the development of the SQL Server 2008 release, and via production experience with large-scale SQL Server customers. Our testing indicates that many customers can expect their performance to nearly double on the same hardware they are currently using, merely by upgrading to SQL Server 2008 R2 from SQL Server 2005 or earlier, and compressing their fact tables. We cover techniques to improve manageability and performance at high-scale, encompassing data loading (extract, transform, load), query processing, partitioning, index maintenance, indexed view (aggregate) management, and backup and restore.
What do yo do if you find malicious code in your system? Delete it? Steve Jones suggests that a honeypot might be a better idea.
With each revision, SharePoint becomes more a SQL Server Database application, with everything that implies for planning and deployment. There are advantages to this: SharePoint can make use of mirroring, data-compression and remote BLOB storage. It can employ advanced tools such as data file compression, and object-level restore. DBAs can employ familiar techniques to speed SharePoint applications. Bert explains the way that SharePoint and SQL Server interact.
Service Broker is a great feature that allows you to defer processing in SQL Server. Learn how you can have processes work together, but in an asynchronous fashion in this piece from Gary Strange.
Would you rather work longer hours or tackle harder work? Steve Jones comments today on a recent post by Seth Godin. The answer as to what most people prefer might surprise you.
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