Settings and activity
2 results found
-
304 votes
Given the upcoming retirement of Azure Data Studio we'd be really interested to hear from our community about where you'll be moving your database development.
If you'd like to chat about your development workflow and hear about our roadmap plans drop me an email and we'll get something set up.
Thanks,
Tim
Daniel Lancelot
supported this idea
·
-
58 votes
We’re going to be reviewing this over the next couple of months, which would be released via the SQL Prompt for Teams EAP (get in touch if you want to know more).
In the meantime please add any other information that you think would be useful.
An error occurred while saving the comment Daniel Lancelot
supported this idea
·
Real shame there has been no progress on this even after over 6 years...
Not functionality that is required often - but generally speaking, when renaming columns, I suspect that the most common use case is to update legacy db's to confirm with a consistent naming strategy - and in most cases this will involve renaming multiple columns within the same tables. For this use case, bulk renaming is essential.
I have just been tasked by a client to perform this task on a legacy db - and I have identified 51 tables with 770 dependant entities that require updating. Most of these tables have between 5 and 20 fields. Using the Smart Rename tool to do this would require somewhere in the region of ~8,000 separate scripts to be generated... which is obviously completely nonsensical.
I believe that for the majority of the alterations I will be quicker to script them manually, as the benefits of being able to update 10 fields in a single stored proc in one go outweigh much of the automation gains for those tables which have a low number of dependencies.