Azure – Presplay Cloud Tech* https://posts.presplay.cloud Trends and Inventions in technology Mon, 03 Jan 2022 15:46:48 +0000 en-US hourly 1 https://wordpress.org/?v=6.8.5 https://posts.presplay.cloud/wp-content/uploads/2018/02/cropped-presplay-2-32x32.png Azure – Presplay Cloud Tech* https://posts.presplay.cloud 32 32 Monitor metrics on Azure Database for PostgreSQL – Flexible Server https://posts.presplay.cloud/monitor-metrics-on-azure-database-for-postgresql-flexible-server/ https://posts.presplay.cloud/monitor-metrics-on-azure-database-for-postgresql-flexible-server/#respond Sat, 22 May 2021 13:25:38 +0000 https://presplay.cloud/?p=22474
Conceptos básicos de bases de datos. - Uneweb Instituto
Monitoring data about your servers helps you troubleshoot and optimize for your workload. Azure Database for PostgreSQL provides various monitoring options to provide insight into the behavior of your server.

Metrics

Azure Database for PostgreSQL provides various metrics that give insight into the behavior of the resources supporting the PostgreSQL server. Each metric is emitted at a one-minute frequency, and has up to 93 days of history. You can configure alerts on the metrics. Other options include setting up automated actions, performing advanced analytics, and archiving history. For more information, see the Azure Metrics Overview.

List of metrics

The following metrics are available for PostgreSQL flexible server:

Metric Metric Display Name Unit Description
active_connections Active Connections Count The number of connections to your server.
backup_storage_used Backup Storage Used Bytes Amount of backup storage used. This metric represents the sum of storage consumed by all the full database backups, differential backups, and log backups retained based on the backup retention period set for the server. The frequency of the backups is service managed. For geo-redundant storage, backup storage usage is twice that of the locally redundant storage.
connections_failed Failed Connections Count Failed connections.
connections_succeeded Succeeded Connections Count Succeeded connections.
cpu_credits_consumed CPU Credits Consumed Count Number of credits used by the flexible server. Applicable to Burstable tier.
cpu_credits_remaining CPU Credits Remaining Count Number of credits available to burst. Applicable to Burstable tier.
cpu_percent CPU percent Percent Percentage of CPU in use.
disk_queue_depth Disk Queue Depth Count Number of outstanding I/O operations to the data disk.
iops IOPS Count Number of I/O operations to disk per second.
maximum_used_transactionIDs Maximum Used Transaction IDs Count Maximum transaction ID in use.
memory_percent Memory percent Percent Percentage of memory in use.
network_bytes_egress Network Out Bytes Amount of outgoing network traffic.
network_bytes_ingress Network In Bytes Amount of incoming network traffic.
read_iops Read IOPS Count Number of data disk I/O read operations per second.
read_throughput Read Throughput Bytes Bytes read per second from disk.
storage_free Storage Free Bytes The amount of storage space available.
storage_percent Storage percent Percentage Percent of storage space used. The storage used by the service may include the database files, transaction logs, and the server logs.
storage_used Storage Used Bytes Percent of storage space used. The storage used by the service may include the database files, transaction logs, and the server logs.
txlogs_storage_used Transaction Log Storage Used Bytes Amount of storage space used by the transaction logs.
write_throughput Write Throughput Bytes Bytes written per second to disk.
write_iops Write IOPS Count Number of data disk I/O write operations per second.

Server logs

Azure Database for PostgreSQL allows you to configure and access Postgres’ standard logs. To learn more about logs, visit the logging concepts doc.

 

Recommended content

  • Backup and restore in Azure Database for PostgreSQL – Flexible Server

    Learn about the concepts of backup and restore with Azure Database for PostgreSQL – Flexible Server

  • Logical decoding – Azure Database for PostgreSQL – Single Server

    Describes logical decoding and wal2json for change data capture in Azure Database for PostgreSQL – Single Server

  • Monitor and tune – Azure Database for PostgreSQL – Single Server

    This article describes monitoring and tuning features in Azure Database for PostgreSQL – Single Server.

  • Logical replication and logical decoding – Azure Database for PostgreSQL – Flexible Server

    Learn about using logical replication and logical decoding in Azure Database for PostgreSQL – Flexible Server

]]> https://posts.presplay.cloud/monitor-metrics-on-azure-database-for-postgresql-flexible-server/feed/ 0 Performance Recommendations in Azure Database for PostgreSQL – Single Server https://posts.presplay.cloud/performance-recommendations-in-azure-database-for-postgresql-single-server/ https://posts.presplay.cloud/performance-recommendations-in-azure-database-for-postgresql-single-server/#respond Sat, 22 May 2021 13:19:42 +0000 https://presplay.cloud/?p=22471
Applies to: Azure Database for PostgreSQL – Single Server versions 9.6, 10, 11

