Best Of
Re: Any known installation issues with version 7. 1. 16. 10851?
Installation of SQLMonitor works fine after installing .Net 4.6.1
Alex_indiwa
1 ·
Re: Smart Rename on a column crashes SSMS.
The reinstall worked for me as well. Thanks @blankenbush!
Luc
1 ·
Re: Licensing - Per user or Per node?
Hi @imops
The licensing model for SQL Monitor remains unchanged from what it has been; SQL Prompt is user based licensing and SQL Monitor (and SQL Backup) are server based licensing.
For SQL Monitor it depends on the number of Windows OS machines you have added to be monitored. A bit of confusion occurs due to differing terminology so let me give a few examples that may help:
A two node Windows Failover Cluster (WFC) which has a single SQL Server Failover Clustered Instance (FCI) across the two nodes. This represents as a cluster with two nodes and a single SQL Server instance. This takes two licenses as there are two Windows OS machines in the cluster.
A two node WFC with two SQL Server FCI across it and each node with a standalone SQL Instance as well. This represents as a cluster with two nodes and two SQL Instances along with each node showing a SQL Instance each. This also takes two licenses as there are two Windows OS machines in the cluster.
A five node WFC with a single SQL Server FCI across it, represents as a cluster with five nodes and a single SQL Server instance and takes five licenses, one for each machine in the cluster.
A single standalone machine with 10 standalone SQL Instances on it will only take only one license.
I hope those examples help clarify how the licensing works for SQL Monitor - as described in your second link above, SQL Monitor auto detects the cluster and all nodes therein and so you will need a license for each Windows OS node in your cluster.
Kind regards,
Alex
The licensing model for SQL Monitor remains unchanged from what it has been; SQL Prompt is user based licensing and SQL Monitor (and SQL Backup) are server based licensing.
For SQL Monitor it depends on the number of Windows OS machines you have added to be monitored. A bit of confusion occurs due to differing terminology so let me give a few examples that may help:
A two node Windows Failover Cluster (WFC) which has a single SQL Server Failover Clustered Instance (FCI) across the two nodes. This represents as a cluster with two nodes and a single SQL Server instance. This takes two licenses as there are two Windows OS machines in the cluster.
A two node WFC with two SQL Server FCI across it and each node with a standalone SQL Instance as well. This represents as a cluster with two nodes and two SQL Instances along with each node showing a SQL Instance each. This also takes two licenses as there are two Windows OS machines in the cluster.
A five node WFC with a single SQL Server FCI across it, represents as a cluster with five nodes and a single SQL Server instance and takes five licenses, one for each machine in the cluster.
A single standalone machine with 10 standalone SQL Instances on it will only take only one license.
I hope those examples help clarify how the licensing works for SQL Monitor - as described in your second link above, SQL Monitor auto detects the cluster and all nodes therein and so you will need a license for each Windows OS node in your cluster.
Kind regards,
Alex
Alex B
1 ·
Re: Any known installation issues with version 7. 1. 16. 10851?
Uh oh, shame on me... ;-)
Alex_indiwa
1 ·
Re: Why does Red Gate SQL Prompt add spaces / tabs between table alias and column name?
Hi @Matthew_Sontum
Thanks for the complete script.
If you uncheck 'Indent parentheses contents' , it should work as you expect.
Thanks for the complete script.
If you uncheck 'Indent parentheses contents' , it should work as you expect.
Tianjiao_Li
1 ·
Re: moving the SQL Prompt Tab History database
Hi @AdamWenger,
I haven't tried it with your file, but, I think you have 2
Can you try to :
- Close SSMS
- Edit the file
- Remove <DatabaseFilePath /> (the first in your file). Save the file.
- Open SSMS
Please let me know if it works,
Regards,
Fabiola
I haven't tried it with your file, but, I think you have 2
DatabaseFilePathtags inside:
<?xml version="1.0" encoding="utf-8" standalone="yes"?> <!----> <TabMagicOptions version="1" type="TabMagicOptions"> <Enabled>True</Enabled> <OpenTabsOnStartup>True</OpenTabsOnStartup> <ReconnectTabs>True</ReconnectTabs> <UseKeyboardShortcut>True</UseKeyboardShortcut> <RecentlyClosedTabsWidth>1104</RecentlyClosedTabsWidth> <RecentlyClosedTabsHeight>974</RecentlyClosedTabsHeight> <GridSplitterLeftWidth>280</GridSplitterLeftWidth> <LastRunWasLicensed>True</LastRunWasLicensed> <SelectedFilterType>0</SelectedFilterType> <SelectedFilterTypeForKeyboardShortcut>0</SelectedFilterTypeForKeyboardShortcut> <KeyboardShortcut>Ctrl+Q</KeyboardShortcut> [b]<DatabaseFilePath />[/b] <MaximumQuerySize>2147483647</MaximumQuerySize> <MaximumNumberOfTabsToRestore>100</MaximumNumberOfTabsToRestore> <MaximumNumberOfConnectionsToRestorePerTab>1</MaximumNumberOfConnectionsToRestorePerTab> <ShownRedGateToolbar>True</ShownRedGateToolbar> [b]<DatabaseFilePath>C:\MyPath\Redgate\savedtabs.db</DatabaseFilePath>[/b] </TabMagicOptions>
Can you try to :
- Close SSMS
- Edit the file
- Remove <DatabaseFilePath /> (the first in your file). Save the file.
- Open SSMS
Please let me know if it works,
Regards,
Fabiola
FabiolaB
1 ·
Re: ReadyRoll - database production deployment
The first question, what, if anything, will break in Production is a big part of what the rest of your process should be all about. We generate the safest scripts we can, but there's no guarantee that every script in every situation will always protect against any possible data loss. That's why a process of testing and validation is so vitally important. You want your dev, test and pre-production environments to mirror production as closely as possible in order to validate that the scripts generated and run won't negatively affect production.
If all three environments are sharing a database it sounds as if you're manually running Readyroll against all three. I wouldn't suggest this. Instead, you should be using different tools, such as the Visual Studio Deployment Manager or Octopus to automate secondary processes and testing of the deployments. Every deployment shouldn't be straight out of Visual Studio.
I hope that's a little helpful.
If all three environments are sharing a database it sounds as if you're manually running Readyroll against all three. I wouldn't suggest this. Instead, you should be using different tools, such as the Visual Studio Deployment Manager or Octopus to automate secondary processes and testing of the deployments. Every deployment shouldn't be straight out of Visual Studio.
I hope that's a little helpful.
Grant
1 ·
Re: Code analysis - missing lightbulb and rule explanation
Sorry to waste your time ... this issue has been resolved.
I neglected to mention that I am running SSMS within a windows VM and restarting the VM has resolved the issue!
I neglected to mention that I am running SSMS within a windows VM and restarting the VM has resolved the issue!
Mark_S
1 ·