SQLServerCentral apologizes and you can win a book
After a plagiarized article this week, a content for you.
2013-12-05
12,041 reads
After a plagiarized article this week, a content for you.
2013-12-05
12,041 reads
Use this script in SQL Monitor to determine the general load on the operating system you can get a count of the processes that are in a runnable state. This value will go up and down as various systems run on the operating system. It’s only a measure of load on the system and won’t indicate the cause of problems, but will show you pressure on the system.
2013-12-03
3,671 reads
SQL Saturday is a training event for SQL Server professionals and those wanting to learn about SQL Server. This event will be held Dec 13 2013 at Università Politecnica delle Marche - Ancona, Italy. This SQL Saturday will feature 3 tracks focused on BI, DBA, and Development.
2013-11-28
2,464 reads
SQL Saturday is a free day of SQL Server training and networking coming to Washington DC on December 7. Paid pre-con sessions for this SQL Saturday are available.
2013-11-21
231 reads
Join Red Gate for a free seminar on December 6 (the day before SQL Saturday Washington DC). Steve Jones and Grant Fritchey, SQL Server MVPs, will present best practices for SQL Server version control, continuous integration and deployment, in addition to showing Red Gate tools in action.
2013-11-18
2,029 reads
Join Red Gate for a free seminar on November 15 (the day before SQL Saturday Oregon). Steve Jones and Grant Fritchey, SQL Server MVPs, will present best practices for SQL Server version control, continuous integration and deployment, in addition to showing Red Gate tools in action.
2013-11-12 (first published: 2013-10-31)
3,118 reads
This metric counts the number of principals who are members of the sysadmin fixed server role. SQL Server relies on role-based security to manage permissions. If multiple IT system administrators have permissions to set up new SQL Server logins, they might be inclined to do so as part of the sysadmin role. Adding a normal user to the sysadmin role could pose a security risk and is not recommended unless the principal is highly trusted.
2013-11-11
3,175 reads
Come join in the SQL Relay in 2013, attending a user group the week of Nov 11, 2013 in the UK. There are some amazing speakers, so be sure to register and attend.
2013-10-30 (first published: 2013-10-21)
5,868 reads
SQLSaturday BI & Big Data Edition is a free training event for everyone interested in learning about Business Intelligence & Big Data with a focus in the Microsoft SQL Server platform. This event will be held November 9th, 2013. In addition to our Saturday free event, we will also host four paid full day pre-conferences.
2013-10-29
387 reads
SQL Saturday is a training event for SQL Server professionals and those wanting to learn about SQL Server. This event will be held Nov 9 2013, admittance to this event is free, all costs are covered by donations and sponsorships.
2013-10-28
2,910 reads
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 Extreme DAX: Take your Power...
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
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