Skip to main content

Back to Basic - create new Azure SQL DB

Hi All


Long time no posts, i have been busy in last few months on a hard day 2 day work and did not 

had the chance to publish some posts.

So i have decided to sit and write some "Back to Basic" posts.


Today i will write about how to create an Azure SQL Db from the portal.



  1. Choose the Subscription.

  2. RG - if its in special Project connect to its RG (Resource group is a virtual collection of resources in order to easy manage budgets.)

  3. DB Name

  4. Server - choose the correct or create one(Server has limited manage capabilities on the DB like security, backup policies and other rules)

  5. Choose no (elastic pool is a feature that will not be explained here)

  6. This is the server tier, means the power of the DB and by pass the payments of the DB (i will have special post on the new tiers options, for this post i will leave the default)

  7. This is the Storage redundancy, for now leave it in the default option.


now we will move to the Networking tab:


8 - 9. Configuration of networking and security is depend on each organization policy, for example if you need private endpoint then you can not configure the whitelist FW rules. But if you want DB with out any security restrictions you can just add your IP and that is all.



Nothing to do here


10 - use what you need

11 - Change to what you prefer




Tags are for better managing.


12 - if all is good you can create the DB, if you gets error you need to go to the relevant error - here its in the basic tab, and to understand the error.


13 - you can create a template for it, and recreate DB from template.


That is all for today



Labels:

Comments

Post a Comment

Popular posts from this blog

Extended Events in SQL Azure

Hi Everybody   Today an English post about 'Extended Events in SQL Azure', some of you shorten the name to 'EE' and some to 'XEvent'. I Love EE so this is how I will call it in this post.   This feature was introduce in SQL Server 2008 and its should help collecting DATA about what is running in the Server.   More Details about this SQL Server feature can be found in this Link: https://msdn.microsoft.com/library/bb630282.aspx?f=255&MSPPError=-2147217396   There are a few differences between EE in SQL Azure and regular SQL Server: In SQL Server versions the EE are on the Server level and therefore you create sessions on Server. In SQL Azure the server is a virtual entity - so the EE is in DB level and you create the session on DataBase. In SQL Server versions the EE can write to files on the server. SQL Azure does not have drives for files (SQL Azure is PAAS.....:-)). There is an option to write to blob storage, for this we need t...
Post a Comment
Read more

How to restore deleted Azure Synapse dedicated SQL pool

  Existing dedicated pool can be easily restored from Azure portal or PowerShell command, but for now deleted pool could be restored from PowerShell only! Example: # Connect to Azure with system-assigned managed identity $AzureContext = (Connect-AzAccount -Identity).context # set and store context $AzureContext = Set-AzContext -SubscriptionName $AzureContext.Subscription -DefaultProfile $AzureContext # $AzureContext = Set-AzContext -SubscriptionName $SubscriptionName -DefaultProfile $AzureContext $SubscriptionName="Databases" $ResourceGroupName="stg-rg-we" $ServerName="stg-synapse-we"   $DatabaseName="sql_we_2023_11_07_13_42" $NewDatabaseName="sql_dp_we_deleted" ######################################## $token = (Get-AzAccessToken -ResourceUrl https://database.windows.net).Token $SubscriptionId = "ce088f9e-1111111a3914b" $DedicatedPoolEndPoint = "stg-synapse-we.sql.azuresynapse.net" $DedicatedPoolName = $DatabaseNam...
Post a Comment
Read more

The journey to the Lakehouse

A long time has passed since the last post, we have gone through a long and tedious journey to adapt what Azure offers us, to our needs. Our needs were simple, the Current Datawarehouse (SQL Server on VM inazure) served the BI. ML teams worked on GCP, we want to let both teams to work on Azure in a platform that will have the ability to scale and will not fail every 2 days. We checked: Snowflake on azure Synapse analytics GCP We decided to go for the full Azure product for the reasons: Migration time support costs Synapse as a platform contains many components, and the challenge was to find what fits  us as an organization and as a group. The knowledge of the people and their abilities influenced the plans. Here's what we planned and what we did: We start to put everything in the Data Lake in parquet or delta format, build on top of Azure ADLS gen 2. We had to move some data to T-SQL compatible platform, so this involves setting up a dedicated Synapse pool , which is a fully man...
Post a Comment
Read more