Allow transact-sql jobs for all service tiers not just elastic scale databases
Allow transact-sql jobs for all service tiers not just Elastic Scale databases
Recently, you rolled out Elastic Database Jobs for Elastic Scale databases which gave users the ability to write t-sql jobs to run on databases. This functionality should be extended to all service tiers so that all users can take advantage of this functionality. While writing jobs using Powershell Runbooks is a serviceable workaround, many organisations have a large amount of jobs that are written in t-sql that would be very difficult to migrate. Giving all users the ability to write t-sql jobs would help to remove this barrier to adoption.
Debra Dove - MSFT commented
Elastic job is not limited to Elastic pools. This was just a Portal limitation in the initial Public Preview. We have re-architected Elastic job to integrate the feature directly in SQL Database and therefore is no longer dependent on other Azure services. Please contact me directly if you are interested in participating in the new Private Preview, we will be completely re-doing the Portal and jobs will have access to all types of target group member types through the Portal. ddove(at)Microsoft(dot)com
Larry E commented
Our organization is planning to migrate between 400-500 databases to SQL Database in the near future, and Elastic Pools with Elastic Jobs are going to be a critical part of our success, and we have databases/pools that will need to be created in both Standard and Premium tiers. Being able to easily run T-SQL scripts against a pool of databases is a must-have feature.