Basics of Statistics in SQL Server 2005
If you're having a problem with particular queries, there are a few things you can do with the information that the server collects about the distribution of data in columns and indexes.
Getting Started with SQL Server Service Broker
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.
Upsert Dimension Table
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.
Introduction to SQL Server Management Studio
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.
MDX Operators: The IsLeaf() Operator: Conditional Logic within Calcula
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.
Avoiding the Metadata Pitfalls
By doing a bit of groundwork and effectively controlling the scope of the metadata repository continuously throughout the project, few problems should arise.
SQL Server Management Studio
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.
SQL Server 2005 Waits and Queues
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.
Our Very Own SQL Server Data Compression
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.
Gathering Metrics with SMO
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.
Blogs
T-SQL Tuesday #192: What career risks have you taken?
By James Serra
I’m honored to be hosting T-SQL Tuesday — edition #192. For those who may...
AI: Blog a Day – Day 3: LLM Models – Open Source vs Closed Source
By Vinay Thakur
Continuing from Day 2 , we learned introduction on Generative AI and Agentic AI,...
How to Parameterize Fabric Linked Services in Azure Data Factory for Azure Devops Deployment
Quite the title, so let me set the stage first. You have an Azure...
Forums
A Quick Restore
Comments posted to this topic are about the item A Quick Restore
Guarding Against SQL Injection at the Database Layer (SQL Server)
Comments posted to this topic are about the item Guarding Against SQL Injection at...
Ola Hallengren Index Optimize Maintenance can we have data compression = page
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
Question of the Day
A Quick Restore
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers