SQL Database

  1. Enable access to SQL Server/ Storage accounts via P2S VPN

    Currently when the Azure resources (SQL server/ Storage accounts) are associated with P2S VPN VNET they are accessible in the VMs created in same subnet only via client tools. If possible kindly allow the resource access via the VPN connection on the client machine. In this case a User doesn't need to include the Network client IP in the allowed network range and it will allow to keep Firewall configuration restricted to some office network (if required) and baseline minimal networks in advanced security.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. I'm Store SQL Data base in AOS Project but it was provides the some errors

    Recently I store my data in Sql but it was presents the some error messages.... can u solve this data base problem - https://aostv.in/

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Deploy SSDT database project: update table with security policy fails when column was added

    During publishing of a SSDT Database Project, after adding a column on a table with an view and a security policy on Azure SQL Database, deployment fails with this error message:

    (51,1): SQL72014: .Net SqlClient Data Provider: Msg 3729, Level 16, State 3, Procedure vDemo, Line 1 Cannot ALTER 'dbo.vDemo' because it is being referenced by object 'SecurityPolicy_Demo'.
    (51,0): SQL72045: Script execution error. The executed script:
    ALTER VIEW [dbo].[vDemo]
    AS
    SELECT Id,
    CustomerId,
    Col01
    FROM [dbo].[Demo];

    1 vote
    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 →
  4. Obfuscate passwords in Azure SQL Audit Logs

    When using the query 'CREATE USER xxxxx WITH PASSWORD = 'xxxxxx', the password is stored by Azure SQL Auditing. This password can then be viewed by anybody with access to the SQL Audit Files, and if Log Analytics is configured, anybody with access to the Log Analytics instance. It would be more secure if passwords were not stored to the SQL Audit logs.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add DB tier tile in Azure dashboard

    Please add a tile in Azure Dashboard so you can see the current DB tier. There is a workaround that we can monitor DTU limit (e.g. 3000 DTU) in last 30 minutes, but it does not show the actual current tier. (e.g. S12).

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. Give access to Full Text Search crawl logs.

    Troubleshooting Full Text Search issues would be much easier having access to FTS crawl logs.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Azure SQL Managed Instance - Encrypt multiple db's with different asymmetric keys

    The big blocker for us moving to Azure SQL Managed Instance is that we will not be able to provide our customers the option of BYOK.

    We need to be able to set a separate asymmetric key as the TDE protector for each database, allowing our customers to set their own encryption key for their own database.

    Right now, Managed Instances allows only setting one TDE protector per instance, not per database. We cannot be expected to pay for an additional instance for each database just to be able to encrypt each database with different keys. This is already possible…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Support update of backup retention days via the azure cli

    The Azure CLI for SQL MI instances does not support update of the backup retention time. The documentation does not seem to refer to such an option, leaving only powershell and the REST APIs as options.

    4 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 →
  10. Ability to create consolidated Vulnerability scan report across multiple sql servers/databases

    Allow to create aggregate reports by sql servers and its databases instead of database by database which does not scale

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Azure SQL managed instance replication - general availability time frame?

    I understand replication for Azure SQL Managed instance is in preview mode. Wondering, if you have any approximate time frame when it can be used for Production database. Looks like decision makers in my company would feel comfortable once the product is in 'general availability' mode

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. make harder to delete resources on azure portal

    Clicking "Delete" on pinned SQL Database in the Azure Portal Dashboard doesn't ask for confirmation. This should be fixed. Also, two-factor authentication for delete actions would be perfect.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Authenticate using Azure AD DS

    Just like how Azure Files supports authenticating using Azure AD Credentials from Azure AD DS domain joined machines, it would be great to be able to authenticate to Azure SQL in a similar manner.

    We have some legacy apps running in Azure VMs that users log into, it would be great to be able to authenticate to SQL using their current logged in credentials (similar to how Windows or Azure AD Integrated authentication works)

    Currently we are prompting them for credentials and using the Active Directory Password authentication mode.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Azure SQL Managed Instance DNS alias

    Just like DNS alias is supported for Azure SQL database https://docs.microsoft.com/en-us/azure/sql-database/dns-alias-overview,
    we need same functionality supported for Azure SQL managed instance, abstraction layer to redirect traffic during upgrades, massive data maintenance etc.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Hyperscale: Bring back copy database

    We really, really need the ability to copy Hyperscale databases just like other Azure SQL tiers!

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Support AzureRm powershell sending database/server audit logs to write to Log Analytics

    Azure Automation account still dont fully support Az modules. It is very hard to setup a new Automation account with Az only.

    I have a lot of Runbooks written using AzureRm and would like the RM to be updated to include the log analytics workspace instead of only storage.

    AZ command: (supports Log Analytics)
    =========================
    Set-AzSqlServerAuditing
    Set-AzSqlDatabaseAuditing

    AzureRm Command: (does not support Log Analytics)
    ===================================

    Set-AzureRmSqlServerAuditing
    Set-AzureRmSqlDatabaseAuditing

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Enable XE sqlserver.backup_restore_progress_trace

    This event was introduced in SQL Server 2016 and is also available in Azure SQL Database Managed Instance.
    In order to track (automated) backup times/running time and restore progress this would be very helpful in backup/restore monitoring for Azure SQL Database.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Bug when exporting job database

    Error encountered during the service operation.
    One or more unsupported elements were found in the schema used as part of a data package.
    Error SQL71501: Error validating element [jobs_internal].[visible_targets_formatted]: View: [jobs_internal].[visible_targets_formatted] contains an unresolved reference to an object. Either the object does not exist or the reference is ambiguous because it could refer to any of the following objects: [jobs_internal].[database_credentials].[C], [jobs_internal].[database_credentials].[name] or [jobs_internal].[targets].[C].
    Error SQL71501: Error validating element [jobs]: Schema: [jobs] has an unresolved reference to object [##MS_JobAccount##].
    Error SQL71501: Error validating element [jobs_internal]: Schema: [jobs_internal] has an unresolved reference to object [##MS_JobAccount##].

    1 vote
    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 →
  19. Recover SQL Server

    There is an option to recover deleted SQL databases. But when by accident you've deleted the server there is no chance to recover the server back up (if you don't configured a backup).
    Of course a warned man counts for two and you definitely need to configure backup. It would be nice if the same option as recover databases was available with recover sql servers.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Implement Azure SQL Server backup

    At present, MS is not offering any backup capabilities for backing up an Azure SQL Server(Logical container) and master database. Please include them in the offering as this will help customers to recover from accidental deletions/catastrophes. MS did mention that it can be restored from product group on best effort basis if its within 7 days however no guarantee was provided.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

SQL Database

Categories

Feedback and Knowledge Base