User profile for ben_b

Hi @Diogo, @David Atkinson, @Kendra_Little I haven't been using Redgate SQL Source Control for the last couple of years (we've been using Visual Studio and Database projects) but I am now looking at Redgate SQL Source Control again as I prefer the 'connected' method of development. I kind of agree with the following statement made by the original poster. "Ideally, branching would be built into the UI so I could, at a minimum, switch branches". Is this something that you guys are considering? I saw a video where Kendra uses sublime merge for handling conflicts, I was wondering what the redgate teams use for creating/switching branches (excluding the command line)? cheers Ben / comments

Hi @Diogo, @David Atkinson, @Kendra_Little I haven't been using Redgate SQL Source Control for the last couple of years (we've been using Visual Studio and Database projects) but I am now looking a...

0 votes

I showed this tool to a DBA and they asked if they could import their server lists from their existing CMS registered servers (Central Management Server)... would be a good feature! / comments

I showed this tool to a DBA and they asked if they could import their server lists from their existing CMS registered servers (Central Management Server)... would be a good feature!

0 votes

Hi - this forum is just for red-gate products. for Microsoft SSRS you are probably better off asking the question on somewhere like stack overflow or looking for a tutorial on youtube. that said, as I am here. you create the report in the client tool SSDT https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?view=sql-server-2017 then you will need to install the server component (where you will deploy the report) https://www.microsoft.com/en-us/download/details.aspx?id=55252 you configure your project properties and deploy from within the client tool SSDT. cheers Ben / comments

Hi - this forum is just for red-gate products. for Microsoft SSRS you are probably better off asking the question on somewhere like stack overflow or looking for a tutorial on youtube.that said, a...

0 votes

cheers Mike - I believe this has worked!! I don't work too much with triggers, do you know why I wasn't able to find the objects through SSMS / SQL Search? / comments

cheers Mike - I believe this has worked!! I don't work too much with triggers, do you know why I wasn't able to find the objects through SSMS / SQL Search?

0 votes

ah ok - I just realised it was at Server Level. Server>>Server Objects>>Triggers. Cheers! / comments

ah ok - I just realised it was at Server Level. Server>>Server Objects>>Triggers. Cheers!

0 votes

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

How can we help you today?

ben_b

Comments