A simple guide to use PostgreSQL - DEV Community

The Performance Recommendations feature analyses your databases to create customized suggestions for improved performance. To produce the recommendations, the analysis looks at various database characteristics including schema. Enable Query Store on your server to fully utilize the Performance Recommendations feature. After implementing any performance recommendation, you should test performance to evaluate the impact of those changes.

Permissions

Owner or Contributor permissions required to run analysis using the Performance Recommendations feature.

Performance recommendations

The Performance Recommendations feature analyzes workloads across your server to identify indexes with the potential to improve performance.

Open Performance Recommendations from the Intelligent Performance section of the menu bar on the Azure portal page for your PostgreSQL server.

Performance Recommendations landing page

Select Analyze and choose a database, which will begin the analysis. Depending on your workload, th analysis may take several minutes to complete. Once the analysis is done, there will be a notification in the portal. Analysis performs a deep examination of your database. We recommend you perform analysis during off-peak periods.

The Recommendations window will show a list of recommendations if any were found.

Performance Recommendations new page

Recommendations are not automatically applied. To apply the recommendation, copy the query text and run it from your client of choice. Remember to test and monitor to evaluate the recommendation.

Recommendation types

Currently, two types of recommendations are supported: Create Index and Drop Index.

Create Index recommendations

Create Index recommendations suggest new indexes to speed up the most frequently run or time-consuming queries in the workload. This recommendation type requires Query Store to be enabled. Query Store collects query information and provides the detailed query runtime and frequency statistics that the analysis uses to make the recommendation.

Drop Index recommendations

Besides detecting missing indexes, Azure Database for PostgreSQL analyzes the performance of existing indexes. If an index is either rarely used or redundant, the analyzer recommends dropping it.

Considerations

  • Performance Recommendations is not available for read replicas.

Next steps

Recommended content

  • Logical replication and logical decoding – Azure Database for PostgreSQL – Flexible Server

    Learn about using logical replication and logical decoding in Azure Database for PostgreSQL – Flexible Server

  • Limits – Azure Database for PostgreSQL – Flexible Server

    This article describes limits in Azure Database for PostgreSQL – Flexible Server, such as number of connection and storage engine options.

  • Planned maintenance notification – Azure Database for PostgreSQL – Single Server

    This article describes the Planned maintenance notification feature in Azure Database for PostgreSQL – Single Server

    Logical decoding – Azure Database for PostgreSQL – Single Server

    Describes logical decoding and wal2json for change data capture in Azure Database for PostgreSQL – Single Server

    Backup and restore in Azure Database for PostgreSQL – Flexible Server

    Learn about the concepts of backup and restore with Azure Database for PostgreSQL – Flexible Server

    Overview of business continuity with Azure Database for PostgreSQL – Flexible Server

    Learn about the concepts of business continuity with Azure Database for PostgreSQL – Flexible Server

    Query Performance Insight – Azure Database for PostgreSQL – Single Server

    This article describes the Query Performance Insight feature in Azure Database for PostgreSQL – Single Server.

]]> https://posts.presplay.cloud/performance-recommendations-in-azure-database-for-postgresql-single-server/feed/ 0 Five Ways To Migrate Your On-Premises SQL Database To Azure https://posts.presplay.cloud/five-ways-to-migrate-your-on-premises-sql-database-to-azure/ https://posts.presplay.cloud/five-ways-to-migrate-your-on-premises-sql-database-to-azure/#respond Tue, 20 Feb 2018 04:49:46 +0000 https://presplay.cloud/?p=9000 There are currently three deployment options for SQL Server Database on the cloud. Well, four, if you count Azure SQL Databases in elastic pool. But Azure SQL DB in elastic pool is essentially just Azure SQL Databases grouped into an elastic pool so you can maximize what you’re paying for and share the resources.

Anyway, I digress. Right now, you can either put your SQL Server database in a SQL Server in an Azure VM, in a Managed Instance, or in an Azure SQL Database. Now, there are different considerations for choosing one over the other, but that’s a whole different blog post. In this post, we are going to focus on how you can move your on-premises SQL Server database to Azure.  Here’s a neat table comparing the possible ways for the three:

