Frequently Asked Questions

Migration time depends on data volume, complexity, and network speed. A simple schema with 10GB of data can migrate in hours. Large enterprise databases with 10TB+ may take days to weeks. Our schema analyzer provides time estimates based on your specific database.

Yes, using incremental sync. First, perform initial bulk load while your source database runs normally. Then use change data capture (CDC) or timestamp-based sync to keep Snowflake updated. Finally, switch over during a brief maintenance window (often under 5 minutes).

LegacyToCloud supports migrations from MySQL, MariaDB, PostgreSQL, Amazon Aurora, and Microsoft SQL Server to Snowflake. Each source has specific type mappings and considerations we handle automatically.

Snowflake uses standard SQL, so most analytical queries work with minimal changes. However, if your application uses database-specific features (stored procedures, triggers), those may need rewriting. Our analysis report identifies these areas.

Snowflake doesn't have an ENUM type. We convert ENUMs to VARCHAR and document the allowed values. You can enforce constraints using Snowflake CHECK constraints or create a lookup table for validation.

Snowflake supports stored procedures in JavaScript, Python, Java, and Snowflake Scripting (SQL). MySQL/PostgreSQL procedures need to be rewritten. Our analysis identifies all procedures and provides migration guidance.

Snowflake automatically optimizes query performance through micro-partitioning and doesn't require traditional indexes. Primary keys are metadata-only (not enforced). We recommend clustering keys for large tables based on common query patterns.

MySQL JSON columns map to Snowflake VARIANT type, which natively supports semi-structured data. You can query JSON fields directly using dot notation or bracket syntax. VARIANT can hold up to 16MB of data.

Snowflake supports foreign key syntax but doesn't enforce referential integrity. This is common in data warehouses for performance. The constraints serve as documentation and can be used by BI tools.

Snowflake uses consumption-based pricing. You pay separately for storage (~$23/TB/month) and compute (credits based on warehouse size). A small warehouse costs ~$2/hour when running. You can pause warehouses when not in use.

Schema analysis is free. Migration planning starts at $199 for small databases. Enterprise migrations with hands-on support range from $3,000 to $50,000+ depending on complexity. Contact us for a custom quote.

Often costs go down because you eliminate server maintenance, licensing, and over-provisioned hardware. Snowflake's separation of storage and compute means you only pay for what you use. We provide cost estimates before migration.

Yes. We use encrypted connections (TLS) for all database access. Data in transit is encrypted. We never store your actual data - only schema metadata for analysis. For bulk loads, data goes directly from your source to your Snowflake account.

No. You can upload a schema file (mysqldump --no-data) for analysis without providing credentials. For live analysis, we recommend connecting to a read replica or using a read-only database user.

Yes, Snowflake is SOC 2 Type II, HIPAA, PCI-DSS, and FedRAMP compliant. It offers features like column-level encryption, data masking, and row-level access policies for sensitive data.