简体   繁体   English

Sql Server Migration Assistant使用哪种数据库作为内部数据存储库?

[英]What kind of database the Sql Server Migration Assistant uses as an internal data repository?

What kind of database the Sql Server Migration Assistant uses as an internal data repository and stores it in the source-metabase.mb file? Sql Server Migration Assistant使用哪种数据库作为内部数据存储库并将其存储在source-metabase.mb文件中?

I guess that this it is one of standard tool that I could use to open and edit some entries (I need to autamatically add some custom scripts for tables with BLOBs data migration ) 我想这是我可以用来打开和编辑某些条目的标准工具之一(我需要为带有BLOB数据迁移的表自动添加一些自定义脚本)

You could also just suggest the way how to check most popular database formats: SqlServer Compact, MySQL, Access.. 您也可以建议如何检查最流行的数据库格式的方法:SqlServer Compact,MySQL,Access。

it is one of standard tool that I could use to open and edit some entries 它是我可以用来打开和编辑某些条目的标准工具之一

I would not count on it :) It was a proprietary metadata format that has nothing to do with DB products that SSMA supports. 我不会指望:)它是一种专有的元数据格式,与SSMA支持的数据库产品无关。 It can store metadata for representing Oracle and also SQL Server among others, obviously formats are not connected with file structure that actual DBs use. 它可以存储用于表示Oracle以及SQL Server等的元数据,显然格式与实际DB使用的文件结构无关。 SSMA format has no open docs, also it may fail to synchronize your changes after manual intervention if you reverse engineer it (due to the fact it was designed just as the migration tool to target SQL Server and was supposed to mostly create new objects there based on source database counterparts). SSMA格式没有开放的文档,如果您对它进行反向工程,则它在手动干预后也可能无法同步您的更改(由于它被设计为仅作为针对SQL Server的迁移工具,并且应该主要在此基础上创建新对象)在源数据库副本上)。

Can you just write some stored procedures or triggers in your database? 您可以只在数据库中编写一些存储过程或触发器吗? For most DBs metadata is exposed as special tables/views anyway. 无论如何,对于大多数数据库来说,元数据都是作为特殊的表/视图公开的。 Probably you need to do it only for SQL Server as it's your target db after migration, right? 可能您只需要对SQL Server进行此操作,因为它是迁移后的目标数据库,对吗? Looking into ways to directly parse or manipulate files managed by "big" DB (like SQL Server or Oracle) doesn't seem to be a good idea for most scenarios. 在大多数情况下,寻找直接解析或操纵“大”数据库(例如SQL Server或Oracle)管理的文件的方法似乎不是一个好主意。 (except digital forensics, for example) (例如,数字取证除外)

SQL Server metadata related views are here and functions are here . 与SQL Server元数据相关的视图在此处 ,函数在此处 You may profile your SQL Server instance while connecting to it with SSMA just to get some feel what it does to extract metadata (object names, columns of tables, source of SPs etc.) 您可以在使用SSMA连接到SQL Server实例时对其进行概要分析,以了解它提取元数据(对象名称,表的列,SP的来源等)的作用。

Data manipulation is pretty much clear from the DB side if you need it too. 如果需要的话,从数据库方面来看,数据操作也很清楚。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 数据迁移助手 SQL 服务器到 Azure VIEW 服务器 State - Data Migration Assistant SQL Server to Azure VIEW Server State SQL Server迁移助手问题 - SQL Server Migration Assistant issue 用于访问的SQL Server迁移助手 - Sql Server Migration Assistant for Access 用于访问的SQL Server迁移助手:日期数据类型 - SQL Server Migration Assistant for Access: Date data type 将Sybase数据库转换为MSSQL数据库加载数据库对象时出错Microsoft SQL Server迁移助手 - Converting Sybase Database to MSSQL Database Error loading database objects Microsoft SQL Server Migration Assistant SQL Server迁移助手身份生成 - SQL Server Migration Assistant Identity Generation MySQL到SQL Server迁移助手已经消失了吗? - MySQL to SQL Server Migration Assistant has disappeared? 使用 Microsoft SQL Server Migration Assistant for Access 将 Access 数据库转换为 MSSQL 数据库 - Converting Access Database to MSSQL Database Using Microsoft SQL Server Migration Assistant for Access 使用迁移助手工具迁移多个数据库 - SQL SERVER to AZURE SQL Database - Migrating multiple Databases using Migration Assistant Tool - SQL SERVER to AZURE SQL Database 数据迁移后的SQL数据库日志迁移sql server - SQL database log migration after data migration sql server
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM