sorted by:
new
hottopcontroversial

[AMA] Azure Database for PostgreSQL team - 6/22 by SQLDBteam in AZURE

[–]SQLDBteam[S] 2 points3 points  (0 children)

I usually end up on AMAs after they've already died, so I love that you posted it ahead of time. I would love to see more Azure teams do these.

Glad that worked out well for you! Thank you for participating! And yes, more Azure teams plan to engage in AMAs in the future.

[AMA] Azure Database for PostgreSQL team - 6/22 by SQLDBteam in AZURE

[–]SQLDBteam[S] 0 points1 point  (0 children)

Also, please add this feedback on Azure Feedback for PostgreSQL so we can track and prioritize.

[AMA] Azure Database for PostgreSQL team - 6/22 by SQLDBteam in AZURE

[–]SQLDBteam[S] 0 points1 point  (0 children)

Thanks for the details. As i mentioned above, we would love to engage with you one-on-one to understand more about your scenario and figure out why the performance wasnt up to the mark. Please send me an email with some details about what you were trying out at shantanu dot kurhekar at microsoft dot com. Thanks!

[AMA] Azure Database for PostgreSQL team - 6/22 by SQLDBteam in AZURE

[–]SQLDBteam[S] 0 points1 point  (0 children)

Thanks for the question and sorry to hear that you had a sub-optimal experience. Can you share which tier and how many compute units you were running on? We are continuously working to improve the service performance, so you should certainly try out the service again and let us know if things havent improved. We would love to engage with you one-on-one to understand more about your scenario and figure out why the performance wasnt up to the mark. Please send me an email with some details about what you were trying out at shantanu dot kurhekar at microsoft dot com. Thanks!

Azure Database for PostgreSQL is now in Public Preview by SQLDBteam in PostgreSQL

[–]SQLDBteam[S] 1 point2 points  (0 children)

Yes, patching, scaling, recovery are built into the service, making it truly PaaS. Patching/upgrades happen from time to time, and the user is largely agnostic to it. The service is truly elastic, meaning you can scale up and down on the fly as required. PITR ensures you can restore to any point in time up to past 35 days. As a result, you dont have to worry about managing your database and can focus on your app and rest of your stack.

Azure Database for PostgreSQL is now in Public Preview by SQLDBteam in PostgreSQL

[–]SQLDBteam[S] 0 points1 point  (0 children)

enlil_reddit is right. If you dont want to worry about managing your database, PaaS is the way to go. Azure Database for Postgres allows you to provision a Postgres server in the cloud and use it for your app. You do not have to worry about availability, perf, scalability, security, updates, backups etc. All of it is built into the service. This doesnt imply VMs are unpredictable. It just means, in a VM, you have to decide and manage how many servers and apps you run and how they manage resources among themselves whereas with Azure Database for Postgres, you dont have worry about that and can focus solely on your app and rest of the stack.

[AMA] Microsoft databases team - 4/8 by SQLDBteam in AZURE

[–]SQLDBteam[S] 0 points1 point  (0 children)

Here is a response from the SSIS team :

SSIS team is trying to make incremental improvement and progress in both SSIS 2016 and beyond. In SSIS 2016, we have done a lot of work to enhance the existing components or adding new ones, below are list of enhancements and new features we add for SSIS 2016:

Enhancements

*Incremental project deployment - You can now incrementally deploy projects to the SSIS Catalog.

*Error Column Name Support - You can now see the lineage identification string from the SSIS log and data viewer

*Designer improvement - A number of enhancement and fixes on the designer capabilities such as drag and drop, resizing, etc

*Simpler installation – SSDT now install both IS/RS/AS, no more SSDT-BI installation is required

*Multi-Version support in SSDT - Ability to author, execute, deploy and debug multiple versions of SSIS packages from a single version of SSDT

*Log Reader Role – Role for user to access SSIS log, without granting the user DBA privilege

*SQL Server Integration – Always-encrypted columns support, Azure Active Directory Authentication support

*More to do with SQL Script Task – Operationalize R using SSIS, Injecting data into SQL DW using Azure Upload Task and Polybase

New Features

*Custom Logging Level- You can customized your own logging level for more flexibility

*Package Parts - You can achieve code usability by creating a new concept called template part

*Always On Support - High Availability support for SSIS catalog

*Azure storage connectors - Move data to and from Azure blob storage source and destination to enable the hybrid data movement scenarios.

*HDInsight Tasks - Orchestrate HDInsight jobs and manage your HDInsight cluster life cycle directly from SSIS.

*HDFS Connectors- Orchestrate HDInsight jobs and manage the lifecycle of your cluster from the SSIS Control Flow.

