A Fine Slice Of SQL Server
Aaron Nelson has proposed breaking up SQLPackage.exe into at least three cmdlets:
SQLPackage.exe – Needs to be made into at least 3 cmdlets
SQLPackage.exe – Needs to be made into at least 3 cmdlets (and possibly more; we have added ideas for additional cmdlets below). The first 3 cmdlets that need to be made into are:
Export-SqlDatabase
Import-SqlDatabase
Compare-SqlDatabase
This seems reasonable and would help maintain databases.
Comments closedChrissy LeMaire and Aaron Nelson have succeeded; Microsoft has fixed the three issues with SQLPS:
In my previous blog post “Can We Get These 3 SQLPS Issues Fixed before SQL Server 2016 RTMs?“, Aaron Nelson and I asked the SQL and PowerShell community to help upvote 3 SQL Connect items. The items addressed three problems with SQL Server’s PowerShell module, SQLPS.
- It took 3-5 seconds to load
- It changed the present working directory when loaded
- It produced approved verb warnings when loaded
Today, Microsoft responded, letting everyone know that the issues were addressed in SQL Server Management Studio March 2016 Refresh.
Given the reputation Connect has in the community, I’m glad to see these issues get fixed.
Comments closedDrew Furgiuele digs into why Powershell scripts break with SQL Server 2016:
One of the steps I tried to remedy the problem was removing the SQLPS module directory from the PSModulePath environment variable, to see if the Import-Module would skip over it. Turns out I was only half right: I should have removed non 2016 versions of the module path, as Matteo goes on to explain:
I’m hoping there will be a real fix for RTM. This works, but it’s neither intuitive nor easily decipherable.
Comments closedVery quick and simple and hopefully of use to people, this could easily be turned into a function. The full script is below and also available here on the Powershell gallery or by running Save-Script -Name Set-ExtendedEventsSessionstoAutoStart -Path <path>
This is indeed a quick and easy script, and quite useful when checking across a large number of instances.
Comments closedMike Fal creates and does basic configuration of an Azure SQL Database instance using Powershell:
From a logical standpoint, working with Azure SQL databases is not very different from setting up a SQL Server instance and database in your environment. There are 3 main components we will need to deploy:
A server
A database
A firewall (server or database)
This is the second part in his series.
Comments closedSimon Sabin uses Powershell to install Power BI:
Having recently been having rebuilding my machine I finally decided to automate the process of installing the software I need.
This was a life saver as I was reinstalling a few times to try and figure out why I wasn’t getting sound on my external monitor. So I was gradually uninstalling everything until I found out that it was Hyper-v that was causing the problem.
The outcome meant I was installing PowerBI lots and had to automate it.
This looks like the first step toward a Chocolatey script.
Comments closedChrissy LeMaire has an update on SQLPS and SQL Server Linux:
Microsoft is investigating options for a cross-platform lightweight SQL Management Studio GUI tool for Linux.
Microsoft is investigating open sourcing the SQL Server PowerShell provider and cmdlets, and that it “makes a lot of sense” and “aligns with what Microsoft has already done with our Azure PowerShell cmdlets on github.” This is being tracked by connect item 2442788.
Microsoft doesn’t have dates or more details to share for any of these items at this time and will keep the community updated on their progress as they continue to evaluate our plans based on customer feedback
I’m most interested in the first of these points, but this is all interesting news. Also check out her guest appearance on the PowerScripting Podcast.
Comments closedMike Fal introduces us to Azure SQL Database operations using Powershell:
What is this all about? It took me a bit of digging, but what it boils down to is that Microsoft made a fundamental change to how things are managed within Azure. You will now find documentation on these two different deployment models: Classic Deployments and Resource Manager Deployments. These two different set of Powershell cmdlets reflect these different models, as anything for Classic Deployments are handled by cmdlets in the Azure and Azure.Storage modules. All the Resource Manager Deployment stuff is handled by the AzureRM* modules.
This is the first in a series and serves as an introduction to the topic.
Comments closedJust recently a reply was made to the Connect item, highlighting the fact, that the current values of the Data/Log/Temp and Backup Directories – meaning the currently configured values – is exposed through the Server.ServerProperties collection. According to the answer, only public property values are exposed.
Using PowerShell, we can now retrieve the desired information from any given instance of Analysis Services. Doing so would look something like this:
It’s good to know that this information is available via Powershell.
Comments closedMike Fal wants to automate loading multiple CSV files:
Once the staging table is in place, the load is actually fairly simple. You have lots of options, but the easiest one for my money is to build a BCP call and execute that. BCP is a simple utility that has been around for a while, mostly because it is effective. The build is not difficult:
It’s quick, dirty, and functional.
Comments closed