You can mould PowerShell to the way you want to work, with all the settings and modules that you require, by using the profiles. Profiles are PowerShell scripts that run at startup, and once you have understood where they are and when each is used, they have a whole range of uses that make using PowerShell a lot more convenient.
R Services were added to SQL Server 2016, and there are customers using this feature to improve their business processes.
Performance tuning is a creative process which requires a lot of attention and manual work. SQL Server 2016's Query Store makes some of this work much easier, but what if you're using an earlier version? Fikrat Azizov shows how to automate assessing SQL Server query performance changes by using custom performance collection tools and reports.
In this article Greg Larsen explores using the temporal table feature of SQL Server 2016 to create a history table for an existing SQL Server table.
Larry Page is a very interesting person, one that is looking to change the world.
In this first part to looking at deploying SSIS packages to new environments, Andy Leonard looks at a few options for migrating your work to a new instance.
Azure SQL Data Warehouse uses SQL to query the data, but there are some differences to SQL Server's dialect of TSQL, and queries don't necessarily work in the same way. DBAs are also required to use SSDT to access Azure SQL Data Warehouse. It is worth taking the time to try the preview of the product, and take it for a 'spin around the block', following Robert Sheldon's walk-through.
After the crash of an US Air Force database was reported, Steve Jones has some advice.
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
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...
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....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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