Skip to main content

SQLAzure and SqlServer2012 a Conspiracy of silence Part 2 (and today about T-SQL)

שלום לכולם
ובכן שנת 2012 נכנסת, שנת ה - SQL Server 2012, מתוכננים ערבי השקה בכל העולם והשיווק מאסיבי כתמיד.
אנשי הענן או אלו המשתמשים ב SQL Azure, יכולים כבר עכשיו להינות מיתרונותיו של SQL Server 2012, וב Production.  בפוסט הראשון הבאתי דוגמא קטנה של הפקודה TRHOW.
היום אביא כמה דוגמאות לפקודות שניתן להשתמש בהן:
1. IIF – זוהי פקודה חדשה שנכנסה ב 2012 ומטרתה להחזיר נתון במידה ומשפט מסוים יוצא אמת או לא יוצא אמת – הסינטקס שלו הוא
IIF([boolean expression], [true value], [false value])
ולכן אם המשפט הבא יורץ ב Azure הוא יחזיר תוצאה ולא שגיאה.
select    IIF(1=1, 'T','F')
2. שימוש בפונקציה EOMONTH – המחזירה את היום האחרון של החודש
image
3.  ואחרונה חביבה להיום פונקציה בשם CONCAT המבצעת חיבור בין סטירנג למספר ללא צורך בהמרה
SELECT 'SQL Server ' + CAST(2012 as varchar(10)), CONCAT( 'SQL Server ' ,2012)
זו פקודה שמבצעת את אותו הדבר….

אז הנה 3 דוגמאות קטנות על הקשר בין SQLServer 2012 לבין SQL Azure.
שתהיה לכולנו שנה מוצלחת

Comments

Popular posts from this blog

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...

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...

Azure SQL DB tiers comparison

Hi All In the last few month Brent Ozar gae us 2 masterpiece blogs related to Azure SQL DB:   How fast can a $21,468/mo Azure SQL DB load data?     In this blog Brent compared the abilities of Azure SQL DBs to load Data - he compared all combinations of vCors tiers. (When I asked him about comparing the Standard\Premium tiers, he told me to do it.... :-) )   There’s a bottleneck in Azure SQL DB storage throughput.   In this blog Brent showed us that in the vCors world the storage throughput has limit and there is not need to pay so much money when you need to upload lots of data.   So I took have taken up his challenge and done a comparison in Azure SQL DB in Standard\Premium tiers. I have created a new DB with 1 Table. I have generated 7 GB of DATA, and created the file in my local on premise drive (Yes, do not kill me, I did not had the time to put it on azure), and uploaded it via BCP command.   bcp "TableNam...