I am connecting to on premises SQL Server and an Azure SQL database that is in a pool. Both from same SSMS instance.
When I right click on a stored procedure in any database on the on-premise server, I see the properties option and can add/modify permissions. But the Azure SQL connection does not show the properties option for stored procedures so I must GRANT in T-SQL.
There is a lot of info in the properties general as well as permission I'd like to have the SSMS access to see easily. Is there a setting in Azure SQL that enables / disables properties?
Thanks for any help!
Azure SQL database doesn't support the all the properties settings in SSMS.
For example, SSMS supports Azure SQL database properties settings:
But as you found that it doesn't support Stored Procedure properties setting.
Is there a setting in Azure SQL that enables / disables properties?
No, there isn't such settings in Portal or SSMS. No matter which account(admin or db_owner) you login to the Azure SQL database.
The only way is you grant it in T_SQL.
Hope this helps.
This isn't an Azure SQL Database issue, but a database permissions issue.
Are you connecting in the same way - i.e. both using a SQL login?
You will need to ensure that you grant the same permissions for the user on both databases, one way might be to script out the permissions from the on-premises database and run the query on the Azure one. You should still ensure that you do this at the lowest level possible so that you don't grant excessive permissions. I suggest at the schema level
The permission that you need at the minimum level is:
GRANT VIEW DEFINITION ON SCHEMA::<my schema name> TO <my user>
Related
Just want to know that I have my ASP.NET MVC application and related SQL Server database. I have signed up for a free Azure account.
I want to know if I can publish my app and database to Azure with this free account. The purpose of that, I want to check how the things are working properly and also since I working from home, selected user's want to see the progress of my project.
you need to have paid subscription for SQL server feature. Try finding SQL server express also know that SQL server will separately require you to pay SQL server license key. I would suggest to look into free SQL server hosting accounts instead of directly using Azure SQL server.
I'd like to move the database for several Delphi applications from on-premise SQL Server to Azure Managed Instance. It would use Azure Active Directory Integrated authentication.
We use TADOConnections. I'm having trouble setting the connection string. It looks like TADOConnection does not support Azure Managed Instance and Azure Active Directory Integrated authentication. Is that correct?
Version 18.3 and latter of the Microsoft OLE DB Driver for SQL Server includes the required Microsoft Active Directory Authentication Library (ADAL.dll). Since this traffic is going across the internet keeping this up to date would be a good practice.
Then using the connection string shown for the database on Azure as a starting point you can add Provider=MSOLEDBSQL.1 (plus a ; separator if needed) in the ADO connection string so the above driver is used.
Synapse Analytics serverless SQL pool endpoint can have multiple databases. Serverless SQL pool has no local storage; only metadata objects are stored in databases.
Question:
Can I backup these databases manually? I don't see anything in the portal, maybe through Powershell or Azure-CLI?
Is there any automated backup or restore point taken?
Is my only option to keep all the metadata in source control (which I should keep anyway) and deploy from there in case of a disaster?
Currently, it is not possible to backup Serverless SQL Pool databases. Please, file feature proposal on Azure Feedback.
Also, check this blog, where you can see how you can use PowerShell DbaTools to script Synapse SQL objects which may help you.
I am working on a project to replicate an application that currently runs on premises to an Azure SQL Database. For the foreseeable future, the application will have to run both on site and on Azure. The project is stored in TFS, and multiple filegroups are specified. Development is ongoing. Is there a way I can maintain this as one project in source control, given that Azure SQL databases only have a primary filegroup? I feel like I can't be the first person in this situation, but I haven't found a decent solution yet.
I'm fine with the Azure database only running on primary, but that is not an option for the local database. This is not for a single deployment, I would like to continue to deploy changes both locally and to Azure from source control. I may be asking for too much here, I just really really want to avoid dual maintenance, when there are a number of teams involved.
Thank you!
You have two options:
Add manual SQL Statements to setup Filegroups on your on-premises SQL Server that don't run against SQL Azure
Use a new feature of Azure named SQL Managed Instances. This is fully managed SQL Server instance running in Azure that supports all features of SQL Server such as filegroups. Don't go installing your own SQL Server on IaaS. That's not necessary anymore with this new feature.
There is no way to use multiple filegroups in Azure SQL Database. If you want to move your database to the cloud and keep the ability to use multiple filegroups, please consider setting an Azure VM with SQL Server on it. Another option would be to change your application so that it does not use SQL filegroups.
As for the replication, please consider SQL Server replication or Azure Data Sync. Azure Data Sync requires an Azure SQL database. It is slower than SQL Server replication but it can handle conflicts.
I am trying to connect to database from Integration Service project from Microsoft visual studio. How do I create a database from SQL SERVER 2012.
SQL Server Management Studio (SSMS) will allow you to create a database and tables through its graphical user interface. However, I'm guessing what you're looking for is actually an SSIS Connection Manager to an existing database. Look at the connection managers in SSIS, create a new one, and fill in the boxes. What you're doing is building a database connection string. You will need credentials (username and password, or a Windows authenticated user) to connect to the database. Also, you may need to spend some time reading the documentation.