The Bulldogs
Steve Jones talks about IT Project Failure and how you should re-evaluate things are you move forward.
Steve Jones talks about IT Project Failure and how you should re-evaluate things are you move forward.
Learn how using the OUTPUT clause in SQL Server 2005 queries simplifies T-SQL code and returns results of rows changed by an INSERT, UPDATE or DELETE SQL command.
Having separate databases for each client? It's a common problem and Steve Jones wonders if this might be a feature coming in SQL Server at some point.
Having separate databases for each client? It's a common problem and Steve Jones wonders if this might be a feature coming in SQL Server at some point.
Having separate databases for each client? It's a common problem and Steve Jones wonders if this might be a feature coming in SQL Server at some point.
As much as we're SQL Server folks here, sometimes we do need to connect to other data stores. Hai shares some of his experiences doing so. Might come in handy someday.
This paper introduces Service Broker, a new feature in Microsoft SQL Server 2005. With Service Broker, internal or external processes can send and receive guaranteed, asynchronous messaging by using extensions to Transact-SQL.
KPIs or Key Performance Indicators are one of the most important entities in driving business decisions. It can be defined as a (quantifiable) measurement used to define and measure an organization's progress in achieving business goals. KPIs for an organization are decided upon by giving careful thought to how each goal and the progress towards these goals should be measured.
In a followup to his article on SQL Server Everywhere, Jacob Sebastian takes a more in-depth look at the smallest platform for SQL Server, Compact Edtion.
An overview of how to collect data from TSQL into Operations Manager Performance Rules.
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