Service Broker is a new feature in SQL Server 2005 that brings queuing and reliable messaging to SQL Server. Service Broker provides the “plumbing” to let you pass messages between applications, using SQL Server as the transport mechanism. Applications can use a single shared SQL Server database for this purpose or distribute their work across multiple databases.
We get Vincent Rainardi's "Data Warehouse Loading Part 2" article taking a look at how you can perform an "upsert" in your data warehouse.
SQL Server Management Studio is used to manage, query and design SQL Server solutions. In this video you're shown the basics of how to use Management Studio.
In this article, we will concentrate upon the useful IsLeaf() operator, from the perspective of its use within a calculation. We will discuss the straightforward purpose of the operator, to ascertain whether a member is a leaf-level member of a dimension; the manner in which IsLeaf() manages to do this; and ways we can leverage the operator to support effective conditional logic to meet various business needs within our own environments.
By doing a bit of groundwork and effectively controlling the scope of the metadata repository continuously throughout the project, few problems should arise.
After quite a few versions, Enterprise Manager is being retired. SQL Server 2005 will have a new management tool called the SQL Server Management Studio (SSMS). Amit Lohia brings us a first look at some of the features of this new tool.
The methodology helps identify the areas of slow performance by looking at the problem from two directions called Waits and Queues. An analysis of Waits indicates where SQL Server is spending lots of time waiting. In addition, the biggest waits point out the most important or relevant Queues (that is, Performance Monitor counters and other data) for this workload.
Data space can be a concern in many situations as more and more data is being stored in your systems. Designing your schema to take this into account is important for a DBA and Steve Jones takes a look at how design decisions can be used to solve a business problem.
Keeping track of the performance of your SQL Servers requires metrics. There are many methods for doing this, but some type of automated process is essential these days with DBAs managing many servers. New author Allen White brings us a technique for doing this using SMO, the replacement for DMO in SQL Server 2005.
XML really makes it easy to move data from here to there and from there to here. However, eventually the data needs to be stored somewhere, most likely in a relational database. Here is how Edmond Woychowsky gets data from an XML document into a relational database.
By Brian Kelley
But as I've matured over the years, I came to realize that I needed...
By alevyinroc
I will be presenting my latest session, Documenting Your Work for Worry-Free Vacations, in-person...
By Steve Jones
I saw a question asking about the next sequence value and decided to try...
I've got a table with 186,703,969 rows, about 300GB of data. There are several...
I created a SQL Database in Azure Portal but I've just noticed it also...
Comments posted to this topic are about the item An Unusual Identity
What values are returned when I run this code?
CREATE TABLE dbo.IdentityTest2
(
id NUMERIC(10,0) IDENTITY(10,10) PRIMARY KEY,
somevalue VARCHAR(20)
)
GO
INSERT dbo.IdentityTest2
(
somevalue
)
VALUES
( 'Steve')
, ('Bill')
GO
SELECT top 10
id
FROM dbo.IdentityTest2 See possible answers