The next few years will be critical for the information technology staff, as they attempt to integrate and manage multiple, diverse hardware and software platforms. In this article, Lockwood Lyon addresses how to meet this need, as users demand greater ability to analyze ever-growing mountains of data, and IT attempts to keep costs down.
Unique indexes are the database developer's responsibility. Non-unique indexes can be more easily maintained directly on the production database by an automated process.
It's important that you remember to live and enjoy your life as it passes by. Today Steve Jones reminds us that we want to work to live, but also plan to live and plan for the future.
Scott Murray takes a look at what count function variations and related functions are available in SQL Server Reporting Services (SSRS).
It seems that often we promote the best technical people into managerial positions, but is that a good idea? Steve Jones notes that a few people think this is a bad idea and there ought to be a technical career path for IT workers.
ASP.NET Core is a fascinating platform with many good ideas, but in its present form (RC1)there is a culture shock for experienced ASP.NET developers to experience the effort involved in porting a realistic application. There is an obvious advantage on being able to host an application on any web server, but is this enough to compensate for losing the convenience of an integrated pipeline?
In earlier chapters, we talked about the Microsoft Data Mining enemies. We will talk now about Microsoft Azure Machine Learning.
When a business does not have an agreed set of definitions for their every day terms slow burning chaos ensues.
Aaron Bertrand follows up on a recent post about the performance of STRING_SPLIT() with a few additional reader-motivated tests.
Ability to enable Instant File Initialization during the installation of SQL Server 2016.
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