Monitor User Connections in SQL Server
This article explores the causes and remedies for applications failing due to too many open connections to SQL Server.
This article explores the causes and remedies for applications failing due to too many open connections to SQL Server.
Things have evolved since the days of essential pagers and landline connections. Or have they? Brad ponders how the nature of remote working is evolving, and invites you help others learn from your experiences.
A contest from Red Gate and Steve Jones could get you a copy of SQL Monitor and an iPad for Christmas. Steve Jones talks about how you can enter, and perhaps win an iPad for yourself this holiday season.
This challenge involves evaluating mathematical expressions presented using Roman Numerals and return the result of each expression.
Of the big four DML statements in SQL Server, the DELETE is the one least written about. This is odd considering the extra power conferred on the statement by the addition of the WITH common_table_expression; and the OUTPUT clause that essentially allows you to move data from one table to another in one statement.
For years we’ve been told you should use Enterprise Manager in SQL Server 2000 or SQL Server Configuration Manager in...
One very common structure that needs to be handled in T-SQL is the hierarchy. One of our prominent members of the community discusses how you can handle hierarchies in SQL Server.
Three contests from Red Gate Software are coming next week. Get a hint about what might be coming and set a reminder on your calendar.
One piece of advice that is often given to new SQL Server administrators is not to shrink their databases. But they seem to do it often enough anyway. For this Friday's poll, Steve Jones asks if we should do away with shrink.
Cross-posted from a Goal Keeping DBA blog:
Just recently, my oldest son entered the ranks of the teenagers. I shouldn’t actually...
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