2001-08-22
570 reads
2001-08-22
570 reads
2001-08-22
729 reads
Get OLE Providers info I have found this useful in tracking down application driver/connection issues. I only had to use it 2 times. But it did help
2001-08-22
427 reads
Very simple, how much space is free on the hard drives of the SQL Server you are connected to.
2001-08-22
681 reads
2001-08-22
392 reads
2001-08-22
740 reads
This script will search all logged in users and return the spid along with the number of seconds since that spids last batch was executed.
2001-08-22
1,006 reads
Use this script to see showcontig for all tables in the context of the database in which its called. Very handy to schedule during off peak hours prior to any re-indexing to see how bad things are and re-build certain indexes sooner than you thought for peak performance.
2001-08-20
4,203 reads
A handy dandy proc that can be used to zip up a backup file to location specified. Also called from a backup script to automate the compression of all backups using PKZip command line utility. Make sure pkzip is in the path and found by the shell prior to using this script.
2001-08-20
3,735 reads
This script(sproc)uses xp_cmdshell from sql and FINDSTR from DOS to search the current errorlog for a specific string such as kernel or failed login. Compile this in the master db and if you do not pass an input parameter a example usage will display for you. ex: sp_dba_sqlerrorlog kernel Edward J Pochinski III
2001-08-13
1,935 reads
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...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
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