- -c which allows you to use the command prompt, so always required
- -v optional verbose mode which includes the standard SQL Server Agent error log entries
- -iinstancename if you are using a named instance
You may have noticed that SSMS 17.1 now offers an upgrade package for existing SSMS 17.0 installs.
So what’s the difference? Roughly 400MB.
If for some reason you need to restore the system databases, you’ll typically find copies of the original system databases in the …\Binn\Templates folder.
Below shows the file on a SQL Server 2016 default instance installation:
Details on how to make use of them is found here
In case you missed it, AUTOGROW_ALL_FILES was added in SQL Server 2016 and tempdb has this enabled by default.
Further info is mentioned here.
EXEC sp_MSforeachdb '
DB_NAME() AS database_name
,CASE WHEN is_autogrow_all_files = 0 THEN ''no'' ELSE ''yes''
END AS is_autogrow_all_files
Fany Carolina Vargas sure does a great roundup newsletter and Mays can be found here.
In SQL Server Management Studio 17.0 the PowerShell module was moved into the PowerShell gallery.
This means that you may see the following:
When you go to https://www.powershellgallery.com/ you currently see:
I don’t know about you, but it suddenly seems that a simple tweak to SSMS has become a headache for DBAs.
Performing a search gives 4 results and it looks like the matteot_msft is the correct one. Having company package under a users name doesn’t sound like a good idea to me, possibly this should be a team account?
So how do you download it?
lol mind blown, KISS appears to have gone out the window :)
If you’ve made it this far and have an internet connection the supplied method is:
Save-Module -Name SqlServer -Path <path>
Install-Module -Name SqlServer
Lets give it a try:
It’s now requesting NuGet provider version ‘220.127.116.11’ or newer
Once completed you’ll see the folder and files
For the next step, I received the following message which requested for -Force to be used:
Once completed, the SSMS error message no longer occurs