Writing Better T-SQL: Top-Down Design May Not be the Best Choice – Part II
A second part to the series by Mickey Stuewe on writing better T-SQL looks at some of the issues of using views in a complex query.
A second part to the series by Mickey Stuewe on writing better T-SQL looks at some of the issues of using views in a complex query.
So many of the problems that organisations have with their IT applications are due to the struggle with data, in the absence of overall organization-wide control and supervision of data and its progress through the various parts of the organization. Master data management (MDM) offers a solution to the many data woes by controlling data change, It does it in an analogous way to Version Control, so that changes are cleansed, checked, tracked and audited, and any named version can be published to other services. Now Microsoft has an implementation as part of the data platform.
Learn how to use the login commands included with SSMS2016 from PowerShell.
Finding a balance between work and life away from work is hard, but one good way is with periodic vacations. Today Steve Jones notes that some people don't take their vacation, which he sees as a problem.
When writing T-SQL code, we often write code to check if the database object exists first and then take some action. In this tip John Miner covers the new and easier way to do this in SQL Server 2016.
With the introduction of temporal table support in SQL Server 2016 Microsoft also added some additional functionality that makes it easy for you to join the current and history records of a system-versioned table. Greg Larsen shows you some of the different ways to do analysis of your system-versioned records over time.
This week Steve Jones argues against stored procedures. Is it a good argument or do want to stick with your stored procedures.
Simple steps towards understanding what is an Odds Ratio, and how do we arrive at it using TSQL and R scripts.
When you're formatting SQL Code, your objective is to make the code as easy to read with understanding as is possible, in a way that errors stand out. The extra time it takes to write code in an accessible way is far less than the time saved by the poor soul in the future, possibly yourself, when maintaining or enhancing the code. There isn't a single 'best practice, but the general principles, such as being consistent, are well-established. Joe Celko gives his take on a controversial topic.
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