Hot answers tagged

3

Point 2, can be addressed by using AWS RDS to back up data for you. Otherwise, you manually need to create a snapshot of your EC2 instance but this involved a tiny bit of downtime and will cost money to store on S3. Point 1, just restore the database Either way, you want a high level of functionality that you don't want to pay for, so our options for ...


3

The VM has it's private addresses translated to a publicly routable IP address at the network boundary - this is called network address translation. when you assign a public IP to an instance in the cloud what you are really doing is setting up a NAT rule. Inside the VM you continue to work and configure software as you would on a private network, so if your ...


3

Your best bet is to copy the mdf and ldf files to another location. Then uninstall the 2012 version, install the 2014 version. Then you just need to drop your mdf and ldf files into the DATA directory and then browse to the Database node in SSMS, right click then select Attach... It will pop up a dialog. Point it to your mdf and ldf files and you should be ...


2

Execution plans: OBVIOUSLY. As does restarting the server - these are kept in memory and generated on demand. Which also means you never collected them over the years. Unless you have a never patched system which would be a much bigger problem. Statistics: no, those are actually objects in the database, so they transfer. Here you also did NOT collect them ...


2

RDS has recently added a stored procedure to accomplish this: EXEC rdsadmin.dbo.rds_modify_db_name N'<OldName>', N'<NewName>' source: http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.SQLServer.CommonDBATasks.html#Appendix.SQLServer.CommonDBATasks.RenamingDB


1

This isn't really an Azure question, its a "how do I do SQL clustering question". You can't just share a SQL database between two VM's and it magically work, you would need to setup your VM's in a cluster to share the SQL workload between them. Clustering in Azure is slightly different than on premises as you can't use shared disk storage for clustering ...


1

Agreed -- db mirroring would be highly unlikely in this situation since it works best if it's persistent and would need manual intervention every time you turned your desktop system on. Snapshot Replication is the only realistic option in the replication world, and there's no benefit gained over using a simple database backup and restore or AWS snapshot.



Only top voted, non community-wiki answers of a minimum length are eligible