Поделиться через


Synapse implementation success methodology: Evaluate dedicated SQL pool design

Примечание.

Эта статья входит в серию статей, посвященных успешному проектированию внедрения Azure Synapse. Общие сведения о серии см. в статье "Внедрение Azure Synapse — успех благодаря продуманному дизайну".

You should evaluate your dedicated SQL pool design to identify issues and validate that it meets guidelines and requirements. Оценив проект до начала разработки решений, можно избежать блокирующих факторов и неожиданных изменений проекта. Так вы сможете соблюсти сроки проекта и остаться в рамках бюджета.

Synapse SQL has a scale-out architecture that distributes computational data processing across multiple nodes. Вычислительные ресурсы отделены от ресурсов хранилища. Это позволяет масштабировать вычислительные ресурсы независимо от данных в системе. For more information, see Dedicated SQL pool (formerly SQL DW) architecture in Azure Synapse Analytics.

Assessment analysis

During the assessment stage, you collected information about how the original system was deployed and details of the structures that were implemented. That information can now help you to identify gaps between what's implemented and what needs to be developed. For example, now's the time to consider the impact of designing round-robin tables instead of hash distributed tables, or the performance benefits of correctly using replicated tables.

Review the target architecture

To successfully deploy a dedicated SQL pool, it's important to adopt an architecture that's aligned with business requirements. For more information, see Data warehousing in Microsoft Azure.

Migration path

A migration project for Azure Synapse is similar to any other database migration. You should consider that there might be differences between the original system and Azure Synapse.

Ensure that you have a clear migration path established for:

  • Database objects, scripts, and queries
  • Data transfer (export from source and transit to the cloud)
  • Initial data load into Azure Synapse
  • Имена входа и пользователи
  • Data access control (row-level security)

For more information, see Migrate a data warehouse to a dedicated SQL pool in Azure Synapse Analytics.

Feature gaps

Determine whether the original system depends on features that aren't supported by Azure Synapse. Unsupported features in dedicated SQL pools include certain data types, like XML and spatial data types, and cursors.

Дополнительные сведения можно найти здесь

Dedicated SQL pool testing

As with any other project, you should conduct tests to ensure that your dedicated SQL pool delivers the required business needs. It's critical to test data quality, data integration, security, and performance.

Дальнейшие действия

В следующей статье в серии проектов Azure Synapse вы узнаете, как оценить проект пула Spark для выявления проблем и проверки соответствия рекомендациям и требованиям.