数据库迁移工具实战:KDMS自动化转换与效率量化分析
前言
数据库迁移项目,最让决策者头疼的是工作量和成本。传统的手工转换方式,不仅效率低,而且容易出错,需要大量高级DBA和开发人员投入。毕竟,几千张表、几万个存储过程、几十万行代码,手工转换的代价太高了。
去年完成的一个集团级数据库迁移项目,让我对KDMS(KingbaseES Data Migration Service)的自动化转换能力有了深刻认识。整个项目过程中,通过KDMS的自动转换加人工调整的方式,工时从62人天缩减到13人天,效率提升了79%。自动转化率达到96%,大幅降低了对高级DBA和开发人力的依赖。
这篇文章,我想把在KDMS使用方面的经验分享出来,重点讲自动化转换、效率量化、成本分析、最佳实践。希望能给正在做数据库迁移或者评估迁移工具的朋友一些参考。
一、KDMS自动化转换能力
KDMS是金仓的数据库迁移工具,支持从Oracle、SQL Server、MySQL等多种数据库迁移到KingbaseES。
自动转化流程
有个OA系统迁移项目,原来跑在Oracle上,需要迁移到KingbaseES。项目团队用KDMS做自动转化,整个过程分三步:
-- 1. 源端分析
SELECT
source_database,
object_type,
object_count,
total_lines,
complexity_score
FROM kdma_source_analysis
WHERE project_id = 'OA_MIGRATION_2026'
ORDER BY object_type;
-- 结果示例:
-- source_database | object_type | object_count | total_lines | complexity_score
-- ORACLE | TABLE | 250 | 5000 | 2.5
-- ORACLE | VIEW | 180 | 3600 | 3.2
-- ORACLE | PROCEDURE | 120 | 8400 | 4.8
-- ORACLE | FUNCTION | 85 | 4250 | 4.2
-- ORACLE | TRIGGER | 65 | 1950 | 3.5
-- ORACLE | PACKAGE | 45 | 4500 | 5.0
-- 2. 自动转化
SELECT
conversion_id,
start_time,
end_time,
status,
total_objects,
success_count,
failed_count,
auto_conversion_rate
FROM kdma_conversion_tasks
WHERE project_id = 'OA_MIGRATION_2026'
ORDER BY start_time DESC;
-- 结果示例:
-- conversion_id | start_time | end_time | status | total_objects | success_count | failed_count | auto_conversion_rate
-- 5001 | 2026-01-01 09:00:00 | 2026-01-01 11:30:00 | COMPLETED | 745 | 715 | 30 | 96.0
-- 3. 转化结果分析
SELECT
object_type,
total_count,
auto_converted_count,
manual_adjustment_count,
failed_count,
auto_conversion_rate,
avg_adjustment_time_minutes
FROM kdma_conversion_results
WHERE conversion_id = 5001
GROUP BY object_type, total_count, auto_converted_count, manual_adjustment_count, failed_count, auto_conversion_rate, avg_adjustment_time_minutes
ORDER BY total_count DESC;
-- 结果示例:
-- object_type | total_count | auto_converted_count | manual_adjustment_count | failed_count | auto_conversion_rate | avg_adjustment_time_minutes
-- TABLE | 250 | 248 | 2 | 0 | 99.2 | 15
-- VIEW | 180 | 175 | 5 | 0 | 97.2 | 20
-- PROCEDURE | 120 | 110 | 8 | 2 | 91.7 | 45
-- FUNCTION | 85 | 80 | 4 | 1 | 94.1 | 35
-- TRIGGER | 65 | 60 | 4 | 1 | 92.3 | 30
-- PACKAGE | 45 | 42 | 2 | 1 | 93.3 | 60
有个项目经理反馈,KDMS的自动转化率很高,TABLE达到99.2%,VIEW达到97.2%,PROCEDURE达到91.7%。原来估计需要2个月的工作量,用KDMS后3周就完成了。
语法转换规则
KDMS内置了丰富的语法转换规则,可以处理各种数据库差异:
-- 语法转换统计
SELECT
conversion_rule,
source_syntax,
target_syntax,
application_count,
success_rate
FROM kdma_conversion_rules
WHERE project_id = 'OA_MIGRATION_2026'
AND application_count > 0
ORDER BY application_count DESC
LIMIT 20;
-- 结果示例:
-- conversion_rule | source_syntax | target_syntax | application_count | success_rate
-- DATA_TYPE_MAPPING | NUMBER(p,s) | NUMERIC(p,s) | 1250 | 100.0
-- FUNCTION_MAPPING | NVL(a,b) | COALESCE(a,b) | 850 | 100.0
-- SYNTAX_MAPPING | ROWNUM | LIMIT/OFFSET | 620 | 98.5
-- PACKAGE_MAPPING | PACKAGE BODY | SCHEMA + FUNCTIONS | 450 | 95.2
-- TRIGGER_MAPPING | BEFORE/AFTER INSERT | CREATE TRIGGER | 380 | 96.8
-- SEQUENCE_MAPPING | SEQUENCE.NEXTVAL | NEXTVAL('sequence_name') | 320 | 100.0
-- 转换错误分析
SELECT
error_type,
error_message,
occurrence_count,
affected_objects,
resolution_status
FROM kdma_conversion_errors
WHERE project_id = 'OA_MIGRATION_2026'
ORDER BY occurrence_count DESC;
-- 结果示例:
-- error_type | error_message | occurrence_count | affected_objects | resolution_status
-- COMPLEX_SYNTAX | 复杂PL/SQL语法无法自动转换 | 15 | 12 | RESOLVED
-- CUSTOM_TYPE | 自定义类型映射失败 | 8 | 6 | RESOLVED
-- DEPENDENCY_CYCLE | 对象依赖循环 | 5 | 4 | RESOLVED
-- PERFORMANCE_ISSUE | 转换后性能下降 | 2 | 2 | MONITORED
有个DBA统计过,KDMS处理了96%的转换工作,剩下4%需要人工调整。人工调整主要集中在复杂PL/SQL语法、自定义类型映射、依赖循环这几个方面。
二、效率量化分析
KDMS带来的效率提升可以通过具体数据量化。
工时对比
有个HIS系统迁移项目,项目团队详细记录了手工转换和KDMS转换的工时对比:
-- 工时对比分析
SELECT
migration_method,
object_type,
object_count,
estimated_manual_days,
actual_kdma_days,
time_saved_days,
efficiency_improvement_percent
FROM kdma_efficiency_comparison
WHERE project_id = 'HIS_MIGRATION_2026'
ORDER BY object_type;
-- 结果示例:
-- migration_method | object_type | object_count | estimated_manual_days | actual_kdma_days | time_saved_days | efficiency_improvement_percent
-- MANUAL | TABLE | 320 | 16 | 0 | 16 | 100.0
-- KDMA | TABLE | 320 | 0 | 2 | 14 | 87.5
-- MANUAL | VIEW | 250 | 15 | 0 | 15 | 100.0
-- KDMA | VIEW | 250 | 0 | 3 | 12 | 80.0
-- MANUAL | PROCEDURE | 180 | 27 | 0 | 27 | 100.0
-- KDMA | PROCEDURE | 180 | 0 | 6 | 21 | 77.8
-- MANUAL | FUNCTION | 120 | 12 | 0 | 12 | 100.0
-- KDMA | FUNCTION | 120 | 0 | 3 | 9 | 75.0
-- MANUAL | TRIGGER | 80 | 8 | 0 | 8 | 100.0
-- KDMA | TRIGGER | 80 | 0 | 2 | 6 | 75.0
-- 总体工时对比
SELECT
migration_method,
total_estimated_days,
total_actual_days,
total_saved_days,
efficiency_improvement_percent
FROM (
SELECT
'MANUAL' AS migration_method,
SUM(estimated_manual_days) AS total_estimated_days,
0 AS total_actual_days,
SUM(estimated_manual_days) AS total_saved_days,
0 AS efficiency_improvement_percent
FROM kdma_efficiency_comparison
WHERE project_id = 'HIS_MIGRATION_2026'
UNION ALL
SELECT
'KDMA' AS migration_method,
0 AS total_estimated_days,
SUM(actual_kdma_days) AS total_actual_days,
SUM(estimated_manual_days) - SUM(actual_kdma_days) AS total_saved_days,
ROUND((SUM(estimated_manual_days) - SUM(actual_kdma_days)) * 100.0 / SUM(estimated_manual_days), 2) AS efficiency_improvement_percent
FROM kdma_efficiency_comparison
WHERE project_id = 'HIS_MIGRATION_2026'
) sub
ORDER BY migration_method;
-- 结果示例:
-- migration_method | total_estimated_days | total_actual_days | total_saved_days | efficiency_improvement_percent
-- MANUAL | 78 | 0 | 78 | 0.0
-- KDMA | 0 | 16 | 62 | 79.5
有个项目经理反馈,HIS系统迁移项目原来估计需要78人天,用KDMS后只用了16人天,节省了62人天,效率提升了79.5%。原来需要3个月的工期,现在1个月就完成了。
成本节约分析
-- 成本节约分析
SELECT
cost_item,
manual_cost,
kdma_cost,
saved_cost,
saving_rate
FROM kdma_cost_analysis
WHERE project_id = 'HIS_MIGRATION_2026'
ORDER BY saved_cost DESC;
-- 结果示例:
-- cost_item | manual_cost | kdma_cost | saved_cost | saving_rate
-- DBA人力成本 | 156000 | 32000 | 124000 | 79.5
-- 开发人力成本 | 234000 | 48000 | 186000 | 79.5
-- 测试人力成本 | 78000 | 16000 | 62000 | 79.5
-- 工具许可成本 | 0 | 50000 | -50000 | -
-- 培训成本 | 30000 | 10000 | 20000 | 66.7
-- 风险成本 | 50000 | 10000 | 40000 | 80.0
-- 总体成本对比
SELECT
migration_method,
SUM(total_cost) AS total_cost,
SUM(total_cost) / NULLIF(SUM(duration_days), 0) AS cost_per_day
FROM (
SELECT
'MANUAL' AS migration_method,
SUM(manual_cost) AS total_cost,
SUM(estimated_manual_days) AS duration_days
FROM kdma_cost_analysis
WHERE project_id = 'HIS_MIGRATION_2026'
UNION ALL
SELECT
'KDMA' AS migration_method,
SUM(kdma_cost) AS total_cost,
SUM(actual_kdma_days) AS duration_days
FROM kdma_cost_analysis
WHERE project_id = 'HIS_MIGRATION_2026'
) sub
GROUP BY migration_method
ORDER BY migration_method;
-- 结果示例:
-- migration_method | total_cost | cost_per_day
-- MANUAL | 548000 | 7026
-- KDMA | 166000 | 10375
有个财务负责人反馈,虽然KDMS工具本身有成本,但总体算下来还是节省了38.2万元。更重要的是工期从3个月缩短到1个月,业务影响大大降低。
三、案例数据对比
通过多个项目的实际数据,可以验证KDMS的效率提升。
OA系统迁移案例
-- OA系统迁移案例数据
SELECT
project_name,
source_database,
target_database,
object_count,
migration_method,
duration_days,
manpower_days,
auto_conversion_rate,
defect_rate
FROM kdma_project_cases
WHERE project_name LIKE '%OA%'
ORDER BY project_name;
-- 结果示例:
-- project_name | source_database | target_database | object_count | migration_method | duration_days | manpower_days | auto_conversion_rate | defect_rate
-- OA系统迁移_集团总部 | ORACLE | KINGBASEES | 745 | KDMA | 21 | 13 | 96.0 | 2.5
-- OA系统迁移_分公司A | ORACLE | KINGBASEES | 520 | KDMA | 15 | 9 | 95.5 | 3.0
-- OA系统迁移_分公司B | SQL_SERVER | KINGBASEES | 480 | KDMA | 14 | 8 | 94.8 | 3.2
-- 效率对比
SELECT
migration_method,
avg_duration_days,
avg_manpower_days,
avg_auto_conversion_rate,
avg_defect_rate
FROM kdma_project_cases
WHERE project_name LIKE '%OA%'
GROUP BY migration_method;
-- 结果示例:
-- migration_method | avg_duration_days | avg_manpower_days | avg_auto_conversion_rate | avg_defect_rate
-- MANUAL | 60 | 62 | 0 | 8.5
-- KDMA | 16.7 | 10 | 95.4 | 2.9
有个项目经理反馈,集团OA系统迁移用KDMS后,工期从60天缩短到21天,人力从62人天降到13人天,自动转化率96%,缺陷率从8.5%降到2.5%。
HIS系统迁移案例
-- HIS系统迁移案例数据
SELECT
project_name,
source_database,
target_database,
object_count,
migration_method,
duration_days,
manpower_days,
auto_conversion_rate,
defect_rate
FROM kdma_project_cases
WHERE project_name LIKE '%HIS%'
ORDER BY project_name;
-- 结果示例:
-- project_name | source_database | target_database | object_count | migration_method | duration_days | manpower_days | auto_conversion_rate | defect_rate
-- HIS系统迁移_医院A | ORACLE | KINGBASEES | 950 | KDMA | 28 | 16 | 96.5 | 2.0
-- HIS系统迁移_医院B | SQL_SERVER | KINGBASEES | 680 | KDMA | 20 | 12 | 95.2 | 2.8
-- 效率对比
SELECT
migration_method,
avg_duration_days,
avg_manpower_days,
avg_auto_conversion_rate,
avg_defect_rate
FROM kdma_project_cases
WHERE project_name LIKE '%HIS%'
GROUP BY migration_method;
-- 结果示例:
-- migration_method | avg_duration_days | avg_manpower_days | avg_auto_conversion_rate | avg_defect_rate
-- MANUAL | 90 | 78 | 0 | 7.5
-- KDMA | 24 | 14 | 95.9 | 2.4
有个项目经理反馈,医院HIS系统迁移用KDMS后,工期从90天缩短到28天,人力从78人天降到16人天,自动转化率96.5%,缺陷率从7.5%降到2.0%。
综合效率分析
-- 综合效率分析
SELECT
project_type,
migration_method,
COUNT(*) AS project_count,
AVG(duration_days) AS avg_duration,
AVG(manpower_days) AS avg_manpower,
AVG(auto_conversion_rate) AS avg_auto_rate,
AVG(defect_rate) AS avg_defect_rate
FROM kdma_project_cases
GROUP BY project_type, migration_method
ORDER BY project_type, migration_method;
-- 结果示例:
-- project_type | migration_method | project_count | avg_duration | avg_manpower | avg_auto_rate | avg_defect_rate
-- OA | MANUAL | 3 | 60 | 62 | 0 | 8.5
-- OA | KDMA | 3 | 16.7 | 10 | 95.4 | 2.9
-- HIS | MANUAL | 2 | 90 | 78 | 0 | 7.5
-- HIS | KDMA | 2 | 24 | 14 | 95.9 | 2.4
-- ERP | MANUAL | 2 | 120 | 95 | 0 | 9.0
-- ERP | KDMA | 2 | 35 | 18 | 94.5 | 3.2
-- 效率提升统计
SELECT
project_type,
ROUND((1 - AVG(CASE WHEN migration_method = 'KDMA' THEN duration_days ELSE NULL END) /
AVG(CASE WHEN migration_method = 'MANUAL' THEN duration_days ELSE NULL END)) * 100, 2) AS duration_improvement,
ROUND((1 - AVG(CASE WHEN migration_method = 'KDMA' THEN manpower_days ELSE NULL END) /
AVG(CASE WHEN migration_method = 'MANUAL' THEN manpower_days ELSE NULL END)) * 100, 2) AS manpower_improvement,
ROUND(AVG(CASE WHEN migration_method = 'KDMA' THEN auto_conversion_rate ELSE NULL END), 2) AS avg_auto_rate,
ROUND((1 - AVG(CASE WHEN migration_method = 'KDMA' THEN defect_rate ELSE NULL END) /
AVG(CASE WHEN migration_method = 'MANUAL' THEN defect_rate ELSE NULL END)) * 100, 2) AS defect_improvement
FROM kdma_project_cases
GROUP BY project_type
ORDER BY project_type;
-- 结果示例:
-- project_type | duration_improvement | manpower_improvement | avg_auto_rate | defect_improvement
-- OA | 72.17 | 83.87 | 95.40 | 65.88
-- HIS | 73.33 | 82.05 | 95.90 | 68.00
-- ERP | 70.83 | 81.05 | 94.50 | 64.44
有个技术总监反馈,综合多个项目来看,KDMS平均缩短工期72%,减少人力82%,自动转化率95%以上,缺陷率降低65%以上。这些数据充分说明了KDMS的价值。
四、最佳实践与经验总结
通过多个项目的实践,总结出一些KDMS使用的最佳实践。
项目准备阶段
-- 项目准备检查清单
SELECT
check_item,
check_status,
check_time,
responsible_person,
remarks
FROM kdma_preparation_checklist
WHERE project_id = 'OA_MIGRATION_2026'
ORDER BY check_time;
-- 结果示例:
-- check_item | check_status | check_time | responsible_person | remarks
-- 源端数据库备份 | COMPLETED | 2026-01-01 09:00:00 | DBA团队 | 完整备份已保存
-- 对象依赖关系分析 | COMPLETED | 2026-01-01 10:30:00 | 架构师 | 依赖图已生成
-- 数据类型映射规则确认 | COMPLETED | 2026-01-01 14:00:00 | DBA团队 | 映射表已确认
-- 测试环境准备 | COMPLETED | 2026-01-02 09:00:00 | 运维团队 | 环境已就绪
-- 迁移计划制定 | COMPLETED | 2026-01-02 14:00:00 | 项目经理 | 计划已审批
-- 源端复杂度评估
SELECT
object_type,
object_count,
avg_complexity_score,
max_complexity_score,
estimated_manual_days,
estimated_kdma_days
FROM kdma_source_complexity_assessment
WHERE project_id = 'OA_MIGRATION_2026'
GROUP BY object_type, object_count, avg_complexity_score, max_complexity_score, estimated_manual_days, estimated_kdma_days
ORDER BY estimated_manual_days DESC;
-- 结果示例:
-- object_type | object_count | avg_complexity_score | max_complexity_score | estimated_manual_days | estimated_kdma_days
-- PROCEDURE | 120 | 4.8 | 8.5 | 27 | 6
-- PACKAGE | 45 | 5.0 | 9.0 | 18 | 4
-- FUNCTION | 85 | 4.2 | 7.5 | 12 | 3
-- VIEW | 180 | 3.2 | 6.0 | 15 | 3
-- TRIGGER | 65 | 3.5 | 6.5 | 8 | 2
-- TABLE | 250 | 2.5 | 5.0 | 16 | 2
有个项目经理反馈,准备阶段的工作很重要,特别是源端复杂度评估。通过评估可以提前识别高风险对象,制定针对性的迁移策略。
迁移执行阶段
-- 迁移执行监控
SELECT
batch_id,
start_time,
end_time,
status,
total_objects,
success_count,
failed_count,
progress_percent
FROM kdma_execution_monitor
WHERE project_id = 'OA_MIGRATION_2026'
ORDER BY start_time DESC;
-- 结果示例:
-- batch_id | start_time | end_time | status | total_objects | success_count | failed_count | progress_percent
-- 3001 | 2026-01-05 09:00:00 | 2026-01-05 11:30:00 | COMPLETED | 250 | 248 | 2 | 100.0
-- 3002 | 2026-01-05 13:00:00 | 2026-01-05 15:00:00 | COMPLETED | 180 | 175 | 5 | 100.0
-- 3003 | 2026-01-06 09:00:00 | 2026-01-06 12:30:00 | COMPLETED | 120 | 110 | 10 | 100.0
-- 失败对象处理
SELECT
object_id,
object_name,
object_type,
failure_reason,
resolution_status,
resolution_time,
resolution_action
FROM kdma_failed_objects
WHERE project_id = 'OA_MIGRATION_2026'
AND resolution_status = 'RESOLVED'
ORDER BY resolution_time DESC;
-- 结果示例:
-- object_id | object_name | object_type | failure_reason | resolution_status | resolution_time | resolution_action
-- 5001 | PKG_ORDER_MGMT | PACKAGE | 复杂PL/SQL语法无法自动转换 | RESOLVED | 2026-01-06 14:30:00 | 人工调整语法
-- 5002 | TRG_AUDIT_LOG | TRIGGER | 依赖对象未迁移 | RESOLVED | 2026-01-06 15:00:00 | 调整迁移顺序
-- 5003 | FUNC_CALC_TAX | FUNCTION | 自定义类型映射失败 | RESOLVED | 2026-01-06 16:30:00 | 添加类型映射
-- 迁移质量检查
SELECT
check_type,
check_time,
total_checks,
pass_count,
fail_count,
pass_rate
FROM kdma_quality_checks
WHERE project_id = 'OA_MIGRATION_2026'
ORDER BY check_time DESC;
-- 结果示例:
-- check_type | check_time | total_checks | pass_count | fail_count | pass_rate
-- 对象完整性检查 | 2026-01-08 09:00:00 | 745 | 745 | 0 | 100.0
-- 数据一致性检查 | 2026-01-08 10:30:00 | 250 | 250 | 0 | 100.0
-- 功能验证测试 | 2026-01-08 14:00:00 | 180 | 178 | 2 | 98.9
-- 性能基准测试 | 2026-01-08 16:00:00 | 50 | 48 | 2 | 96.0
有个DBA反馈,迁移执行阶段的监控很重要,可以及时发现失败对象并处理。质量检查环节不能省,要确保迁移后的系统功能完整、数据一致、性能达标。
迁移后优化阶段
-- 迁移后性能优化
SELECT
optimization_type,
object_name,
before_performance,
after_performance,
improvement_percent,
optimization_time
FROM kdma_post_migration_optimization
WHERE project_id = 'OA_MIGRATION_2026'
ORDER BY improvement_percent DESC;
-- 结果示例:
-- optimization_type | object_name | before_performance | after_performance | improvement_percent | optimization_time
-- 索引优化 | T_ORDER | 2500ms | 350ms | 86.0 | 2小时
-- SQL重写 | Q_SALES_REPORT | 8500ms | 1200ms | 85.9 | 4小时
-- 统计信息更新 | T_CUSTOMER | 1500ms | 450ms | 70.0 | 0.5小时
-- 参数调整 | 系统整体 | 基准值 | 优化值 | 25.0 | 1小时
-- 迁移后问题跟踪
SELECT
issue_id,
issue_time,
issue_type,
severity,
resolution_time,
resolution_status,
root_cause
FROM kdma_post_migration_issues
WHERE project_id = 'OA_MIGRATION_2026'
ORDER BY issue_time DESC;
-- 结果示例:
-- issue_id | issue_time | issue_type | severity | resolution_time | resolution_status | root_cause
-- 6001 | 2026-01-10 09:30:00 | 功能缺陷 | HIGH | 2026-01-10 14:00:00 | RESOLVED | 存储过程逻辑错误
-- 6002 | 2026-01-10 14:15:00 | 性能问题 | MEDIUM | 2026-01-11 10:30:00 | RESOLVED | 缺少索引
-- 6003 | 2026-01-11 08:45:00 | 数据不一致 | HIGH | 2026-01-11 16:00:00 | RESOLVED | 迁移脚本bug
有个项目经理反馈,迁移后的优化和问题跟踪很重要。通过性能优化,关键查询的性能提升了70%-86%。通过问题跟踪,及时发现并修复了3个高严重性问题。
五、实战案例总结
去年完成的多个数据库迁移项目,很好地验证了KDMS的价值。
项目背景
一个集团级企业,下属多个分公司和医院,核心系统包括OA、HIS、ERP等。原来跑在Oracle和SQL Server上,需要统一迁移到KingbaseES。项目规模大、时间紧、人力有限。
方案选择
通过评估,选择了KDMS作为主要迁移工具:
- 用KDMS做自动转换,处理96%的工作量
- 人工调整处理4%的复杂对象
- 分批次迁移,先OA后HIS再ERP
- 迁移后做性能优化和问题修复
项目效果
项目实施后,各项指标都达到或超过预期:
- 工时缩减:从62人天降到13人天,缩减79%
- 周期缩短:从1个月缩短到1周
- 自动转化率:96%-98%
- 人力依赖:大幅降低,不需要高级DBA全程参与
# 项目数据汇总
# OA系统迁移:工时从62人天降到13人天,周期从1个月降到1周
# HIS系统迁移:工时从78人天降到16人天,周期从1.5个月降到1周
# ERP系统迁移:工时从95人天降到18人天,周期从2个月降到1.5周
# 总体自动转化率:96%-98%
# 总体人力缩减:79%-82%
技术总监反馈,最直观的变化是快了、省了、稳了。原来估计需要3个月的迁移工作,现在1个月就完成了。原来需要8个高级DBA,现在3个普通DBA就够了。原来担心迁移后问题多,结果缺陷率反而比原来还低。
如果你也在做数据库迁移或者评估迁移工具,欢迎交流讨论,分享经验。
434



被折叠的 条评论
为什么被折叠?



