SQL Azure for DBAs and Data Engineers

Hi All   Since this is become more and more important for SQL Azure DB I am writing about 'Security Features in SQL Azure DB'.   I will put everything in a list and links for all features. 1)    Azure SQL Database security guidelines and limitations:   a) Link: https://azure.microsoft.com/en-us/documentation/articles/sql-database-security-guidelines/ .   b) This link explain about: Firewall, Connection encryption and certificate validation, and some best Practices. 2)    Connecting to SQL Database: Best Practices and Design Guidelines:   a) Link: https://azure.microsoft.com/en-us/documentation/articles/sql-database-connect-central-recommendations/   b) This link bring few other links of the FW issue and connection Ports. 3)    Connecting to SQL Database By Using Azure Active Directory Authentication   a) Link: https://azure.microsoft.com/en-us/documentation/articles/sql-database-aad-authentication/   b) You have in this link few other links of the options

Hi All   New feature was released lately - Fail Over in the Geo Replication in SQL Azure. The Announcement is here:   https://azure.microsoft.com/en-us/blog/spotlight-on-new-capabilities-of-azure-sql-database-geo-replication/   As You can see they added Failover feature. That means that until today you have Primary and Secondary DB's, DATA moved on one direction and you could disconnect the connection when ever you wish. but then you have to build everything from the beginning, (you can look in my old post about geo-replications types in sql azure). Now DATA moved backward, when you click Fail over - you still have 2 DB's but the Secondary become Primary and vise versa. I this this is a great feature. you can also read in Hebrew about it in Geri's Reshef Blog   http://blogs.microsoft.co.il/gerireshef/2015/11/23/%D7%90%D7%95%D7%A4%D7%A6%D7%99%D7%99%D7%AA-geo-replication-%D7%91-azure/   This is the new link   enjoy    

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 to gra

Hi All   Today I want to explain how to find and troubleshoot Deadlocks in SQL Azure V12.    At V2 we had this query to run and find our deadlocks:   SELECT * FROM sys . event_log WHERE event_type = 'deadlock'   This query return XML, and we could have change it to XDL and see the deadlock Chart.   You can see this in the 2 links by Thomas Larock ( @ SQLRockstar ):     http://thomaslarock.com/2013/05/how-to-troubleshoot-deadlocks-in-windows-azure-sql-database-wasd/ & https://www.youtube.com/watch?v=RlKCe05WDOw   Now in V12 this feature is not supported - so how do you get the deadlock data?   MSFT Gave us this query (Running on Master DB):     SELECT top 100 *, CAST ( event_data as XML ). value ( '(/event/@timestamp)[1]' , 'datetime2' ) AS timestamp , CAST ( event_data as XML ). value ( '(/event/data[@name="error"]/value)[1]' ,

שלום לכולם והיום על versions. קיימים שלושה מספרים המייצגים את version של ה sql שלך: Select @@version -->  Microsoft SQL Azure (RTM) - 12.0.2000.8   Sep  2 2015 20:51:51   Copyright (c) Microsoft Corporation  select  DATABASEPROPERTYEX(db_name(), 'Version')  --> number like 826 or any other The Performance tier שלושה מספרים אלו מייצגים את מספר גרסת ה sql ברמת בסיס נתונים כאשר ייתכן שתהיה אותה ורסיה אולם מספר שונה - ואפילו באותו שרת ייתכנו שינויים בין בסיס נתונים. למה זה חשוב? לא באמת זה חשוב ולא באמת זה מועיל - אבל יש פה כמה היבטים - ראשית אפשר ללמוד הרבה מהגלגולים ופריסת הגרסאות הרבה ויחד עם זאת אפס אחוז  downtime. שנית כאשר ישנה תקלה יותר נוח למסור ישר את 3 המספרים אלו ואז הטיפול יהיה ממש מהיר - הם יוכלו לזהות במהירות מצי נפרסה הגרסה וכך לזהות בעיות שיכלו להתרחש. ועכשיו ארחיב לגבי הנקודה השלישית. אם תיראו בפוסט הקודם הזכרתי את 3 הגרסאות שקיימות היום ב SQL Azure. web\ business V2 - basic\ standard S1\ Standard S2\ Premium P1\ Premium P2\ Pr