We are currently working on a project to move all of our disparate DBs (MySQL, Oracle, older versions of MS SQL) to SQL Server 2014. So far, pretty much everything has gone smoothly, however, there is one Oracle Database (10g 10.2.0.5), which we're trying to migrate using SSMA that just doesn't show up in the SSMA object explorer. I have tried connecting to this database using the schema owner, the sys AND the system users and it just never shows up. ALL the other schemas on this instance show up and we can migrate them successfully. Has anyone come across this issue before? Could anyone suggest possible reasons for this? I - and the SQL Server DBA - am stumped. In the interim, we're migrating subsets of data using smacked-together Perl scripts, but this is obviously not ideal.

I'm using SSMA for the first time trying to migrate an Oracle XE schema to SQL Server Express. The majority of the tables get created and their data migrated just fine. There are a handful of tables though that keep giving me primary key violation. It tells me the duplicate key value, but when I query the Oracle table for that key there is only 1 record (which makes sense since it has the PK on it). I'm trying to figure out what I could be missing here because this can't be the real error. I mean the oracle table has the PK on it so it can't, and doesn't, have a duplicate value. So why is SSMA giving me seemingly a false error on this when clearly the source oracle table doesn't have this duplicate key in it?

For reporting purposes, we have a DWH (data warehouse) doing ETLs (extract-transform-load) to retrieve data from selected tables in a production OLTP (on-line transaction processing) database. The ETL extracts data with incremental manner, so it only fetches the changed part of data. Tentatively, we believe this should not affect the size of data as a result. It is a simple mapping, so for the selected tables, DWH has the same columns as OLTP. The DWH is SQL Server and the OLTP database is MySQL. Of course, the MySQL data types need to translate to corresponding types in SQL Server context, and we followed the standard in Microsoft SSMA (SQL Server Migration Assistant) . We noticed that the data became times bigger in SQL Server than in MySQL. For example, in an e-commerce Magento application: - The sales_order table contains 7'100'000 rows with size 5.5GB. - However, in the data warehouse, the same table sized 20GB with the same number of rows.\ Please see a partial table definition below. We checked the SQL Server database, it has SQL_Latin1_General_CP1_CI_AS collation and Simple recovery model. And the MySQL OLTP has default collation latin1_swedish_ci. **Our Questions:** - In our setting, why SQL Server got times bigger than MySQL for the same data? Please kindly point out if we missed something and the DWH can get smaller instead. - The straight mapping between OLTP and DWH was simple to implement, and it worked so far, so good. However, we knew that there are many columns fetched but never used in reporting. So, we wonder if there are better designs or best practices in data warehousing. We highly appreciate any hints and suggestions. **Details of the sample partial table definitions:** 1. MySQL OLTP, also refer to the model in Magento open-source repository :

-- msab_magento.sales_order definition

