Checking Up on Developers
This Friday Steve Jones has a poll about developers. Help compile a good list of common mistakes made in SQL Server.
This Friday Steve Jones has a poll about developers. Help compile a good list of common mistakes made in SQL Server.
Prevent overlapping of time events with an indexed view.
The Red Gate SSMS Ecosystem is a framework that makes it easy to develop, share and manage SSMS add-ins. We aim to help add-in developers build everything from homegrown solutions and community-driven projects to commercial solutions provided by partner companies. We hope that DBAs and database developers will benefit from better integrated tools.
This article discusses Microsoft Power BI, different tools under the Microsoft Power BI umbrella and when each of them can be used.
Steve Jones has some concerns over new options in SQL Server 2014 that might lead some customers to experiment in a way that causes them unexpected pain.
Software maintenance is often required when purchasing software packages. But do the vendors deliver value for this charge? Steve Jones has a few thoughts on the subject.
SQL Server provides the UNION, EXCEPT, and INTERSECT set operations. How do they work and how can they be used in SQL Server? Can you provide any examples? Check out this tip to learn more.
Learn how to use SQLCLR to get file system information instead of using xp_cmdshell on your SQL Servers.
You may come across or even inherit a system where many of the users have different default schemas. Usually, this is easy to remedy - you go into Management Studio, right-click the user, and change the default schema through the UI. Or you write an ALTER USER command manually. But what if you have hundreds of users, across all of your user databases, that should all have the same default schema?
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.
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...
Hi All I am trying to find 'bad' characters that users might type in....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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