Q: I’m nervous about migrating. What can be done to ease this process?
A: Don’t be nervous, Tallan has a number of clients that have successfully taken the plunge! As with any software, there are bugs and issues that have been and continue to be addressed, but overall reception so far has been great. If you’re migrating from SQL Server 2005, there are a few more hurdles to jump than from later versions. And the more complex your current configuration is (i.e., uses replication, has other parts of the SQL Server stack), the more planning you should do to make sure it goes off without a hitch.
Tallan has helped many clients execute on migration since RTM release of SQL Server 2016, each with varying degrees of complexity. To date there have been no showstoppers in migrating, and no loss of performance or functionality. Clients love the new features, especially the fresh new look, feel and functionality of Reporting Services and the In-Memory features.
Q: Can Stretch Database be implemented without any database structure changes?
A: Yes. Databases and tables are “stretched” using simple configuration settings. There are no database changes required to implement Stretch Database.
Q: Can Stretch Database be implemented without any application changes?
A: Yes. The location of the data in a “stretched” table is transparent to a SQL Server query. No application or query changes are necessary to access the local or archived data in a stretched table.
Q: What are the restrictions of Stretch Database?
A: There are some limitations to where Stretch Database can be used.
- Some column datatypes are not supported (text, image, timestamp, XML). And computed columns are not allowed.
- Tables that are replicated or are using Change Data Capture cannot be stretched.
- Tables with Full-Text Indexes and tables referenced in an Indexed View also cannot be stretched.
- And tables that are referenced by a foreign key cannot be stretched.
A full list of Stretch Database limitations can be found here.
Click here for information about the Microsoft provided Stretch Database Advisor tool to help determine if a database and/or table qualifies for Stretch Database.
Q: What are the costs associated with using Stretch Database?
A: Stretch Database charges are billed in two categories, Storage and Compute. Storage refers to the cost of maintaining your data in the Stretch Azure database. Storage is charged at a fixed price per GB.
Compute is the speed that your data is transmitted to and from Azure and the speed of computations against the data. Compute costs are charged by DSUs (Database Stretch Unit). You are charged based on how many DSUs are used during a period. There are multiple DSU levels available that are priced according to the performance they provide. The DSU level can be scaled up or down to tune performance at any time.
For more information about SQL Server Stretch Database pricing, click here .
Q: What are R Services in SQL Server 2016?
A: Brings R execution into SQL Server and exposes it through the T-SQL interface. It overcomes some of the issues regarding performance and scale, allowing users to work on very large data sets in SQL. There is also no need for data movement between the database and the R computation because there are now located on the same database.