CREATE TABLE sales_order (
  entity_id int(10) unsigned NOT NULL AUTO_INCREMENT COMMENT 'Entity ID',
  state varchar(32) DEFAULT NULL COMMENT 'State',
  status varchar(32) DEFAULT NULL COMMENT 'Status',
  coupon_code varchar(255) DEFAULT NULL COMMENT 'Coupon Code',
  protect_code varchar(255) DEFAULT NULL COMMENT 'Protect Code',
  shipping_description varchar(255) DEFAULT NULL COMMENT 'Shipping Description',
  is_virtual smallint(5) unsigned DEFAULT NULL COMMENT 'Is Virtual',
  store_id smallint(5) unsigned DEFAULT NULL COMMENT 'Store ID',
  customer_id int(10) unsigned DEFAULT NULL COMMENT 'Customer ID',
  base_discount_amount decimal(20,4) DEFAULT NULL COMMENT 'Base Discount Amount',
  base_discount_canceled decimal(20,4) DEFAULT NULL COMMENT 'Base Discount Canceled',
  base_discount_invoiced decimal(20,4) DEFAULT NULL COMMENT 'Base Discount Invoiced',
  base_discount_refunded decimal(20,4) DEFAULT NULL COMMENT 'Base Discount Refunded',
  base_grand_total decimal(20,4) DEFAULT NULL COMMENT 'Base Grand Total',
  base_shipping_amount decimal(20,4) DEFAULT NULL COMMENT 'Base Shipping Amount',
  base_shipping_canceled decimal(20,4) DEFAULT NULL COMMENT 'Base Shipping Canceled',
  base_shipping_invoiced decimal(20,4) DEFAULT NULL COMMENT 'Base Shipping Invoiced',
  base_shipping_refunded decimal(20,4) DEFAULT NULL COMMENT 'Base Shipping Refunded',
  base_shipping_tax_amount decimal(20,4) DEFAULT NULL COMMENT 'Base Shipping Tax Amount',
  base_shipping_tax_refunded decimal(20,4) DEFAULT NULL COMMENT 'Base Shipping Tax Refunded',
  base_subtotal decimal(20,4) DEFAULT NULL COMMENT 'Base Subtotal',
  base_subtotal_canceled decimal(20,4) DEFAULT NULL COMMENT 'Base Subtotal Canceled',
  base_subtotal_invoiced decimal(20,4) DEFAULT NULL COMMENT 'Base Subtotal Invoiced',
  base_subtotal_refunded decimal(20,4) DEFAULT NULL COMMENT 'Base Subtotal Refunded',
  base_tax_amount decimal(20,4) DEFAULT NULL COMMENT 'Base Tax Amount',
  base_tax_canceled decimal(20,4) DEFAULT NULL COMMENT 'Base Tax Canceled',
  base_tax_invoiced decimal(20,4) DEFAULT NULL COMMENT 'Base Tax Invoiced',
  base_tax_refunded decimal(20,4) DEFAULT NULL COMMENT 'Base Tax Refunded',
  base_to_global_rate decimal(20,4) DEFAULT NULL COMMENT 'Base To Global Rate',
  base_to_order_rate decimal(20,4) DEFAULT NULL COMMENT 'Base To Order Rate',
  base_total_canceled decimal(20,4) DEFAULT NULL COMMENT 'Base Total Canceled',
  base_total_invoiced decimal(20,4) DEFAULT NULL COMMENT 'Base Total Invoiced',
  base_total_invoiced_cost decimal(20,4) DEFAULT NULL COMMENT 'Base Total Invoiced Cost',
  base_total_offline_refunded decimal(20,4) DEFAULT NULL COMMENT 'Base Total Offline Refunded',
  base_total_online_refunded decimal(20,4) DEFAULT NULL COMMENT 'Base Total Online Refunded',
  base_total_paid decimal(20,4) DEFAULT NULL COMMENT 'Base Total Paid',
  base_total_qty_ordered decimal(12,4) DEFAULT NULL COMMENT 'Base Total Qty Ordered',
  base_total_refunded decimal(20,4) DEFAULT NULL COMMENT 'Base Total Refunded',
  discount_amount decimal(20,4) DEFAULT NULL COMMENT 'Discount Amount',
  discount_canceled decimal(20,4) DEFAULT NULL COMMENT 'Discount Canceled',
  discount_invoiced decimal(20,4) DEFAULT NULL COMMENT 'Discount Invoiced',
  discount_refunded decimal(20,4) DEFAULT NULL COMMENT 'Discount Refunded',
  grand_total decimal(20,4) DEFAULT NULL COMMENT 'Grand Total',
  shipping_amount decimal(20,4) DEFAULT NULL COMMENT 'Shipping Amount',
  shipping_canceled decimal(20,4) DEFAULT NULL COMMENT 'Shipping Canceled',
  shipping_invoiced decimal(20,4) DEFAULT NULL COMMENT 'Shipping Invoiced',
  shipping_refunded decimal(20,4) DEFAULT NULL COMMENT 'Shipping Refunded',
  shipping_tax_amount decimal(20,4) DEFAULT NULL COMMENT 'Shipping Tax Amount',
  shipping_tax_refunded decimal(20,4) DEFAULT NULL COMMENT 'Shipping Tax Refunded',
  store_to_base_rate decimal(12,4) DEFAULT NULL COMMENT 'Store To Base Rate',
  store_to_order_rate decimal(12,4) DEFAULT NULL COMMENT 'Store To Order Rate',
  subtotal decimal(20,4) DEFAULT NULL COMMENT 'Subtotal',
  subtotal_canceled decimal(20,4) DEFAULT NULL COMMENT 'Subtotal Canceled',
  subtotal_invoiced decimal(20,4) DEFAULT NULL COMMENT 'Subtotal Invoiced',
  subtotal_refunded decimal(20,4) DEFAULT NULL COMMENT 'Subtotal Refunded',
  tax_amount decimal(20,4) DEFAULT NULL COMMENT 'Tax Amount',
  tax_canceled decimal(20,4) DEFAULT NULL COMMENT 'Tax Canceled',
  tax_invoiced decimal(20,4) DEFAULT NULL COMMENT 'Tax Invoiced',
  tax_refunded decimal(20,4) DEFAULT NULL COMMENT 'Tax Refunded',
  total_canceled decimal(20,4) DEFAULT NULL COMMENT 'Total Canceled',
  total_invoiced decimal(20,4) DEFAULT NULL COMMENT 'Total Invoiced',
  total_offline_refunded decimal(20,4) DEFAULT NULL COMMENT 'Total Offline Refunded',
  total_online_refunded decimal(20,4) DEFAULT NULL COMMENT 'Total Online Refunded',
  total_paid decimal(20,4) DEFAULT NULL COMMENT 'Total Paid',
  total_qty_ordered decimal(12,4) DEFAULT NULL COMMENT 'Total Qty Ordered',
  total_refunded decimal(20,4) DEFAULT NULL COMMENT 'Total Refunded',
  can_ship_partially smallint(5) unsigned DEFAULT NULL COMMENT 'Can Ship Partially',
  can_ship_partially_item smallint(5) unsigned DEFAULT NULL COMMENT 'Can Ship Partially Item',
  customer_is_guest smallint(5) unsigned DEFAULT NULL COMMENT 'Customer Is Guest',
  customer_note_notify smallint(5) unsigned DEFAULT NULL COMMENT 'Customer Note Notify',
  billing_address_id int(11) DEFAULT NULL COMMENT 'Billing Address ID',
  customer_group_id int(11) DEFAULT NULL,
	...
  reward_points_balance_refund int(11) DEFAULT NULL COMMENT 'Reward Points Balance Refund',
  PRIMARY KEY (entity_id),
  UNIQUE KEY SALES_ORDER_INCREMENT_ID_STORE_ID (increment_id,store_id),
  KEY SALES_ORDER_STATUS (status),
  KEY SALES_ORDER_STATE (state),
  KEY SALES_ORDER_STORE_ID (store_id),
  KEY SALES_ORDER_CREATED_AT (created_at),
  KEY SALES_ORDER_CUSTOMER_ID (customer_id),
  KEY SALES_ORDER_EXT_ORDER_ID (ext_order_id),
  KEY SALES_ORDER_QUOTE_ID (quote_id),
  KEY SALES_ORDER_UPDATED_AT (updated_at),
  KEY SALES_ORDER_SEND_EMAIL (send_email),
  KEY SALES_ORDER_EMAIL_SENT (email_sent),
  CONSTRAINT SALES_ORDER_CUSTOMER_ID_CUSTOMER_ENTITY_ENTITY_ID FOREIGN KEY (customer_id) REFERENCES customer_entity (entity_id) ON DELETE SET NULL,
  CONSTRAINT SALES_ORDER_STORE_ID_STORE_STORE_ID FOREIGN KEY (store_id) REFERENCES store (store_id) ON DELETE SET NULL
) ENGINE=InnoDB AUTO_INCREMENT=71xxxxx DEFAULT CHARSET=utf8 COMMENT='Sales Flat Order';

