Synapse implementation success methodology: Evaluate dedicated SQL pool design

Poznámka:

Tento článek je součástí série článků Úspěch implementace Azure Synapse díky designu. Přehled série najdete v tématu Úspěšné implementace Azure Synapse podle návrhu.

You should evaluate your dedicated SQL pool design to identify issues and validate that it meets guidelines and requirements. Vyhodnocením návrhu před zahájením vývoje řešení se můžete vyhnout blokování a neočekávaným změnám návrhu. Tímto způsobem chráníte časovou osu a rozpočet projektu.

Synapse SQL has a scale-out architecture that distributes computational data processing across multiple nodes. Výpočetní funkce jsou oddělené od úložiště, což umožňuje jejich škálování nezávisle na datech v systému. 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
• Přihlášení a uživatelé
• 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.

Další informace najdete tady:

• Table data types for dedicated SQL pool (formerly SQL DW) in Azure Synapse Analytics
• Transact-SQL features supported in Azure Synapse SQL

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.

Další kroky

V dalším článku o úspěchu Azure Synapse podle řady návrhů se dozvíte, jak vyhodnotit návrh fondu Sparku, abyste identifikovali problémy a ověřili, že splňuje pokyny a požadavky.