SQL Database

How can we improve Azure SQL Database?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Master Data Services (MDS) configured to Azure SQL.

    Master Data Services (MDS) currently does not support having Azure SQL DB as it Data source. We have entity store on PaaS and MDS on IaaS and we want to MDS to be configured to Azure SQL instead of on-prem SQL.
    Or even better to have MDS as PaaS.

    83 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  2. SqlBulkCopy.WriteToServer fails on SQL Azure if destination table is temporary

    SqlBulkCopy.WriteToServer fails on SQL Azure if destination table is temporary.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 30

    <=-=Oct 25 2011 2:38PM=-=>

    Hi Andrey,

    Thanks for reporting this issue. SqlBulkCopy.WriteToServer does not work in this case because SQL Azure currently does not support temp table. We will route this bug to SQL Azure team so that they can follow up with you.

    Young Gah Kim
    Development Lead
    ADO.NET Managed Providers and DataSet Team

    <=-=Apr 19 2012 6:15PM=-=>

    Hello Andrey,
    Thanks for reporting the issue. The problem is due to the fact that SQL Azure doesn’t support 3-part names for stored procedure calls. In this case, the driver/provider use tempdb.sys.sp_* syntax to access certain stored procedures that provide metadata about objects and these calls fail. We are looking at resolving the issue & enabling 3-part names for tempdb calls.
    Otherwise, you can use temporary tables in SQL Azure fine – we do support it with the restriction mentioned above. Additionally, you can’t create temporary tables…

  • Don't see your idea?

SQL Database

Feedback and Knowledge Base