Comments
Sort by recent activity
hi @Sergio R - I did spend some time with the command line using the include switch and made some progress but it was a struggle and wasnt "ingeniously simple"... I've created a very bad screen mock-up of what I was thinking to see if anyone else sees value in what i'm talking about. its based on the comparison pane inside SQL Source Control... its basically being able to run something like K-Diff or WinMerge from within SSMS. cheers Ben [image] / comments
hi @Sergio R - I did spend some time with the command line using the include switch and made some progress but it was a struggle and wasnt "ingeniously simple"... I've created a very bad screen moc...
thanks very much for taking the time to answer. I will definitely check out the command line and get back to you. / comments
thanks very much for taking the time to answer. I will definitely check out the command line and get back to you.
Hello, this isn't specifically a red-gate question but there are some red-gate resources that can help you. this simple talk article looks decent https://www.red-gate.com/simple-talk/sql/database-administration/preparing-to-upgrade-your-sql-server/ alternatively, you can search SQLServerCentral and/or post a question on the forum. The big thing with SQL Server 2016 SP1 is that you get most Enterprise Features included with Standard Edition. I've migrated loads of databases and never really had any issues. I'm sure there is some code analysis features in SQL Prompt that would alert you early. Best advice I can give is don't wait around, give it a bash on a test environment and you will have a feel pretty quickly of how difficult the task will be. / comments
Hello, this isn't specifically a red-gate question but there are some red-gate resources that can help you.this simple talk article looks decenthttps://www.red-gate.com/simple-talk/sql/database-adm...
I love SQL Prompt because it gives me back my time - in abundance, every single day. / comments
I love SQL Prompt because it gives me back my time - in abundance, every single day.
"it would be great if you could try to switch branches and let us know if the end result in the Get Latest screen is as you would expect" - I will have a play around next week and get back to you / comments
"it would be great if you could try to switch branches and let us know if the end result in the Get Latest screen is as you would expect" - I will have a play around next week and get back to you
another advantage or RG Sql Source Control is that you dont have the added hassle of sorting out cross database references that you find with Visual Studio database projects. so, i'm putting the full list below for my own notes
no annoying conflicts on the .dbproj file
no re-keying from SSMS to Visual Studio (don't have to keep jumping around between IDEs)
much nicer interface
schema comparison less buggy
you can see other people's changes more easily
cross-db references can be annoying in VS database projects
/ comments
another advantage or RG Sql Source Control is that you dont have the added hassle of sorting out cross database references that you find with Visual Studio database projects.so, i'm putting the ful...
just been playing around with this. two more possible advantages of RedGate 1. Visual Studio db projects can have duplicate object definitions 2. I think you can't (easily) see the SQL definitions in dacpacs but you can in SCA nu-get packages (unconfirmed!) / comments
just been playing around with this. two more possible advantages of RedGate1. Visual Studio db projects can have duplicate object definitions2. I think you can't (easily) see the SQL definitions...
"So you're happy with seeing the changes in the branch appearing as items in the 'get latest' screen?" I think so yep. "This should work as expect today except that you'll need to type the git checkout commands manually (it would be great if you could try to switch branches and let us know if the end result in the Get Latest screen is as you would expect)." Typing the git commands manually is what I was I hoping the RedGate UI could do for me! I like having as few applications open as poss, others in my team dont want to use the command line at all. What is the specific reason you wouldn't want it to auto-sync your DB with the state of the new branch? We use shared databases environments at the moment. We have laptops with 250gb hard disks but our DWH databases are much bigger and we haven't looked at making smaller copies because its a bit of a spaghetti architecture. Also, if there is a lot of context switching then you may have a branch you haven't touched for a week or so and its nice to have the control to put things back manually and refresh your memory of what you were doing. cheers, Ben [image] / comments
"So you're happy with seeing the changes in the branch appearing as items in the 'get latest' screen?" I think so yep."This should work as expect today except that you'll need to type the git chec...
Thanks david. I would probably like to be able to create and switch branches from redgate sql source control gui within SSMS, so I can stay in one place. I don't think i would need/want the database to change after each switch of branch though, I could get the database & branch in the position I want using the 'Commit' & 'Get Latest' tabs within RedGate Sql Source Control. What I would ideally be after is this screen which pops up when you click the arrow next to your current branch. [image] Have it appear when you click the branch label in Redgate Sql Source Control [image] Hope that makes sense. I've only been using git for ~7 months so i'm no expert ! / comments
Thanks david. I would probably like to be able to create and switch branches from redgate sql source control gui within SSMS, so I can stay in one place. I don't think i would need/want the datab...
p.s. i actually think there are quite a few advantages of using redgate sql source control vs visual studio/database projects such as
no annoying conflicts on the .dbproj file
no re-keying from SSMS to Visual Studio (don't have to keep jumping around between IDEs)
much nicer interface
schema comparison less buggy
you can see other people's changes more easily
visual studio has improved massively in the last 2 years tho. The pros/cons of each is what i'm currently researching (including the pros/cons between the redgate and microsoft build/release plug-ins in Azure DevOps). But one small advantage of Visual Studio is that it has the branch management gui. cheers Ben / comments
p.s. i actually think there are quite a few advantages of using redgate sql source control vs visual studio/database projectssuch as
no annoying conflicts on the .dbproj file
no re-keying from SS...