SQL Server and MOM Part II
This article will continue where the last one left off. We will import MOM 2005 Management Packs and Reports and begin monitoring SQL Server 2005.
This article will continue where the last one left off. We will import MOM 2005 Management Packs and Reports and begin monitoring SQL Server 2005.
SQL Server Integration Services checkpoints enable you to start a package from where it failed. This helps you avoid having to re-run a 6 hour package over again. Learn how to use this valuable feature with this quick how-to video. Free registration required.
Our spotlight series is bringing you a look at the people behind the software at Microsoft and this time we delve into security a little as we get to know Raul Garcia.
Automating installations with SQL Server 2000 is easy because it creates a setup.iss file that you can use as input, but Microsoft removed this feature from SQL Server 2005. Learn an undocumented SQL Server 2005 feature that provides similar functionality to setup.iss.
Software developers constantly need to learn about new technologies, products and methodologies. Think about what sort of programming you were doing 5 or 10 years ago. If you have been developing software that long, you will, no doubt, be working on very different systems now than you were then.
Ensuring that your disk subsystem performs well and does not run out of space is a balancing act that many DBAs learn over time through trial and "out of space" errors. New author Arindam Banerjee takes a look at some of the things to consider when capacity planning.
This article adds some handy reporting capabilities to the new load testing tool in Visual Studio 2005 Team System.
Building a data warehouse is a complicated topic and a hot topic now. Many companies embark upon these projects without understanding what they really need. New author Janet Chan takes a look at some of the things you need to consider before embarking on a project such as this.
Enter to win a Ms Pacman/Galaga arcade machine when you download and register a free version of Microsoft Visual Studio Express Editions (free learning resources included).
The benefits and drawbacks of GUIDs as primary keys are generally known. Despite the drawbacks, some people use them to fulfill specific business requirements (the IDs are unique across multiple servers).
It is Friday, the queries are running, and nobody is watching the bill. That...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Comments posted to this topic are about the item What is the Cloud?
Comments posted to this topic are about the item Changing the Schema
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
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