Determining SQL Server database storage requirements
Determine accurate storage requirements for a SQL Server database with these methods. Calculate how to set storage requirements for a database application.
2008-02-04
4,540 reads
Determine accurate storage requirements for a SQL Server database with these methods. Calculate how to set storage requirements for a database application.
2008-02-04
4,540 reads
The Entity Framework is an exciting new technology being developed for ADO.NET. It allows developers to view data using a logical model instead of a physical model, offering more flexibility.
2008-02-01
3,492 reads
In this article I will settle down a little bit and share with you tools that I have used as part of the data governance trade.
2008-01-31
1,234 reads
2008-01-30
1,214 reads
Stored procedures can be an effective way to handle conflicting needs, but it's not always so obvious how to write them so they both perform well and scale.
2008-01-30 (first published: 2007-02-05)
10,708 reads
Paul Randal of SQLskills takes a look at lock escalation in SQL Server 2008
2008-01-30
1,436 reads
In this video, Randy Dyess shows you how important SQL Server dependencies are and some of the faults with SQL Server 2005 with these. For example, SQL Server will allow you to create a stored procedure that points to a table that doesn't exist. He also shows you how this problem has been corrected in SQL Server 2008.
2008-01-30
6,718 reads
This article, part 4 in a series, discusses how to use, publish, maintain and govern the enterprise architecture.
2008-01-29
3,259 reads
Business Intelligence Architect Bill Pearson introduces the numeric Max()function, and leads hands-on practice examples of the basic concepts.
2008-01-29
1,729 reads
This white paper enumerates the connectivity options for databases with Microsoft SQL Server 2005 Integration Services and mentions special considerations that are required when using some database sources with some of the more complex transformations.
2008-01-28
2,727 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...
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