David

My feedback

  1. 552 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    19 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    David supported this idea  · 
  2. 29 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    David commented  · 

    Encountered this recently on Microsoft SQL Server 2017 CU22 14.0.3356.20 (X64) with an ETL MERGE routine which has been running fine for months.

    We added a non-clustered index on the named history table so that we can more efficiently query for deleted records (where the system-temporal 'to' date < 9999), then we see the bug appear.

    Dropping that index has fixed it, but would like a better solution.
    (will try a Column Index workaround suggested below)

    David supported this idea  · 
  3. 30 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    16 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 0

    <=-=Mar 7 2017 2:10AM=-=>

    Thank you for taking time to post this issue!
    I can confirm that Design option in SSMS Object Explorer is not available for temporal (system-versioned) tables.
    Unfortunately, we do not plan to include a fix for this issue in the upcoming release.
    We might include it as an improvement in a future release, though.
    How important for you is to have this option available for temporal tables?

    David supported this idea  · 
  4. 9 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    David commented  · 

    Same issue still with SQL Express 2019 and latest SSMS 18.7.1.
    Any workaround?

    David supported this idea  · 
  5. 262 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    We are very excited to announce the Public Preview of Azure Resource Mover https://aka.ms/resource-mover-preview

    Azure Resource Mover is a new free service that greatly reduces customer time and effort needed to move resources across regions by providing a built-in dependency analysis, planning, and testing that ensures the resources are prepared to move and then successfully moved to the desired region.

    Currently, using this capability, customers can easily move their

    Virtual machines with managed disks,
    Networking components (NIC, VNET, NSG, Load Balancer, Public IP)
    and SQL Azure resources (Database and Elastic pool)

    from one Azure region to another. The service is available through the Azure portal, PowerShell, and SDKs with any Azure subscription and you can move resources from any public region to any other public region.

    We will be improving the resource support coverage in the coming months.

    Support for moving customer production workloads is now…

    David supported this idea  · 
  6. 192 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    33 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    David commented  · 

    Like the others, source control is even more important in SSMS 18+

    David supported this idea  · 

Feedback and Knowledge Base