New features in SQL Server 2008 justify migration
New features such as the FILESTREAM data type and Policy-Based Management offer clear performance enhancements that may make the decision to migrate to SQL 2008 a no-brainer.
2009-04-16
4,223 reads
New features such as the FILESTREAM data type and Policy-Based Management offer clear performance enhancements that may make the decision to migrate to SQL 2008 a no-brainer.
2009-04-16
4,223 reads
In this chapter excerpt from "Microsoft SQL Server 2008 Management and Administration", learn how Resource Governor can improve SQL Server performance.
2009-04-13
2,489 reads
Stored Procedure to build a MERGE statement in SQL 2008 using dynamic SQL.
2010-05-31 (first published: 2009-04-06)
2,499 reads
One of the most interesting features in SQL Server 2008 is filtered indexes. This article starts with a quick explanation and then digs into the details and results.
2009-04-06
2,810 reads
Service Pack 1 for SQL Server 2008 has been released. Follow the link for more information.
2009-03-13
3,769 reads
This article is the first in a series of articles that will be covering all the Control Flow Tasks and Maintenance Plan Tasks in SQL Server 2008 Integration Services
2009-03-12
2,275 reads
Debugging capability in SSMS was a long sought feature by users and finally the Microsoft SQL Server team decided to provide this feature in SQL Server 2008.
2009-03-09
4,514 reads
This document described techniques for bulk loading large data sets into SQL Server. It covers both the available techniques as well as methodologies to performance tune and optimize the bulk loading process.
2009-02-24
3,931 reads
This article is the final article in a series that explores new features that are available in SQL Server 2008 Management Studio
2009-02-19
3,549 reads
SQL Server's new FILESTREAM feature simplifies the process of keeping file-based data, such as images, in sync with relational data.
2009-02-17
2,743 reads
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...
Wa:0817781222 Jl. Otto Iskandardinata No.37, Karanganyar, Kec. Subang, Kabupaten Subang, Jawa Barat 41211
Wa:0817781222 Jl. Ir. H. Juanda No.118, Lebakgede, Kecamatan Coblong, Kota Bandung, Jawa Barat 40132
Wa:0817781222 Jl. Ahmad Yani No.9, RT.01/RW.05, Marga Jaya, Kec. Bekasi Sel., Kota Bks, Jawa...
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