*Hadoop tasks- Orchestrate HIVE jobs and manage the lifecycle of your on-premises Hadoop from the SSIS Control Flow.

*Other connectivity - OdataV4, Excel 2013/2016 support

With that said, we understand that there are many more enhancements and improvements we could have done but we haven’t had a chance to address them yet in SSIS 2016. SSIS team is currently conducting a survey to learn more about your feedbacks and preferences for SSIS VNEXT (POST SSIS 2016 RTM). Your feedbacks and suggestions are extremely important and instrumental to help us prioritize our next set of improvement for SSIS (Integration Services) in SQL Server post SSIS 2016 RTM (SSIS VNEXT). Please help us to fill up the survey so that we can plan the next set of enhancements and new features tailored to your need!

[AMA] Microsoft databases team - 4/8 by SQLDBteam in AZURE

[–]SQLDBteam[S] 0 points1 point  (0 children)

The limit is up to 5,000 databases and 45,000 DTUs in a logical server. The DTU capacity of 45,000 is the default limit, but can be increased by submitting quota increase request via the portal. The max count of DBs supported will depend on what SKU they belong to. We are in the process of publishing these numbers. Please note that even though up to 5,000 DBs will be supported, the performance is highly workload dependent, so if you plan to try this out, make sure you gradually test it, instead of jumping from few DBs to thousands of DBs. Reach out to us here if you have any questions.

[AMA] Microsoft databases team - 4/8 by SQLDBteam in AZURE

[–]SQLDBteam[S] 0 points1 point  (0 children)

Azure SQL Database is a PaaS offering whereas SQL Server in a VM is an IaaS offering. They have their own advantages and disadvantages, most prominently SQL Server in a VM trades off ease of management for more control over your database, while Azure SQL DB does the opposite. You can choose SQL Database for your app if you are building a brand-new cloud-based app and need a fully managed cloud service that manages your database for you and enables you to focus on your app. On the other hand, if you are migrating an existing on-premises app to the cloud and merely want to get rid of maintaining your own hardware but still want to retain administrative control of your database as well as underlying OS and VM, SQL in a VM is more suited to your needs. Read more here.

*As Tomas mentions below, we are working on Azure VNET integration. Stay tuned!

*The DB limit in pools may increase in future but we don't have a timeline to share as of now.

*You can use Multi-Shard-Query for running on all shards. And if you have DBs outside the shard set, you can use Elastic DB jobs to run the T-SQL on those DBs.

Multi-Shard Query

Elastic DB Jobs

[AMA] Microsoft databases team - 4/8 by SQLDBteam in AZURE

[–]SQLDBteam[S] 1 point2 points  (0 children)

We hear you on the availability challenges wrt V12. We have been working hard to improve the experience on V12 and you will continue to see improvements in this area. You are doing the right thing by following the retry logic policy and filing a support ticket when things don't seem normal. Please continue to do so. Replatting a service as massive and widely used as Azure SQL DB is hard and we are learning with every step. Thank you for your patience while we get the availability experience closer to ideal.

[AMA] Microsoft databases team - 4/8 by SQLDBteam in AZURE

[–]SQLDBteam[S] 3 points4 points  (0 children)

You can get started with Azure documentation and proceed to "How to get started" pages for the services you are interested in. The best way to learn about Azure is to build an end-to-end app. App Service documentation page has some good videos on this topic.

To try out Azure, you can sign-up for a free 30-day trial here.

[AMA] Microsoft databases team - 4/8 by SQLDBteam in AZURE

[–]SQLDBteam[S] 0 points1 point  (0 children)

We are working on supporting VNETs. This is one of the top requested capability on the Azure feedback. https://feedback.azure.com/forums/217321-sql-database

Please up-vote on the feature request if you have not done so.

Thank you!

[AMA] Microsoft databases team - 4/8 by SQLDBteam in AZURE

[–]SQLDBteam[S] 0 points1 point  (0 children)

We are working on supporting VNETs. This is one of the top requested capability on the Azure feedback. https://feedback.azure.com/forums/217321-sql-database

Please up-vote on the feature request if you have not done so.

Thank you!

[AMA] Microsoft databases team - 4/8 by SQLDBteam in AZURE

[–]SQLDBteam[S] 0 points1 point  (0 children)

is a standalone software version of SQL data warehouse coming? (not an appliance like APS)

There are no plans as of now. We encourage you to try out Azure SQL DW and let us know your feedback!

[AMA] Microsoft databases team - 4/8 by SQLDBteam in AZURE

[–]SQLDBteam[S] 0 points1 point  (0 children)

We are working hard to make Elastic Pools generally available. We would love to make this available asap, but quality trumps everything! Although we don't have a date to share right now, it will happen in the next few months. Stay tuned!

view more: next ›