User profile for ben_b

If I understand the question correctly, when configuring the database distribution lists you can expand the server node to drag in the database names. when I first used it I dragged the server node across and this was defaulting to .master so I was having to stick in USE statements - I thought that was how it worked until I looked again. / comments

If I understand the question correctly, when configuring the database distribution lists you can expand the server node to drag in the database names. when I first used it I dragged the server nod...

0 votes

Hi Tugberk First off I'll have to admit that I've never been involved with Microsoft licensing and I find the whole thing really opaque. I would also say that in most companies I've worked in, there hasn't really been anyone who understood it! As I understand it SQL Estate manager allows you to classify instances as Production, Test etc. It also picks up information regarding the number of cores, the sql server version/edition, the amount of memory on the server etc. If you are only paying for production instances, could it aggregate the above information so you can compare the number of core, standard/enterprise licenses you should have vs the number you have actually purchased. Other possible use cases might be recommendations - you may have a 2016 SP1 enterprise edition running with less than 128GB ram and no high-availability it might suggest that it would be worth considering standard edition. Or you may have a server running 2-cores but the minimum licensing is 4 cores so it may flag this up. I know CAL licensing, software assurance and legacy editions (i.e. Business Intelligence edition etc) may add too many variables into the mix, but licensing is part of what I would consider managing a SQL Server estate. Most companies I have worked in grow their production estate quite frequently (projects go live and a new production sql server is suddenly in play) but rarely decommission - and I very much doubt that licensing is considered when the pressure is on. Any tool that could help bring even a little clarity to this would be welcomed cheers Ben p.s. I still haven't installed the trial version of SQL Estate Manager so I need to do that - i'll also install the following and will probably have a better understanding of it all afterwards. 1. https://blogs.msdn.microsoft.com/markm/2015/02/17/inventorying-sql-servers-with-the-microsoft-assessment-and-planning-toolkit-map/ 2. idera inventory manager / comments

Hi Tugberk First off I'll have to admit that I've never been involved with Microsoft licensing and I find the whole thing really opaque. I would also say that in most companies I've worked in, the...

0 votes

is the product intended to help with Microsoft licensing at all? Agree with the above that I would be interested in Standalone trial / comments

is the product intended to help with Microsoft licensing at all? Agree with the above that I would be interested in Standalone trial

0 votes

This is a very reductive explanation but just to get you started... Red-Gate toolbelt = embedded inside SQL Server Management Studio Toad for Sql Server = a completely separate IDE If you have a team of SQL Server developers that have been using SSMS for years and are comfortable with it, they will be able to integrate and pick-up Red-Gates tools very quickly. If you have a team of Oracle developers who have all been using TOAD for years and you are migrating to SQL Server, you will probably find this will ease the transition. If you have a team of Oracle developers who have all been Oracle SQL Developer for years and you are migrating to SQL Server, Red-Gate again would be the better choice. Just so you are aware, I only started using Toad a few months ago against Oracle. It has a lot of features but I hated the cluttered interface and millions of buttons so I switched to Oracle Sql Developer. I would start off concentrating on red gate SQL Prompt and spend some time watching the short training videos on youtube. / comments

This is a very reductive explanation but just to get you started... Red-Gate toolbelt = embedded inside SQL Server Management Studio Toad for Sql Server = a completely separate IDE If you have a te...

0 votes

i think you could you use the standalone 'sql compare' product for that - on one side choose the database and on the other choose the folder in the source control repository? failing that, the DLM dashboard will detect 'drift' for you...maybe worth having a look at that. / comments

i think you could you use the standalone 'sql compare' product for that - on one side choose the database and on the other choose the folder in the source control repository? failing that, the DLM...

0 votes

Stable and easily adaptable solutions occur in highly predictable environments. Predictability comes from consistency, a by-product of standardisation and automation. / comments

Stable and easily adaptable solutions occur in highly predictable environments. Predictability comes from consistency, a by-product of standardisation and automation.

0 votes

this could potentially be a very useful tool for people in my position. we have chronic environment problems that aren't going to be remedied anytime soon. we also have shared development databases (with around 8 devs). Our TFS has temporarily been abandoned because of multiple successful deployments being backed out of production because of unforeseen integration issues that came out of the woodwork at a later date. i'm thinking about using this as the beginning of our devOps journey (one script per object, one folder per feature) with the basic principle of deploying the same artefacts (in this case a folder of scripts) against prod as the ones that were used to deploy to test. we would use it for running multiple scripts against one database as opposed to running against multiple databases at the same time. it would essentially be a very simple script deployment tool but the logging, parsing etc will be very useful. I know that this is far from a modern development pipeline but could be the first step in restoring some control, although we are putting off the inevitable which is to stop dev work and do a complete reset of environments and TFS. I have just noticed it has been added to the toolbelt essentials as well which is a welcome addition. / comments

this could potentially be a very useful tool for people in my position. we have chronic environment problems that aren't going to be remedied anytime soon. we also have shared development databas...

0 votes

I'm thinking of using Prompt's 'find invalid objects' feature instead of a 'build' on a database project in visual studio - so will keep an eye on this one as well. we've got the ball rolling on purchasing sql prompt licenses for everyone and I think, as a team, we will eventually abandon database projects in VS and go back to SSMS. / comments

I'm thinking of using Prompt's 'find invalid objects' feature instead of a 'build' on a database project in visual studio - so will keep an eye on this one as well. we've got the ball rolling on p...

0 votes

thanks for highlighting that - I think the hard work on this tool has already been done but the UI needs a bit of a revisit as I would have expected that to be selected by default (and not so hidden away). / comments

thanks for highlighting that - I think the hard work on this tool has already been done but the UI needs a bit of a revisit as I would have expected that to be selected by default (and not so hidde...

0 votes

this is a good idea. I just had a google for one and got directed here. I've demo'd SQL prompt to people many times and a cheat sheet would be a handy material for them to take away / comments

this is a good idea. I just had a google for one and got directed here. I've demo'd SQL prompt to people many times and a cheat sheet would be a handy material for them to take away

0 votes

How can we help you today?

ben_b

Comments