SQL Server allows data access from many sources, probably any that you could want. Some, however, are easier than others. Have you ever tried to update information in Exchange from SQL Server? Not that easy, but new author Steve Boriotti has written code as well as a short article on how you can make this happen.
In this article, I will show you how to leverage the Reporting Services unique extensible architecture to supercharge your report capabilities. First, I will explain how embedded and custom code options work. Next, I will show you how you can leverage custom code to author an advanced report with sales forecasting features.
Andy has some examples of not very high tech solutions that involve some technology behind the scenes, but the binding factor was that someone had to see the problem first, and it wasn't one of those show stopper type problems. It's not about SQL, but we think it is on topic.
This article focuses on a common problem associated with conflicting locks: blocking. When blocking occurs, a single connection blocks all other connections from reading or modifying a particular piece of data. Learn here how to resolve these issues.
Working with a QA server in SQL Server 2000 is something everyone should learn to do. Having some staging area between development and production will help ensure a more stable environment and smoother deployments. After a little hiatus, Steve Jones continues with this series looking at moving the latest backup over to QA.
This article looks at the basics of storage design for cubes using Analysis services. A good starting point for those getting into the use of analysis services.
Akeel Din has written an introductory SQL book that is available for free in PDF form. It's also available in print from Amazon if you like holding something real in your hands.
A basic look at how you can start to build a data warehouse. This has some basics you need to do the design of the various fact and dimension tables.
It was an adventure. Moving a SQL Server physically from one location to another should be a simple process, but it turned out to be a bit more than Steve expected. Read about the adventure and inject a little humor into your day.
Just because a column has an index doesn't mean the SQL Server Query Analyzer will use it. Learn how to create indexes SQL Server will use.
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