Log Shipping Lite with PowerShell
A PowerShell driver that performs incremental restores on a standby server, a lite weight log shipping solution.
2013-07-01
4,650 reads
A PowerShell driver that performs incremental restores on a standby server, a lite weight log shipping solution.
2013-07-01
4,650 reads
PowerShell script to SlipStream SQL Server 2008 installer with SPx patch.
2014-08-27 (first published: 2013-04-18)
1,191 reads
Query Active Directory Computer objects to verify existence
2013-05-01 (first published: 2013-04-16)
1,107 reads
Pre-Create Active Directory Virtual Computer objects to support a new SQL Cluster
2013-04-30 (first published: 2013-04-15)
974 reads
Restores the latest backup of a database to a destination server of your choice, and creates a new backup if needed.
2013-04-16 (first published: 2013-03-30)
1,768 reads
This script is an improvement from my original script entitled "Powershell - Query SQL Servers Operating system details".
2013-03-22 (first published: 2013-02-27)
2,408 reads
The script works through the CMS you have set up to manage your environment and gathers various server information.
2013-02-26 (first published: 2013-02-05)
1,671 reads
Marcin Policht presents the fundamental principles of PowerShell in the context of SQL Server 2012. Join him as he steps through its initial setup and configuration, and reviews specific management areas where its advantages can be realized.
2013-01-31
3,203 reads
This Powershell script calls a stored procedure and exports the results to a CSV file
2014-08-28 (first published: 2013-01-03)
5,076 reads
PowerShell is worth using when it is the quickest way to providing a solution. For the DBA, it is much more than getting information from SQL Server instances via PowerShell; it can also be run from SQL Server as part of a system that helps with administrative and monitoring tasks.
2012-10-29
3,321 reads
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