2. SQL Server DWH, generated by Microsoft SSMA for MySQL:

/****** Object:  Table [msab_magento].[sales_order]    Script Date: 10/11/2023 3:17:43 PM ******/
SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER ON
GO

CREATE TABLE [msab_magento].[sales_order](
	[entity_id] [bigint] IDENTITY(2956088,1) NOT NULL,
	[state] [nvarchar](32) NULL,
	[status] [nvarchar](32) NULL,
	[coupon_code] [nvarchar](255) NULL,
	[protect_code] [nvarchar](255) NULL,
	[shipping_description] [nvarchar](255) NULL,
	[is_virtual] [int] NULL,
	[store_id] [int] NULL,
	[customer_id] [bigint] NULL,
	[discount_amount] [decimal](20, 4) NULL,
	[discount_canceled] [decimal](20, 4) NULL,
	[discount_invoiced] [decimal](20, 4) NULL,
	[discount_refunded] [decimal](20, 4) NULL,
	[grand_total] [decimal](20, 4) NULL,
	[shipping_amount] [decimal](20, 4) NULL,
	[shipping_canceled] [decimal](20, 4) NULL,
	[shipping_invoiced] [decimal](20, 4) NULL,
	[shipping_refunded] [decimal](20, 4) NULL,
	[shipping_tax_amount] [decimal](20, 4) NULL,
	[shipping_tax_refunded] [decimal](20, 4) NULL,
	[store_to_base_rate] [decimal](12, 4) NULL,
	[store_to_order_rate] [decimal](12, 4) NULL,
	[subtotal] [decimal](20, 4) NULL,
	[subtotal_canceled] [decimal](20, 4) NULL,
	[subtotal_invoiced] [decimal](20, 4) NULL,
	[subtotal_refunded] [decimal](20, 4) NULL,
	[tax_amount] [decimal](20, 4) NULL,
	[tax_canceled] [decimal](20, 4) NULL,
	[tax_invoiced] [decimal](20, 4) NULL,
	[tax_refunded] [decimal](20, 4) NULL,
	[total_canceled] [decimal](20, 4) NULL,
	[total_invoiced] [decimal](20, 4) NULL,
	[total_offline_refunded] [decimal](20, 4) NULL,
	[total_online_refunded] [decimal](20, 4) NULL,
	[total_paid] [decimal](20, 4) NULL,
	[total_qty_ordered] [decimal](12, 4) NULL,
	[total_refunded] [decimal](20, 4) NULL,
	[can_ship_partially] [int] NULL,
	[can_ship_partially_item] [int] NULL,
	[customer_is_guest] [int] NULL,
	[customer_note_notify] [int] NULL,
	[billing_address_id] [int] NULL,
	[customer_group_id] [int] NULL,
	[edit_increment] [int] NULL,
	...
	[shipping_incl_tax] [decimal](20, 4) NULL,
 CONSTRAINT [PK_sales_order_entity_id] PRIMARY KEY CLUSTERED 
(
	[entity_id] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 95) ON [PRIMARY],
 CONSTRAINT [sales_order$SALES_ORDER_INCREMENT_ID_STORE_ID] UNIQUE NONCLUSTERED 
(
	[increment_id] ASC,
	[store_id] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 95) ON [PRIMARY]
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]

