Do Other Departments Know What You Do?
Do other departments know what you do? One on one discussions is a great way to make sure.
Do other departments know what you do? One on one discussions is a great way to make sure.
There were many new DMVs added in SQL Server 2012, and some that have changed since SQL Server 2008 R2. This is a brief overview of the biggest changes and what they mean to you!
SQL Bits is only two weeks away! Join us for the free community day on July 19th, there is also a paid-for pre-conference day on July 17, as well as a paid-for special training day on July 18. There are a whole host of great speakers, including Grant Fritchey, Steve Jones, and David Atkinson (and Brent Ozar, and Benjamin Nevarez, and Karen Lopez...you get the idea). Register while space is available.
There are some aspects of tables in SQL Server that a lot of people get wrong, purely because they seem so obvious that one feels embarrassed about asking questions. Robert Sheldon reckons that no questions about SQL Tables are off-limits, and deserve frank answers.
In the next level of the Stairway to Biml, we breakdown the various elements in a Biml file to help you understand what parts of the files are used to control the package generation.
Phil Factor fluffs the feathers of the shared sandbox model of development.
Source control will allow you to maintain branches in the development of your database, but the subsequent merge isn't pain-free. How can the database developer support the rapid development and delivery of features in an application? Versioning, branching and merging is part of the solution, but what about the rest of the solution?
Today we have a guest editorial from Sarah Wagner that thanks all the people that have helped her become a better DBA.
Here is a short How To article on querying for permissions in a SQL Server database
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