Monitor SQL database size increase
Hi I want to be able to monitor how the size of my database increases over time. I have created a SQL server VM and have wired up the Log Analytics and set it to capture the SQL performance counter called "SQLServer:Databases(*)\Data Files(s) Size (KB)". The data is being captured because when I run the following query I get results. Perf | where ObjectName =="SQLServer:Databases" and CounterName == "Data File(s) Size (KB)" and InstanceName == "Jason_DB" | project TimeGenerated, CounterName, CounterValue I have been running a SQL Job over night on the database to insert two rows into a table every 5 min but I'm only seeing the database size of "8,192"! The chart is linear and show no "Data file" size increase! Is there something wrong with my query or do I not understand the SQL performance counter in collecting? Current query Perf | where ObjectName =="SQLServer:Databases" and CounterName == "Data File(s) Size (KB)" and InstanceName == "Jason_DB" | project TimeGenerated, CounterName, CounterValue | summarize avg(CounterValue) by CounterName, bin(TimeGenerated, 5m) | render timechart Rendered chartHelp with log analytics query to check SQL database availability
I need a log analytics query that will tell me whether a particular SQL database is available or not. In some instances, database was down. We would like to create an alert using a query in case database is not available. Can anyone help with this?Azure Synapse dedicated SQL pool vs. Azure SQL vs SQL
Hello, currently we operate on-premises PostgreSQL DB that we use as our data warehouse. I would like to set up a data warehouse in Azure, but the Azure portal is bit confusing, as there are multiple options: 1) in Azure Synapse, there is dedicated SQL pool (formerly labeled as Azure Data Warehouse) Then, outside Azure Synapse there are two additional options: 2) Azure SQL database ( /BrowseResource/resourceType/Microsoft.Sql%2Fazuresql ) and 3) "SQL database" (/BrowseResource/resourceType/Microsoft.Sql%2Fservers%2Fdatabases) https://docs.microsoft.com/en-us/azure/architecture/data-guide/relational-data/data-warehousing describes that Azure SQL (#2 above) uses symmetric multiprocessing (SMP) while "Azure Synapse Analytics" (#1) above uses massively parallel processing (MPP). My data needs are not so vast to utilize the MPP. Thus it seems I should be considering #2, i.e. outside the Synapse Analytics. Azure SQL (#2) above further branches into "Single Database", "Elastic pool" and "Single instance managed DB". I am guessing that for my scenario, "Azure SQL - Single Database" is the best option. If I choose this, will I be able to use this storage in Azure Synapse Analytics? Furthermore, to use Azure Data Factory (ADF) - if I set up "Azure SQL - Single Database", should I be aiming to use Data Factory within Azure Synapse Analytics, or outside it (i.e. use ADF in Azure portal)?Build Mapping Data Flows using Managed Identity (formerly MSI) for Azure SQL DB and Azure Synapse
Hi All, I thought you might like to read my new article: Build Mapping Data Flows using Managed Identity (formerly MSI) for Azure SQL Database and Azure Synapse Analytics (formerly SQL DW) https://www.linkedin.com/pulse/build-mapping-data-flows-using-managed-identity-formerly-angane Mark Kromer Based on your Tech Community blog I have created this article. Happy Learning!Tweet Sentiment Analytics made easy by Azure Services
I have written an article that explains how you can perform Tweet Sentiment Analytics using services from the Azure cloud. You can find the article on https://www.linkedin.com/pulse/tweet-sentiment-analytics-made-easy-azure-services-narendra-anganeAccelerated and Flexible Restore Points with SQL Data Warehouse
We are thrilled to announce that SQL Data Warehouse (SQL DW) has released accelerated and flexible restore points for fast data recovery. SQL DW is a fully managed and secure analytics platform for the enterprise, optimized for running complex queries fast across petabytes of data. The ability to quickly restore a data warehouse offers customers data protection from accidental corruption, deletion, and disaster recovery. We have seen scenarios where compliance requirements and having multiple test and development environments of a data warehouse enforce stricter capabilities in this area as well. To continue delivering first-class data protection and recovery, we have released the following critical improvements which are seamlessly integrated within the Azure Portal. Read about it in the Azure blog.Latest updates to Azure Database for MySQL
Earlier this year, in March, we announced the general availability (GA) of Azure Database for MySQL, offering the community version of MySQL together with built-in high availability, a 99.99 percent availability SLA, elastic scaling for performance, and industry leading security and compliance in Azure. Since GA, the team has been at work delivering a variety of new features and additional functionality to enhance and extend the value of this service. We are pleased to share with you some details about the new additions to this service based on customer feedback. Read about it in the Azure blog.Latest updates to Azure Database for PostgreSQL
Earlier this year, in March, we announced the general availability (GA) of Azure Database for PostgreSQL, offering the community version of MySQL together with built-in high availability, a 99.99 percent availability SLA, elastic scaling for performance, and industry-leading security and compliance in Azure. Since GA, the team has been at work delivering a variety of new features and additional functionality to enhance and extend the value of this service. I am pleased to share with you some details new additions to this service based on customer feedback. Read about it in the Azure blog.
