Run a specific query across all servers using powershell
Run a specific query across all servers using powershell
2019-05-03 (first published: 2015-03-06)
3,264 reads
Run a specific query across all servers using powershell
2019-05-03 (first published: 2015-03-06)
3,264 reads
PowerShell V2 introduces the "try-catch-finally" statements, similar to those you already use when you write .NET code. "Try-catch-finally" encloses a block of script that is likely to produce errors under specific circumstances and therefore helps you to keep your code organized. This article is a short usage guide for this error handling construct.
2015-02-24
8,518 reads
2015-02-06
1,642 reads
PowerShell is a very popular and powerful feature in the Microsoft stack. It is extensively used for development, deployment and administration across various ecosystems like SQL Server, SharePoint, Azure Cloud and others. PowerShell cmdlets are available for HDInsight as well and in this tip we will take a look at fundamental aspects of Microsoft Azure PowerShell for HDInsight.
2014-12-26
7,675 reads
Remove backup folders from multiple servers.
2019-05-03 (first published: 2014-12-09)
621 reads
2014-11-04
1,774 reads
You can execute PowerShell code that creates the data of an object, but there is no cmdlet to generate the 'object notation' code from an existing PowerShell object; until now, that is. Phil Factor also produces a ConvertTo-YAML function and explains how they both work, with illustrative code.
2014-11-04
9,369 reads
Extract SQL Server Name, Instance Name, Service Account details, startMode and ServiceState details with Powershell.
2019-05-03 (first published: 2014-10-13)
6,124 reads
I was having a hard time to reading the Windows 2012 R2 Failover cluster log from my live server. That is why I just wrote a simple PowerShell script to get the job done for me.
2014-08-21 (first published: 2014-07-29)
1,752 reads
Marcin Policht provides a comprehensive overview of Windows PowerShell’s capabilities in regard to managing SQL Databases (or, in general, cloud-resident resources).
2014-07-18
3,207 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