How to find who created a SQL Server in Azure Portal? - sql-server

How to find who created a SQL Server in Azure Portal? I need to know the createdUserId of that particular SQL Server.

You can get the information from the Activity Logs which has information about the created user and so on.

Related

Google Cloud SQL - SQL Server Users

I am currently working on a project to help configure an application in GCP, been working mostly in Azure and I am a bit confused with users and rights in Cloud SQL for SQL Server. It seems that SA is not permitted and I can understand that but in their documentation it states:
You can create other SQL Server users or roles. All Users you create using Cloud SQL are granted the same database permissions as the sqlserver login. if you use a different method the user wont have the same permissions as the customer admin accounts.
My questions.
Create with cloud sql means i have to use the console to create those users and not thru TSQL inside say SQL Server Management Studio that connects to SQL Server?
If i create a login will I then be able to add that login as a user to the database?
thank you.

Audit who deployed SQL database to Azure

Through SSMS, connecting to my on prem server, you can right click a database, select tasks and "DEPLOY DATABASE TO MICROSOFT AZURE SQL DATABASE". Is there a way to log/audit who did this from my on prem server?
After doing this, I've checked the SQL Server logs and do not see any entries for this.
Thanks!
You should be able to investigate the logs using power-BI content pack refer below link.
https://powerbi.microsoft.com/fr-be/blog/monitor-azure-audit-logs-with-power-bi/
You can also use Azure Activity Log API to check the resource changes refer API link below for details - https://learn.microsoft.com/en-us/rest/api/monitor/activity-logs/list?tabs=HTTP

Remote connection Azure SQL Server not showing All databases

When I connect my Azure SQL Server using Azure portal then it shows me all databases (shown in the screenshot1)
But when I connect to the same server using SSMS inside Azure VM then it shows only one database (shown in the screenshot2)
Please someone help me in this issue
I think you'd better check the Options settings, did you specify the db name. If so, you will only can see specified db, not all.

How to get SQL Database Status in Azure with Log Analytics

I would like to show whether an Azure SQL database is online or not in an Azure Workbook.
Is this information available to resource metric/log analytics workspace so that I can show it in an Azure Workbook.
Could you provide me a hint?
There isn't a feature or function to check the Azure SQL database Status.
Once the Azure SQL database created, it will be alive or online all the time. Unless you manually delete or pause it(Elastic pool).
HTH.

Error Migrating SQL Server Database to Azure

So I am completely new to .Net Core development, and was given a codebase that I am trying to host on Microsoft Azure. I have the local database file (.mdf) in SQL Server Management Studio, and am trying to deploy it to an Azure Database, However it keeps failing during migration and giving me this issue
Error SQL71627: The element User: [ISOCENTRIC\Administrator] has property >AuthenticationType set to a value that is not supported in Microsoft Azure SQL >Database v12.
(Microsoft.SqlServer.Dac)
However, when I SELECT * FROM master.sys.database_principals; and it dumps the db users list, the "ISOCENTRIC\Administrator" user does not appear in that list, so I cannot find a way to drop it from the DB. Is there something I am missing regarding the location of this user and how I can drop it from the db so I can migrate to Azure?
p.s. This is my first post on here so please let me know if I should make any changes to adhere to correct formatting on this forum.
Thanks in advance.
I guess the database users can't be migrated to Azure SQL DB because they are Windows users. You'll need to drop those users before you deploy this database to Azure SQL DB.
You can always backup and restore a copy of this database, remove the users, and then deploy that one to Azure SQL Db.
I figured out that my query to dump the database users was incorrect, and was able to find and drop the user causing the issue.

Resources