Using DMVs to Find the Ports that SQL Server is Listening On
The other day I was asked to provide the port number that a SQL Server instance was listening on. As...
The other day I was asked to provide the port number that a SQL Server instance was listening on. As...
Performance is always one of the most important things a DBA can learn to deal with. It's also one of the more nebulous arts to learn. Today Steve Jones shares some thoughts on how we might better help people learn.
MVP Allen White shows how he can use Powershell to setup SQL Source Control from Red Gate Software on Nov 18, 2010.
Windows PowerShell has the concept of execution policy that determines in which cases script and configuration files are able to...
sp_locks is a useful tool which can help a DBA in detecting and troubleshooting blocking and concurrency scenarios. This article demonstrates a worked example of using sp_locks to troubleshoot a database concurrency issue.
This article presents a case study of using the Management Data Warehouse feature in SQL Server 2008 to analyze disk usage trends by product.
Today we have a guest editorial from Andy Warren. Are you ready for an inspection at work? Are you really running your environment in a way that would make you proud? Andy has some thoughts about sticking to your policies and procedures.
The first part of your job is to identify the unique color combinations of products and the second part is to identify the products that have the given color combination.
Phil points out that the SQL Server community has a role to play in making sure that the wisdom of SQL Server Pundits is regularly tested and challenged.
The system stored procedure sp_start_job is a very useful T-SQL command that starts a SQL Agent job. The problem with this is that it starts the job and it doesn't wait until the job is finished and sometimes I want to start a job and wait until the job is finished and move on to another job or task that depends on the result of the previous job.
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