Database Weekly - June 2, 2008
A look back at the news from the week including Windows 7 and taking an unwired vacation.
A look back at the news from the week including Windows 7 and taking an unwired vacation.
Is building software like building a house? Steve Jones digs into the comparison at the start of an editorial series looking at other professions.
Is building software like building a house? Steve Jones digs into the comparison at the start of an editorial series looking at other professions.
Is building software like building a house? Steve Jones digs into the comparison at the start of an editorial series looking at other professions.
A look back at the news from the week including Windows 7 and taking an unwired vacation.
In SQL Server 2005 there is the concept of alias data types, which are similar to user-defined data types in SQL Server 2000. Yakov Shlafman brings us the first part of a series looking at these structures in SQL Server 2000.
Seeking to recognize DBAs for the work they do, the Exceptional DBA Awards are open for nominations. Steve Jones talks a bit about the event.
Get an overview of typical data mining problems and the tools and models that are available in SQL Server 2005 for solving these problems.
One of the first things that should be done when managing SQL Server is to setup an appropriate backup plan in order to minimize any data loss in the event of a failure. Along with setting up a backup plan there are certain database configurations that need to be setup to ensure you are able to backup databases correctly. In this tip we will look at the different recovery models that SQL Server offers and how to choose a recovery model for your database.
The concept of telecommuting is arguably the most controversial working arrangement to evolve from the 1990's technological revolution. Tim Ford explains what it requires to work remotely – not just the tools you need, but the also character traits.
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