Both SET and SELECT can be used to assign values to variables. But when to or when not to use SET or SELECT? Or does it matter? This articles shows you how SET and SELECT are different in various scenarios, along with examples. You will also find a test script that you can run, to identify the performance differences between SET and SELECT
Randy says that the biggest reason we have so many injection vulnerabilities is that all the asp books use inline sql for their examples! We STILL encounter developers who don't understand injection. Read and pass on to your dev team.
The Web Data Administrator is a utility program implemented in ASP.NET that enables you to easily manage your SQL Server data wherever you are. Using its built-in features, you can do the following from Internet Explorer or your favorite Web browser:
Create and edit databases in Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (MSDE)
Perform ad-hoc queries against databases and save them to your file system
Export and import database schema and data
Andy Warren started his worst practice series some time ago with the intention of looking at the worst things you can do. Given that we may not always be able to implement the best practices, at least we can try to avoid doing things harm the system or decrease performance. This article continues the series and looks at an item I see mentioned in our discussion forum quite often, triggering external events. From a trigger.
Press release about Embarcadero products being named finalists in the annual Jolt awards sponsored by Software Development magazine.
Reader Rob Potter suggested that our logo could use some fine tuning and graciously submitted some ideas he had for doing just that. Come take a look and tell us what you think.
It's not SQL Server related, but take a break and see how you do. The highest I've seen so far is 1602. If you beat it send a screen shot (small, please) to sjones@sqlservercentral.com
Adding a column is one of the simpler tasks you'll ever do as a DBA, yet danger lurks! All too often we add columns without going through some type of check list to make sure we're safe. What could adding a column break? You might be surprised!
Brian has been busy lately helping us with content for our magazine (you have checked out www.sqlserverstandard.com haven't you?) but he's back this week with a great write up a new product that let's you read from the transaction log.
Looking for a good (or another) TSQL reference? This might be the one. Bruce took a good look at it and points out both the good and the bad.
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