SQL Server Needs Incremental Updates
Although Brian likes that Microsoft delayed the next release of SQL Server for quality, he disagrees with the release strategy. See his opinion and argue your own!
Although Brian likes that Microsoft delayed the next release of SQL Server for quality, he disagrees with the release strategy. See his opinion and argue your own!
It's been some time and he apologizes. This next part of this series from Steve Jones looks at selective auditing changes to data on the server using a combination of methods presented in previous articles in the series. Read on if you have problems tracking changes to data on some tables, but don't want to implement a solution that tracks every change.
Error handling is one of those things that is simple to do in SQL Server, but most people don't do it and it's not the most rebust thing. Here's another way that you can implement error handling in your stored procedures from a new author Amit Jethva.
Have you ever built a join graphically using Access or Visual Studio? Did you know that you can do this with the native SQL Server tools? And it's easy! Follow along as Dale Corey shows you how.
The fourth and final installment in this series, this week Andy discusses how using XML can reduce the load you put on your network and on your server. This is a high level article that discusses concepts. We think you'll find a good idea or two in this one!
Lumigent Technologies today announced that they are a recommended supplier to provide data auditing solutions for risk management to customers of Microsoft SQL Server 2000 through their Entegra product. Enterprises that depend on SQL Server databases can now rely on Entegra as a trusted auditing solution to enable compliance with regulatory requirements.
The error handling in SQL Server leaves something to be desired, especially compared with other RDBMSes and languages. The standard method of testing for errors can leave your code bloated and hard to read. Stefan Popovski looks at another method of handling errors.
What's wrong with SQL Server? Lots of things to some people, but here's a look at where this product is positioned in the marketplace against the other RDBMSes.
A little off topic (or is it?), David needed to vent a little - something we can all appreciate. Meant to be light hearted fun, please don't take too seriously.
Sometimes its good to get back to basics - or to make sure you really know all the basics. This is a very good intro to all the different join types.
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 SQL Art, Part 4: Happy...
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
WhatsApp: 0817839777 Jl. I Gusti Ngurah Rai No.8 A-B, RT.8/RW.6, Wil, Kec. Duren Sawit,...
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