FYI, This request has been made a many times. In just the 1st 3 "pages" of this forum I've found 5 requests all for the same thing as this suggestion.
Had we all searched for our request prior to raising a new one, you might discover that this is a highly sought after feature. As scrolling thru hundreds of tables & views sucks (is very unproductive). As does typing the table name into the filter each time you want a new table.
Please consider a menu button in Object explorer pane. where we can toggle "enable/disable" the schema grouping nodes, for the database in question. That way you don't have pointless levels of schema groups where there is only 1 schema (dbo) or only a screenful of tables or only a few tables in the schema. But do get the collapsed schema node when there are more than ~10 tables in the schema or lots of schemas in the database.
Below are suggestions for the same thing:-
(sometimes CLOSED as respondee clearly didn't understand the request & so talks about MS documentation)
Probably some more suggestions requesting this. I stopped looking after scrolling down 3 screens
Apologies closed in error. Reopening
I realise that it is possible to write a powershell script that identifies all resources in a VM (disk nic). Deletes the VM, Then recreates the VM with a new name. It runs in less than a minute.
It is also possible to do something similar to rename disks. (copy to new name, delete old & reattach)
As I could write a Rename-AzureRmVM & Rename-AzureRMManagedDisk function in a short period of time. (less than 4.5 years) Perhaps the Azure team might consider doing the same thing, while they are thinking about doing it better in the API.
Thanks! This is something we are considering as we add enhancements to auto-configuration. You may be able to do this using Azure Files, today.
I know this is an old thread, Has any progress been made?
I need to add the .NET 3.5 Feature. (And related ASP.NET features) would be so much easier if I could specify a SOURCE: in my ARM + DSC scripts rather than downloading an entire ISO image just to map it for this one feature.
US Date format causes a massive number of bugs. And once Windows is installed it is a real pain to change the machine default to DMY.
Most powershell commands are User Session based. So to change DateFormat, Culture, Location etc you are left to edit the registry.
If we can set the Regional Settings at the Creation of the VM is makes DSC & automated builds much simpler.
Thanks, Aaron. You can pass into PowerShell and REST the timezone you want your VM deployed as. I think the feedback to do this via the portal is also good.
I'm not convinced that the location of the Azure Data Center is a great basis for the default language, date format etc of the VM. Many use UTC. That said if you are in UK, Singapore, Australia, The current default of USA dates is the worst option. MDY is alien to all but the USA. So this idea has some merit.
A better option would be to ensure we have the ability to set these on creation of the VM. Both via the Portal and the ARM template.
Thanks for the feedback.
We do have the ability to switch languages in the footer. Based on the language selection, we update the date formats as well. But for English we currently default to US formats. We’ll look into adding support for UK as well.
This is something we’re thinking about, but would like to ensure that we’re providing a sufficiently robust set of capabilities within the template language syntax itself.
What scenarios are “overly complicated and hard to maintain”? This will help us understand where we need to invest.
1. Be nice if the Templates were Idempotent. Currently it has issues with Disks. Which if they already exist causes it to crash.
2. I'd like greater interdependence between values. eg:
When I drop from a GS5 (prod env) to a GS3(dev2 env), I need to create significantly fewer disks per storage. Or fewer storage groups with same number of disks. So I'd like a rule, function or something that could use a value of one parameter to control the generation of another.
Perhaps something more Powershell DSC like, to create the template like a MOF file.
3. I'd like some attribute on the Disks I create, so that I can know what they are within Windows.
eg: I create 10 * P10's for the Log, 16 * P30's for the Data, 16 * P30's for the Indexes & a few more for TempDB. & some normal HDD's for other stuff. In Windows when I RAID them together, I need to ensure I group the P10's with P10's & so on. Be nice if there was a Tag, property or something I could set when I create the disk So I could use it in Windows storage pools.
4. Depending on which machines we enable in the specific environment build, we'd then like to have the appropriate rules enables in the NSG. eg: Only if we enable the DataMart VM should we open port 1433. If we don't add the WEB VMs in the TEST4 environment, then we don't open ports 80, 433 etc
In short we create complete environments of 8+ Machines ( some have scale-out). Then want to swap the machine sizes depending on if it is Production, Pre-Prod, UAT, Dev, Test. And tweak it based on the size of Dev/Test environment we need to spin up.
We need the disks & networking to intelligently change based on the limits of the chosen VM size.
It would also be nice to use the same script to tear it down again. If we spin up a large stress test, I'd like to know I got rid of it all correctly, often even with Tags we miss a subnet, a nic or disk. And it is time-consuming. We also delete AD accounts but that is more DSC related.
This is a very interesting idea! We would like to know what specific usage you have in mind – for example, are you continuously generating operational logs on-prem and would like an utility to easily upload these files into blob storage for further analysis, maybe using HDInsight? Please post your comments!
This could be handy to include on-prem SQL FileStream data into Azure Blob or File store objects.
In bound. Web users upload media (pictures, video, audio) which eventually makes it into the more secure on-Prem ODS. (I'm thinking of a medical system here, where patients & regional medics could "cache" this stuff via the cloud.
Out Bound: Typical publishing scenario. On-Prem app that uses file streaming could have the media loaded up to a Blob store which is mapped to a CDN.