Change SQL Server Service Accounts with Powershell
If you need to change multiple SQL Server Services accounts across your environment, Powershell can do that for you.
2016-02-24 (first published: 2016-02-19)
6,725 reads
If you need to change multiple SQL Server Services accounts across your environment, Powershell can do that for you.
2016-02-24 (first published: 2016-02-19)
6,725 reads
When starting out with PowerShell, it is hard to escape from the detail to work out the best strategy for creating scripts. Laerte Junior explains how, when and why it pays to think in terms of versatile functions to meet varying demands.
2016-02-01
3,169 reads
Tim Smith shows how using PowerShell can be an effective way to track SQL Server snapshot and transactional replication counts for sources and destinations.
2016-01-28
3,231 reads
Whereas it is easy to provide inline documentation for a normal scripted PowerShell cmdlet or function so as to provide comprehensive help at the command-line or IDE, the same isn't true of binary cmdlets written in C#. At last, there is an open-source utility to assist with this that is being actively maintained and updated. At last, binary cmdlets need no longer be the poor cousins of scripted cmdlets in their documentation
2016-01-18
3,322 reads
2016-01-04
1,303 reads
PowerShell is like any computer language: you must understand the paradigms, the constructs, and the way it is designed to work to get the most value from it. It is no good just translating 'sausage-string' procedural algorithms. To demonstrate how Powersahell should be used as its' creators intended, Laerte Junior shows the difference between PowerShell problem-solving with, and without, PowerShell paradigms.
2016-01-01
6,637 reads
2015-12-29
1,113 reads
2015-12-10
1,218 reads
2015-12-18 (first published: 2015-12-09)
4,586 reads
If you're making a report from table-based data, an MS Word document is often a good option. In the second part of his introduction to SQL Server best-practice monitoring, Laerte Junior shows how to use PowerShell scripts to create a Word-based report with colour-coded alerts where there are problems or best practices aren't being followed.
2015-11-12
8,610 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