Below are answers to questions asked during the recent webinar. If you have additional questions, please contact Karen Lopez at karenlopez@infoadvisors.com or Thomas LaRock at thomaslarock@confio.com
Q: So this is for both Devleopment and Production correct?
A: Yes, in fact, it's all production to Microsoft. Only you know if it's a development environment or production.
Q: Can you put them in partition? file groups?
A: Neither Partioning nor filegroups/placement is supported. A partitioning-like strategy can be done either by manually managing data across tables or across databases.
Q: These limits are for WASD only or do they apply to virtual servers in the cloud that you install sqlserver on?
A: The presentation today is only about WASD. Running SQL Server on VMs in the cloud or on premises have different design considerations. The limits and features we talked about today apply only to WASD.
Q: Can you speak to backup and recovery?
A: Backup and Recovery functions are not supported. You can do exports and imports and automate those.
Q: Does this mean that TDE is a standard part of the WASD offering and is on whether we ask for it or not?
A: TDE is not supported in WASD
Q: What responsibility does Microsoft take if there is a datacrash since we are not in control of replication anymore?
A: We can't answer on behalf of Microsoft, but when you provision a database, it's a logical database which may be located across many physical servers. There are three replicas behind the scenes and a transaction is considered committed when two have been updated. Read more here: http://msdn.microsoft.com/en-us/library/windowsazure/jj156170.aspx
Q: Our app requires replication - so we won't be able to use this, correct?
A: Replication is not supported directly by WASD. However, if you want to export data to a different server/database for reporting purposes, you can use the automated export facility.
Q: Is there a trial version to test from a personal laptop for the sake of learning?
A: No, WASD doesn't run locally. However, there are trial offers available that you can use to test and learn. Even a paid subscription of a small dataset is very affordable.
Q: What about sequences? I know that identity values are not used, but can we use sequences?
A: SEQUENCEs are not currently supported in WASD. Identity is supported.
Q: Can you specify collation on server stand up?
A: Yes you can
Q: How can I move existing databases to Azure? Or Sync data from my on premise database to Azure?
A: You would need to assess any changes to design that might be necessary. There are features in SSDT that can help you with this assessment. Microsoft has a tutorial on Data Sync http://www.windowsazure.com/en-us/manage/services/sql-databases/getting-started-w-sql-data-sync/
Q: Does WASD expose standard DMVs and DMFs?
A: There are some DMVs supported. See http://msdn.microsoft.com/en-us/library/windowsazure/ee336238.aspx#dmv
Q: Can you run SSRS off WASD?
A: There is a service called Windows Azure SQL Reporting. Read more at http://msdn.microsoft.com/en-us/library/windowsazure/gg430130.aspx
Q: Are all DMVs available for monitoring Host vs. Instance?
A: There are some DMVs supported. See http://msdn.microsoft.com/en-us/library/windowsazure/ee336238.aspx#dmv
Q: How are data files and log files handled? I know when using a standard install, you put them on different "Spindles"?
A: You don't have to worry about managing any physical file placements.
