What to look for in an employer
A Job interview for a database Developer is, or should be, a two-way process. They are sussing you out, and you are sussing them out.
A Job interview for a database Developer is, or should be, a two-way process. They are sussing you out, and you are sussing them out.
Alex Kuznetsov's team of developers are geared to doing rapid development of database applications in a busy corporate setting, yet take considerable time over meticulous database design, extensive constraints, automated tests, error logs, and defensive coding. Why? Because it cuts down on the subsequent need for maintenance.
Baton Rouge, LA. LSU. Free Training. Come visit, learn a few things, and enjoy meeting other SQL Server pros.
Find the country, region and city of a user from an IP address using SQL Server. Oscar Garcia provides some code and resources if you want to dig into your analytics on your own.
This Friday Steve Jones talks performance reviews. The system in place at Microsoft is a tough one, which allows some to thrive, and some not to. Is it one you'd like to have in place?
Arshad Ali shows you how to create standard/custom report templates in SQL Server Reporting Services (SSRS), to ensure consistency throughout the organization in both the look and feel of reports.
A look at the performance of SQL Server compared to SQLite for single user applications.
An interesting reuse of technology in a completely new way caught Steve Jones' eye. See if you agree that this is rather amazing.
Annette continues her popular series for SSIS beginners by showing how a data flow task can be used in a package to move data from a SQL Server database to an Excel file, and insert an additional column into the Excel file that’s based on derived data.
Today Steve Jones talks about one of his pastimes: reading. He recommends you read more, and share the books you enjoy.
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,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
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
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
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