GO

ALTER TABLE [msab_magento].[sales_order] ADD  DEFAULT (NULL) FOR [state]
GO

ALTER TABLE [msab_magento].[sales_order] ADD  DEFAULT (NULL) FOR [status]
GO

...

ALTER TABLE [msab_magento].[sales_order] ADD  DEFAULT (NULL) FOR [shipping_incl_tax]
GO

EXEC sys.sp_addextendedproperty @name=N'MS_SSMA_SOURCE', @value=N'msab_magento.sales_order' , @level0type=N'SCHEMA',@level0name=N'msab_magento', @level1type=N'TABLE',@level1name=N'sales_order'
GO

I've just migrated a MySQL database over to Microsoft SQL Server using Microsoft SQL Server Migration Assistant for MySQL. For some reason the table names in SQL Server are not named the same way as in MySQL. If my table is named *accounts* in MySQL, if will after the migration be called *databaseName.accounts*, why is that? It makes it pretty annoying since I have to change the table names in all my queries to *database.OldDatabaseName.Table* instead of just *database.Table*. ### MySQL ## SQL Server Or can I somehow rename the tables? Because when I click rename I can only edit the last part: 'accounts'.

everyone. I am attempting to do a simple test migration of a table with 4 columns and 1 row from Oracle to SQL using SSMA. Brand new VM with Windows Server 2019 Datacenter and brand new SQL 2019 Dev ver 15.0.4083.2. Installed SSMA for Oracle 8.18.0 and SSMA for Oracle ExtensionPack_8.18.0. When I do sync with database after converting schemas I get this error: Errors: CREATE or ALTER ASSEMBLY for assembly 'SSMA4OracleSQLServerCollections.NET' with the SAFE or EXTERNAL_ACCESS option failed because the 'clr strict security' option of sp_configure is set to 1. Microsoft recommends that you sign the assembly with a certificate or asymmetric key that has a corresponding login with UNSAFE ASSEMBLY permission. Alternatively, you can trust the assembly using sp_add_trusted_assembly. I made sure that 'clr strict security' option of sp_configure is set to 0 but I still get the same error. I see 3 assemblies in the GUI of SSMA: Microsoft.SqlServer.Types SSMA4OracleSQLServerCollections.NET SSMA4OracleSQLServerCollections.NET I checked and all the files are present in "C:\Program Files\Microsoft SQL Server Migration Assistant for Oracle\bin". Tried to reinstall SSMA and got the same error. Tried it on a different server – same error. Does anyone know what am I missing? Thank you.

