Learn SQL Server in Arabic
A series of videos on SQL Server have been produced in Arabic. Learn about SQL Server in another language.
A series of videos on SQL Server have been produced in Arabic. Learn about SQL Server in another language.
We have a guest editorial today from Chris Shaw, on the need to take chances in your life.
There is nothing mysterious about SQL Server backups. They are essential, however you use your databases. Grant Fritchey explains the basics of database backups and restores with SQL Server 2014.
We don't always do the job we would want done for us. We don't pride ourselves as craftspeople do. At least that's what Steve Jones thinks.
The new SQL Server 2014 “Memory Optimization Advisor” tool helps you quickly analyze tables to see how easy it is to migrate them to In-Memory OLTP tables. Read on to learn more.
Many of us have checks in place on systems or processes, but would we be aware of tampering with the operation of our computer systems? Steve Jones notes that auditing can be important to ensure things are working well.
Using a default account for SQL Server services can be a security risk for two reasons. Firstly, it can give the service a higher level of permissions than it needs. Secondly, isolation is compromised by several services running under the same account. This metric checks whether SQL Server services are running under any of the default accounts, such as localsystem.
The process of doing SQL code-reviews used to be tedious and error-prone. Until SQL Enlight, it was a process that was difficult to automate for release and deployment. As it is now both a Command-line utility and an SSMS add-in, the database developer can see immediately the parts of the code that would raise eyebrows with the vigilant production DBA.
The idea of not having a boss appeals to many of us, but is it really what you'd like? Steve Jones notes that Zappos is trying this, by eliminating many of the manager roles at the company.
Tuning a SQL Server instance and improving the way it performs is a complex task that many people struggle to complete. In this piece, Steve Jones talks about the idea that it is a science as much as an art.
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