The Differences Between SQL Server 2000 and 2005 - Part 2
Steve Jones continues with his look at how SQL Server 2005 differs from SQL Server 2000, this time tackling the differences from a developer perspective.
Steve Jones continues with his look at how SQL Server 2005 differs from SQL Server 2000, this time tackling the differences from a developer perspective.
Join Business Intelligence Architect Bill Pearson as he continues his subseries surrounding components of the Analysis Services dimensional model. In this article we continue our introduction to dimension attributes, focusing upon the Misc group of attribute properties.
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.
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.
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.
The Trash Destination and this article came from early experiences of using SSIS and community feedback at the time. When developing a package it is very useful to have a destination adapter that does nothing but consume rows with no setup requirement. You often want run a package part way through development, or just add a path so you can set a Data Viewer.
When searching meta-data to find an occurance of a particular string or pattern it is difficult to look everywhere. This procedure helps you find what you are looking for.
Steve Jones talks about alternative hybrids, in this bi-monthly update on automotive news.
This component needs little explanation. It generates random integer (DT_I4) and string (DT_WSTR) data and places them in the pipeline. You specify how many columns of each you would like and for any string columns you pass a fixed length value. You then need to specify how many rows in total you require to be generated.
Last time, we discussed Table inheritance, which allowed us to easily reduce redundancies in our table design by creating "base" or "super" tables that contain columns and relations that "sub-tables" automatically inherit.
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