Get SQLServer Name and Uptime SPROC
Stored procedure to provide clean output of system name and uptime since last restart
2010-11-16 (first published: 2010-11-08)
1,259 reads
Stored procedure to provide clean output of system name and uptime since last restart
2010-11-16 (first published: 2010-11-08)
1,259 reads
Script will display current status of SQL server services and even show if not installed. Works on SQL 2005,2008 2008R2. Both 32 and 64 bit servers.
2010-11-15 (first published: 2010-11-09)
3,566 reads
In the last script, we covered removing the trailing partition in a Range Right, date valued partition. This script adds a new (empty) partition to the partition scheme.
2010-11-12 (first published: 2009-12-17)
1,071 reads
This is simple script to change string to title case. It will take string in any case and convert it to initcap.
2010-11-12 (first published: 2010-10-19)
1,524 reads
This script automatically splits a partitioned table, merges the partition function and then drops the associated file group for the partition.
2010-11-11 (first published: 2009-12-17)
2,215 reads
This script will help you transfer logins between one instance of SQL and another.
2010-11-08 (first published: 2010-01-07)
4,611 reads
Days, hours and minutes since SQL Server service was started
2010-11-05 (first published: 2010-01-15)
2,506 reads
This script may help identify tables impacted by frequently-occurring scans.
2010-11-02 (first published: 2010-02-04)
3,889 reads
A Recursion function that was used to apply a Rate percentage to a base amount for the reqested number of times.
2010-10-28 (first published: 2010-10-13)
581 reads
Create a data dictionary with two stored procedures using sys objects to view via SSRS (or other reporting tool) report
2010-10-21 (first published: 2010-10-16)
2,261 reads
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...
It is Friday, the queries are running, and nobody is watching the bill. That...
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....
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
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