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.
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.
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.
If you’ve been watching AI roll through the data community and thinking, “this seems...
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
It is Friday, the queries are running, and nobody is watching the bill. That...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Hi All I am trying to find 'bad' characters that users might type in....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
I set up a few users on my SQL Server 2022 instance.
CREATE LOGIN User1 WITH PASSWORD = 'Demo12#1' CREATE USER User1 FOR LOGIN User1 GO CREATE LOGIN User2 WITH PASSWORD = 'Demo12#2' CREATE USER User2 FOR LOGIN User2 GO CREATE LOGIN User3 WITH PASSWORD = 'Demo12#3' CREATE USER User3 FOR LOGIN User3 GOI then created a schema that one of them owned. Under this schema, I added a table with some data.
CREATE SCHEMA MySchema AUTHORIZATION User1
GO
CREATE TABLE Myschema.MyTable(myid INT)
GO
INSERT MySchema.MyTable
(
myid
)
VALUES
(1), (2), (3)
GO
SELECT * FROM MySchema.MyTable
GO
I granted rights and verified that User2 could access this table.
GRANT SELECT ON Myschema.MyTable TO User2 GO SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOThis worked. Now, I move this schema to a new user.
ALTER AUTHORIZATION ON SCHEMA::Myschema TO User3; GOWhat happens with this code?
SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOSee possible answers