An overview of Master Data Services - MDS in SQL Server 2008 R2
With Master Data Services, IT organizations can centrally manage critical data assets companywide.
With Master Data Services, IT organizations can centrally manage critical data assets companywide.
When developing reports that use Analysis Services as a data source end user can sometimes be confused about some of...
A book review of a new T-SQL book for SQL Server 2008, written by longtime SQLServerCentral author and MVP, Kathi Kellenburger.
This week, a guest editorial from Phil Factor on how SQL Server database documentation falls woefully short of what is required and expected by most development teams.
In building a database, typically we want a well normalized design. However there are cases for considering options for denormalization in complex systems. Timothy Claason gives you some thoughts on the subject.
Build your SQL Server skills without leaving your desk.
A new type of application looks to collate and integrate knowledge from workers all around a company. Steve Jones is reminded of the Borg for today's editorial and says it might be good for data professionals.
Auditing your SQL Server instances has become more of a concern these days. SQL Server 2008 introduced a new feature named SQL Server Audit. Enabling this feature can be done in just a few simple steps, but so could disabling this feature. And when it comes to audits, many times you are asked to provide proof that the audit itself has not been tampered with.
This Friday's poll asks when types of distractions you might like to have at work that would let you recharge. Answer and let everyone else know what would help you enjoy your job more.
Continuing with his series on changes in SQL Server 2008, Arshad Ali takes a look at table enhancements and new data types.
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