Released: SQL Server Migration Assistant (SSMA) v7.3

Overview SQL Server Migration Assistant (SSMA)  for Oracle, MySQL, SAP ASE (formerly SAP Sybase ASE), DB2 and Access lets users convert database schema to Microsoft SQL Server schema, upload the schema, and migrate data to the target SQL Server (see below for supported versions). What is new? Improved quality and conversion metric with targeted fixes…


OracleToSQL: Collation

Description Oracle bases its language support on the values of parameters that begin with NLS. These parameters specify, for example, how to display currency or how the name of a day is spelled. Oracle Database provides the following types of collation: Binary Monolingual Multilingual Unicode Collation Algorithm (UCA) How to find feature enablement? SELECT *…

0

OracleToSQL: Database Logging

Description Redo logs are transaction journals. Each transaction is recorded in the redo logs. Though redo generation is expensive operation, Oracle uses online redo logs as hot backups in case of instance crashes to ensure recoverability to a consistent state. The online redo log files contain the information necessary to replay a transaction, committed or…

0

OracleToSQL: Database Audit

Description Auditing facilitates database activity monitoring. It’s the recording of selected user database actions. Monitoring statements, privileges, or objects Security policies can trigger auditing when specified elements in an Oracle database are accessed or altered AUDIT_SYS_OPERATIONS initialization parameter- Enables or disables the auditing of top-level operations directly issued by user SYS, and users connecting with…

0

Migration approach for Oracle features

This blog posting focuses on tasks associated with migrating an Oracle database to the latest version of SQL Server. If preparing for a migration requires changes to Oracle features/functionality, then it is important to carefully consider the potential impact of each change on the applications that use the database. This posting provides links to detail about workaround…

0

DEA 2.0: Telemetry and Local Audit for Database Experimentation Assistant

Database Experimentation Assistant contains an internet-enabled feature that can send telemetry information back to Microsoft. The same information is saved on your computer for Local Audit so that you can always see what information is being collected. All log files from DEA are saved in %temp%\DEA. In addition, you can decide which events get collected,…


DEA 2.0 Technical preview: Release Overview – Database Experimentation Assistant

Overview Database Experimentation Assistant (DEA) is a new A/B testing solution for SQL Server upgrades. It will assist in evaluating a targeted version of SQL for a given workload. Customers who are upgrading from previous SQL Server versions (SQL Server 2005 and above) to any new version of the SQL Server will be able to use these…


DEA 2.0: How to Use Database Experimentation Assistant

The Database Experimentation Assistant (DEA) is a new A/B testing solution for changes in SQL Server environments (e.g. upgrade, new indexes, etc.). It assists in evaluating how the workload on your source server (current environment) will perform against your new environment. It guides you through performing an A/B test through three steps: capture, replay, and…


DEA 2.0: Analysis FAQ  

 What security permissions do I need to generate and view an analysis report on my server? The current logged in user in DEA should have sysadmin privilege to the analysis server.  If the user is part of a group permission, make sure the group has sysadmin privileges as well.   Possible Errors: Explanation / Solution: “Unable to…

0

DEA 2.0 – Replay FAQ

For questions regarding configuration, following the instructions provided in Configure Replay Environment. 1. What security permissions do I need to start a replay capture on my target server? The Windows user performing the trace operation in the DEA Application should have sysadmin privileges in the target SQL Server. This is needed to start a trace. The service account, under…

0

DEA 2.0 – Capture Trace FAQ

What are the events captured while running trace on a production database? The following table provides the list of events and the corresponding column data that we collect for the traces Event Name Columns Text Data (1) Binary Data (2) Database ID (3) Host Name (8) Application Name (10) Login Name (11) SPID (12) Start…

0