SQL Server in Azure VM Managed Instance Azure SQL Database (Singleton/Elastic Pool)
Backup & Restore Yes Yes No
Dettach/Attach Yes No No
Mirroring/Availability Groups Yes No No
Log Shipping Yes No No
Replication Yes Yes Yes
DMA/DMS Yes Yes Yes
Bulk Load Yes Yes Yes

Most every strategy you have for migrating SQL Server on-premises will work for SQL Server in Azure VM. This is the most common way of migrating to the cloud. It is easy since it is essentially just moving your old server to a new server.  Managed Instance also allows you to restore Native SQL Server backups from on-premises SQL Server, so it is fairly compatible and moving is more or less smooth. The challenge comes when moving your existing SQL Server Databases to Azure SQL Database. Due to security reasons and infrastructure differences you cannot restore a SQL Server backup to Azure. So this often leaves a lot of people scratching their heads about how to move their existing databases to Azure SQL Database. Here are five ways to migrate your on-premises SQL Database to Azure:

  1. Data Migration Assistant/ Data Migration Service 

    This is the service/tool that Azure specifically created for this task.  The tool can also perform assessments to identify feature parity and database compatibility issues when moving your SQL Server to any of the available deployment options for SQL Server from on-premises SQL Server to Azure SQL Database. It will present you with a report identifying all those, as well as possible fixes for the different Database Compatibility level available for your chosen target. For the migration, DMA/DMS has offline and online options. Offline allows you to either migrate just the schema or the schema and data in one shot. You would likely use this method for testing/POC, for small databases, or those applications that can afford longer downtime while you move the data. The online option allows you to keep the on-premises database and the Azure SQL Database continuously synchronizing after you have moved the initial schema/data. This way you have ample time for the Azure SQL Database to get caught up and then decide when to cut-over and start pointing your application to the Azure SQL Database.  Microsoft’s Doc has a detailed step by step on how to do both offline and online migration to Azure SQL Database.

  2. Replication

    You can add an Azure SQL Database as a subscriber to a transactional replication. This can let you migrate the data and objects from your on-premises SQL  Server to Azure SQL Database. Since you cannot restore backups, you can only initiate this replication from a snapshot. Similar to online migration for DMS, you can start your synching well before your scheduled migration and when everything is synchronized, decide when you can cut-over and re-point your applications to the azure sql database. One thing to note, you can only replicate tables with a primary key. So if you have a number of tables without them, you’ll need to get creative or pair it with other techniques to move those tables.

  3. DACPAC

    Dacpac is a single file containing the definitions for your database schema –  tables, view, stored procedures,  functions, and other database objects. Sort of like a schema, only backup. You can create and restore one to Azure SQL Database using SSDT, SSMS or SQLpackage.exe. Since this only migrates your schema, you’ll need to pair it with other techniques to bring your data to Azure SQL DB. You’d likely use this for POC/test or for new applications that do not require any data to migrate. You can create a dacpac file and deploy one using SSDT, sqlpackage.exe or SSMS.

  4. BACPAC

    BACPAC is similar to DACPAC but encapsulates both schema and data.  So you can bring your entire database to Azure SQL Database. This single file stores the information in json format. This strategy is applicable to small databases. You can create a BACPAC file and import one using SSDT, sqlpackage.exe or SSMS.

  5. Generate SQL Scripts

    Sql Server Management Studio has a Generate SQL Script UI. You can right click a database-> Tasks -> Generate SQL Scripts. If you’ve been working with SQL Server, you’ve probably used this before. What you may not have noticed before is when you click on Advanced, you can actually control what the script provides you. Specifically, you can change the Engined Type from Stand-Alone or Azure SQL Database. So the script provided is compatible with it. You can also actually specify on type of data to script whether to output Schema Only or Schema and Data.  So for what it’s worth, it is your TSQL version of DACPAC or BACPAC. The advantage of this is you can add/modify the resulting TSQL script as you need to. Similar to BACPAC, if you are scripting the data, it is applicable for small databases but not bigger databases. If you review the resulting script, it is actually writing your data as individual insert commands per row.

Azure provides a very helpful tool for planning your migration, the Azure Database Migration Guide. You can change the source and destination and it will provide you with a guide for the pre-migration, migration, and post-migration tasks that you need to be aware of as well as links to the resources and tools for each step. If you are planning a migration, be sure to check the page beforehand to assist you in your planning.

]]> https://posts.presplay.cloud/five-ways-to-migrate-your-on-premises-sql-database-to-azure/feed/ 0