When using SQL Server Migration Assistant for Access with the Migration Wizard, all goes well converting an Access (2016) database to SQL Server Express (2017) until I get to the Link Tables step. Here the SQL Server connection dialogue appears: I enter the same credentials used to create the tables. My understanding is that this dialogue appears to allow for using a different SQL Server login with Access, so probably nothing out of the ordinary here. But then I receive the following error:

Connection failed:
SQLState: '01000'
SQL Server Error: 772
[Microsoft][ODBC SQL Server Driver]
[DBNETLIB]ConnectionOpen (SECDoClientHandshake()).
Connection failed:
SQLState: '08001'
SQL Server Error: 18
[Microsoft][ODBC SQL Server Driver]
[DBNETLIB]SSL Security error

I've tried with and without encrypting the connection with the same error, so it doesn't seem like an SSL error. I have four SQL Server ODBC drivers installed: - ODBC Driver 11 for SQL Server - ODBC Driver 13 for SQL Server - SQL Server - SQL Server Native Client 11.0 If I create a connections using the ODBC Data Source Administrator, I can produce the same error using the SQL Server driver. The other three work fine. So it seems that SSMA is using the *SQL Server* driver (oldest of the four) instead of the *SQL Server Native Client*, which is supposedly a dependency of SSMA.

I'm attempting to migrate a relatively large Oracle DB to MSSQL using SSMA however due to disk space constraints, I had to stop the full migration last night when it was 50% of the way through. Upon investigating disk space usage, I've found that the transaction log file is nearly 3x the size of the data files. Is there any way I can get this down? Would you recommend deleting the new DB and starting again from scratch? Would the Transaction log file have normalised in size if I let SSMA complete the migration? I've tried shrinking the txn log to no avail. Any help here is appreciated. Cheers Mark

I'm currently working on a project to convert our Access Apps to store the table data in SQL Server. Using SSMA to migrate the data results in the foreign keys and Look-ups work as expected in Access when completed. However, if I import & link directly from SQL Server back to Access, the foreign key look-ups do not work. The only difference I can determine in the links is, the ones SSMA created do not specify a DSN and the ones I manually created do. I'm hopefully someone might have run into this in the past and might have some insight. *We are migrating from Access 2013 to SQL Server 2012.*

I'm trying to use Microsoft's SQL Server Migration Assistant for Sybase ('SSMA') to migrate multiple Sybase databases (that have the same schema) to a single SQL Server database. All of the tables in the new SQL Server database will have an extra column project_id, which should have a fixed value depending on which Sybase database data is being migrated from. I've migrated the schema using SSMA, and then created the new columns in SSMS. But I the new columns aren't visible in SSMA, and I can't see any way to achieve what I want to do. How can I migrate data from each of the Sybase databases whilst utilising the extra project_id column?

I need to migrate an Oracle database in which there is more than one table. I created new SSMA project and grant all privileges to my Oracle user, but still an error occurs: > User does not have required permissions: SELECT ANY DICTIONARY. Anybody have idea how to solve this problem?

We have a very big Oracle db and want to archive whole of the oracle db to SQL Server. We are trying to weigh between SSIS v/s SSMA. Can the complete migration be achieved using SSMA? We do not have any schema/tables setup in sql. We need to migrate whole of the oracle db to sql. Is there any cons using SSMA in this kind of migration?

When I run the upsizing module it goes through the motions but the report at the end says >"table was skipped or export failed" for each of the tables. I can't find a solution for this. I can't figure out why this is?

I have Sql Server Migration Assistant for Access v2.7, running on Windows Server 2016. On the same server I have 64bit version of Access 2016 and a 32bit version (I assume) of Access 97. I am able to migrate Access 2007.accdb files on this server. However, when I click add database and choose an Access 97.mdb file I get the following error: *"Cannot open a database created with a previous version of your application."* Is it possible to migrate (directly) from Access 97 using this tool? The following link suggested it should be: https://learn.microsoft.com/en-us/sql/ssma/access/sql-server-migration-assistant-for-access-accesstosql *Microsoft SQL Server Migration Assistant (SSMA) for Access is a tool for migrating databases from Microsoft Access versions 97 through 2010 to Microsoft SQL Server 2005 / Microsoft SQL Server 2008 / Microsoft SQL Server 2012 / Microsoft SQL Server 2014 / Microsoft SQL Server 2016 / Microsoft SQL Server 2017*

I need to migrate some old MS Access data to a SQL Server Database. Which tool is easier for a newbie to work with: SQL Server Import/Export or Migration assistant for access(SSMA)

