2013-02-06 (first published: 2012-12-27)
1,851 reads
2013-02-06 (first published: 2012-12-27)
1,851 reads
Creates and populates a date-dimension table suitable for OLTP or data warehouse purposes.
2013-02-04
3,276 reads
Changes the database compatibility level of all databases to the given level.
2013-01-31 (first published: 2013-01-07)
938 reads
Database Users and their Corresponding Roles and type login.
2013-01-28 (first published: 2013-01-16)
2,118 reads
One of the new cool features in SQL 2012 is the SQL Server Availability groups. In other words being able to failover a group of databases which are logically connected. i.e. SharePoint databases. Well, it is also possible to do that in SQL 2008 (R2). It’s called a Grouped Failover.
2013-01-24 (first published: 2013-01-16)
574 reads
2013-01-18 (first published: 2012-06-21)
1,377 reads
Query Active Directory to get information on user logins.
2013-01-18 (first published: 2011-05-16)
3,865 reads
This function will return a value of date if found within a string, the date format in the string will vary. If no date is found a null value is returned
2013-01-17 (first published: 2012-12-18)
1,274 reads
Get database status,file details,free space
in sql 2005 and 2008 sql versions
2013-01-16 (first published: 2012-12-07)
2,526 reads
Just a stab at automating index maintainenance in SQL Server 2008
2013-01-11 (first published: 2008-11-07)
2,735 reads
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
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...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
WhatsApp:0817-866-887 Jl. Ahmad Yani No.31, Pattunuang, Kec. Wajo, Kota Makassar, Sulawesi Selatan 90174 (@bcakcumakassar)
Hi All I am trying to find 'bad' characters that users might type in....
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