SQL Server Hardware Performance Checklist
We take a look at each of the major components of a SQL Server's hardware, and examine what can be done to help maximize the performance of your hardware.
We take a look at each of the major components of a SQL Server's hardware, and examine what can be done to help maximize the performance of your hardware.
In the Database administration world, it is often necessary to run a query on the production box and then run the same query on the QA or UAT box and compare the results. In this article, I would like to introduce a method that takes advantage of an MS-DOS batch file and SQL Server utility, BCP.exe, to compare the query results executed on two different servers.
So you open up the tool a hundred times a day. In this article by Brian Kelley, he shows you how to get the most out of some of the known and unknown features.
There is nothing spectacular about using indexes per say. However, on many occasions I have come across a variety of SQL coders that never consider validating that the index they think they are using is efficient or even being used at all. We can all put indexes on the columns that we think will be required to satisfy individual queries, but how do we know if they will ever be used. You see, if the underlying table data is constructed, contains, or is ordered in a particular way, our indexes may never be used. One of the factors around the use of an index is its clustering factor and this is what this article is about.
This article is a member of the series Introduction to MSSQL Server 2000 Analysis Services. The series is designed to provide hands-on application of the fundamentals of MS SQL Server 2000 Analysis Services, with each installment progressively adding features and techniques designed to meet specific real - world needs.
Every once in awhile there is a unique T-SQL solution in SQL Server that solves a rare problem. Not many of us have had to deal with boolean evaluation in our jobs, but a few have. Author Eli Leiba has and brings us a new article that shows how to build a procedure that can take a boolean expression and evaluate it to true or false.
This series of articles will examine the purposes, uses, and optimization of cursors in SQL 2000. SQL languages are designed so groups of records, or sets, can be manipulated easily and quickly. The speed at which groups of data can be altered, updated and deleted, demonstrates why working with sets is the preferred method. However, there are places where cursors are a better choice.
The next version of SQL Server due in 2005 will bring about many changes in how it works, with .NET, the CLR integration, Integration Services, and much more. Many of us are looking to get a jump on the product and see where these changes might affect our scripts and environments. Jon Reade has started the work in decoding the new DBCC commands, which ones work and which don't. Since there's a limited amount of documentation for the Beta product, read about his detective work and send him off an
SQLServerCentral.com is all about learning. Our goal has been to build a community where we all teach each other how to become more proficient with SQL Server. Most of our content to date has been written articles that show you how to do something. Well we have a a better idea, maybe. Check out our new video HOWTO series.
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
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...
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