I'm trying to migrate a MySQL database to SQL Server using the **SQL Server Migration Assistant for MySQL**. Converting the schema and synchronizing with SQL Server works fine. However, after clicking the Migrate Data button, SSMA crashes after a few seconds (*SSMA has stopped working*). What might be the cause of this problem?

I'm working on migrating a legacy application's DB (in Access 2003 format) to a SQL Server 2008 back-end (This will be upgraded later on). We are close to hitting the 2GB size limit in Access and performance is starting to degrade, even with up to date indexes and constant compacts. I have successfully migrated the data into a SQL DB via SQLServer Migration Assistant (SSMA) for Access 2017, after fixing a few issues with tables not having primary keys. I am able to access the data through the legacy application as normal, but the data access during load is now taking up to 45 seconds for the initial query compared to 1 or 2 before the migration. Performance seems to improve after the initial load, however. I have loaded the application and watched on the SQL activity monitor the requests coming in, and the worst offender at 22 seconds is just a simple select: SELECT "Id" FROM "dbo"."Table" "t" The table itself has a little under 11,000 rows, and the query runs almost instantly through management studio, while taking around the same time running through Access and using the linked tables. The Access DB is on the same machine and same drive as the SQL DB, and is not going out over the network. Both are currently being run inside of a VM for testing purposes. Is there any way to speed up my queries using this method? Activity monitor is not showing any heavy CPU or I/O use during these queries so I do not think those are having a large effect on performance.

I am working in a Oracle 11g database migration to SQL Server 2012, I did the migration using SSMA v5.3 and all works fine. However, I did re-write code in some objects like triggers and stored procedures because the SSMA did a standard migration. But my questions is about this: The Oracle Db have some packages that use global variables like this code: CREATE OR REPLACE package OPS_TRACKING.pkg_trade_data as -- packaged variable to be used by triggers not to execute during -- archival and resoring process of the trade data archive_restore_flag varchar2(1) := 'N'; procedure p_archive_trade_data( p_trade_id number ); In my case this global variable is called for some triggers like it: CREATE OR REPLACE TRIGGER "OPS_TRACKING"."TG_TRADE_GROUP_AER_DI" after insert or delete on ops_tracking.trade_group for each row declare v_id number; v_trade_id number; begin If pkg_trade_data.archive_restore_flag = 'N' Then if inserting then v_trade_id := :new.trade_id; else v_trade_id := :old.trade_id; end if; select id into v_id from ops_tracking.trade_summary where trade_id = v_trade_id for update nowait; update ops_tracking.trade_summary set transaction_seq=ops_tracking.seq_trade_summary_transaction.nextval ,last_update_timestamp_gmt = sysdate where trade_id = v_trade_id; End If; -- archive_restore_flag end tg_trade_group_aer_di; / As you can see in this trigger the global variable (pkg_trade_data.archive_restore_flag = 'N') is used for take a decision and based in their value the oracle trigger execute the action. I would like to know which is the equivalent or which are my options to migrate this code to SQL 2012. I appreciate your comments and advice's.

Database migration from MySQL to MS SQL using SSMA tool is very nifty, however, I have one question around this. I have 2 MySQL Db's want to migrate to MS SQL, one sizes around 850 GB and another one around 450 GB, there are few tables have millions of records and migration take a day only for such tables. I was searching for a solution, if there is any way we can keep synching the data from source to destination after doing the first full pull migration. Your guidance is much appreciated. Thank you, Indra

I'm trying to use Microsoft's SQL Server Migration Assistant for Sybase 5.3 ('SSMA') to migrate multiple Sybase databases (that have the same schema) to a single MSSQL database. The first database migrated fine. But when I try to migrate data from the next one, I see lots of warnings like: The table 'MyDatabase.dbo.MyTable' contains data. If you continue with data migration, all data in the table will be deleted. I don't want the existing data to be deleted, but can't find a way to do this in SSMA.

I am using Microsoft SQL Server Migration Assistant v6 (aka SSMA) to update a database from Access to SQL Server. I am getting informational messages that say "A2SS0029: Index name 'Name' was changed during conversion.". As these are just index names, that shouldn't cause a problem for me. But I do wonder why the name has to be changed. Particularrly since I was able to create an index with the given name manually after the migration. Why are the index names being renamed? And am I wrong about that not causing any problems (given that I don't have any queries that use index hints, if that is even possible with Access).