Building Your Brand at Work?
This Friday's poll asks how much you can help yourself while working at your job? Can you build your own brand at work?
This Friday's poll asks how much you can help yourself while working at your job? Can you build your own brand at work?
SQL Server 2005/2008 provides the ability to change the execution and security context with the EXEC or EXECUTE AS clause to allow a user to perform high privileged activities without allowing the user to have high privilege access.
Recently, a fellow DBA showed me a set of documentation on a commercially available product. This is a product people pay money for to license and use. It's not an in-house developed application or a community released free sample.
Securely sending Service Broker messages from instance to instance requires a somewhat complex configuration. This tip walks you through the proper methods
SQL Server 2005 implemented the concept of a database object schema. A schema is a distinct namespace to facilitate the separation, management, and ownership of database objects. It removed the tight coupling of database objects and owners to improve the security administration of database objects. Database object schemas offer functionality to control and help secure application objects within a database environment not available in previous versions of SQL Server.
I've had a few requests in the past, so I decided to just give it a go. Here's the raw footage from the episode of the Voice of the DBA podcast that I shot this week. It's uncut, the raw footage of what I took off the camcorder,
Everyone has an opinion on the best advice to give an IT person who is unemployed and wants to get back into paid work. Phil Factor outlines what he would advise.
Complete package to allow tracking of any data that Profiler can capture and storage for auditing purposes, use to satisfy SOX compliance.
This edition of SQL School brings us a look at how to set single user mode for your SQL Server instance.
I read a post on Brent Ozar’s blog last week that discussed employers’ expectations when hiring new team members. Though the story was specific to database professionals, the same principles apply to almost any hiring situation. The moral of Brent’s story...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Hi All I am trying to find 'bad' characters that users might type in....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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