I just installed Management Tools and SSMA for Sybase.  I am attempting to connect to my Sybase ASE 15 database to attempt a migration to MS-SQL 2008.  I have the Sybase 12.54 Client installed but I get an error message that SSMA cannot find the connectivity files when I try to connect to Sybase. I have reinstalled the Sybase Client and have rebooted.  I checked my ODBC DataSources and the Sybase drivers are there. I also have created ODBC datasources for both MS-SQL and Sybase, so I know the drivers work.

How do I get SSMA to find the Sybase Data Access Connectivity libraries? My SYBASE environmental is pointing to the correct location.

Thanks

Hello to all!

I have a question that is quite similar to this thread: http://social.msdn.microsoft.com/Forums/en-US/sqlservermigration/thread/4517b86b-5c87-45aa-95c4-e2c77633a7cd, but I'm not sure if at the end the user used the SSMA tool.

Maybe that thread could be a foregoing discussion.

I have used SQL Server Migration Assistant for Oracle  to make a few migrations and everything has worked fine but all the required work has been done manually. By manually I mean selecting which tables I want to migrate and the doing click on the migrate data button, just like 

this : http://blogs.msdn.com/b/ssma/archive/2010/08/27/migrating-oracle-s-sample-hr-schema.aspx

But then I realize that all those tasks could be done automatically by creating an agent job because according to the documentation:

"Every time that you migrate data to SQL Server, SSMA creates a SQL Server Agentjob. These are namedssma_oracle data migration package {GUID}, and are visible in the SQL Server Agent node of SQL Server Management Studio in thefolder."

So I was thinking if I could create the job that executes such job and scheduling it and then realized that the job it is deleted after finishing the manual migration.

According to the previous thread it can be done by creating a package which maps the desired tables from the Oracle source and then creates the destination tables in SQL Server.Once the package is created it can be used within a scheduled job but then ,¿where does the SSMA tool is used?

Is it possible to find a solution or it just can be done in such way?

Thank you.

I have an existing database originally created in SQL 2000.  When attempting to attach it to SQL 2012 for the first time, I get...

Database '<name here>' cannot be upgraded because its non-release version (539) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database.

However, I can attach it just fine to SQL 2005, 2008, or 2008 R2 with no issue.  And in fact if I attach it to any of those instances, then attach it to 2012, it works just fine.  But there appears to be no way to go directly from 2000 -> 2012.

Is this a bug?  Intentional?  I couldn't find any documentation about it's intent.  Suggesting that I recreate the database is a bit silly, there's a ton of tables and data inside it.  I have a large number of customers still on SQL 2000, and I'd like them to upgrade.  They're not going to readily have available other editions for an interim attachment, and there's too much data for me to download every data to my site, attach it once, and send it back.  

Is there another conversion tool that can be run?

Hello there,

We are currently using SSMA v5.2 to migrate from Oracle 10.2.04 to SQL 2008R2, we have a few tables that has very large row counts, one is 400million rows, another is around 30million rows (we have not selected to convert this 2 tables in the POC) and the one that caused the error on the topic is 300k rows but contains blob. Another table that contains blob but only about 30k rows were migrated fine if we selected it by itself, it took around 1hr for that particular table. With that in mind we thought that perhaps the table with 300k blob rows may be ok if selected by itself, but it threw the error around 25%

Is SSMA able to handle large blob migration for this case and are there any settings that can be tweaked to improve the migration. We are concern on the tables that have millions of rows if SSMA is failing on BLOB migration. Would appreciate any pointers/help/suggestions.

Thanks!

I have Windows server 2003 std/SQL server 2000 std server (old server).  I also have a "go between Work PC".  So the "Work" PC will be identical to the old server (Win2003\SQL2000).  I will copy the "Data" folder over from the old server to the "Work" PC, run the SQL 2008 Update in Place on it.   (So if something does not work, I can always plug the old server back in and then try to figure out what went wrong.  So I don't plan on clobbering the old server.)  I have new server I will setting up as Windows server 2008 std R2 / SQL server 2008 std R2 (32 bit SQL- same as before on SQL 2000).

With the SQL server software "stopped" on both servers (Work and New), can I hook a crossover cable between the 2 servers and copy the entire contents from Program Files\Microsoft SQL Server\MSSQL\Data folder from the Windows 2003\SQL 2008 (upgraded) machine to the "Data" folder on the new Windows 2008\SQL 2008 and everything be fine with SQL server?

This is how I've always done it on SQL 2000 to go from an old server to a new server and it has always worked.  Just wondering if that still applies in SQL 2008?

thanks

Murf

Hi I am migrating from oracle 11G to sql server 2008r2. Could you pl. tell me which collations settings are suitable/synchronizable to the following oracle collation settings.  Thanks my mail id isshivakumar_dontula@mahindrasatyam.com/mca.dece.shiva@live.in

Hi all,

DataBase migration needs to be done from sql server 2005 to sql server 2012

How can I test the synonyms  and setup the linked servers after restoring the DataBase.

Any tips plaese for doing better migration welocme!

Regards,

K

Hello everyone,

I have this issue with number of concurent connection to Informix db server which is actualy linked server in SQL 2012.
Speaking in other words, my application is querying SQL server, there is no direct connections from my application to Informix server, so I'm not the one who control number of connections to Informix. Since clients Informix has limited number of licences (connections) situations where SQL server exhaust all informix licences occurs from time to time.

Is there a way to control number of connection from sql server to infromix? And yes, underlying access to informix is through ODBC drivers.

Thanx,

Aleksandar

Hi,

We Migrate SQL Server from One Server to New Server.

What steps and what should i include in document ?.

My Server Ip remaining same for New Server.

-- Bhavesh Thakkar

Sr.Database Administrator
My Blog
Linked In Profile

Hi

I am using SSMA for Access to transfer data from MS Access 2007 to SQL Server 2008. I use SQL Authentication and the opertion is successful. When I run my Access aplication, it expects windows authentication. The linked tables in Access app have no UID and PWD for username and password. Its strange that SSMA software in table information for linked tables uses UID and PWD. Without SQL authentication my Access app is useless. please help me.

Thanks 

Dear friends,
I am doing conversion from Oracle 10g to SQL Server 2008. SQL Server 2008 runs on computer with Windows 7. Firstly I have prepared schema of database with using of offer "Convert schema" in SQL Server Metadata Explorer.

And then I started to migrate Data. But this problem appeared. SSMA wrote me, tables XY doesn't exist in target. But when I repeated to prepare its with using of Convert schema, SSMA wrote me - Tables XY already exist. But in SQL Server Management Studio it doesn't exist any new database schema. Could you help me, please? Anna

I am attempting to automate the process of migrating an Access database to SQL Server via the SSMA Console. The process works flawlessly via the GUI, but the console seems to have a very basic, but common coding issue -- or I'm missing something.

Here is what is happening:

I have used the sample scripts to customize my needs as they seem to provide everything I need -- that being a very basic access database being linked into a very basic sql database...

I have built a batch file that executes the following: 
SSMAforAccessConsole.exe -s script.xml -c server.xml -v variables.xml -l log.txt

The console ends with this message: 
[2/4/2013 11:44:49 AM]    START map-schema
FATALERR Access Database was not found by name 'Test_Access_Database'

In locating the map-schema line (in script.xml) it reads:
<map-schema source-schema="$AccessDatabase$" sql-server-schema="$SQLServerDb$.dbo" />

Referencing the AccessDatabase variable line, which reads:
<variable name="$AccessDatabase$" value="Test_Access_Database.mdb"/>

I know that the AccessDatabase variable is being read properly prior to this, in-code, because if I change the value to an incorrect file name it will ding me with the ".mdb" still appended... and I am sure that this is the area where it is breaking because if I, for example, "hard-code" a '1' before the variable  the error reads:
FATALERR Access Database was not found by name '1Test_Access_Database'

A common mistake made by programmers (being one myself) is to unintentionally parse a string containing a file name through a function that removes the file extension (thus giving just the file's root name)... I believe this is the case with this scenario.

Obviously I could be mistaken, or I could just run it manually, but I need this to be an automated process as it is a part of my company's life-cycle and they require their database admins to execute and test the process.

Please let me know as soon as possible if I'm making a simple mistake, or of any work-arounds or patches that could allow me to continue using this product as a solution -- as it does appear to be the most accurate and dependable process available for performing this task.

Here is my full list of scripts being used:

(Please note that all of my Schemas are in a custom directory, thus I have removed one '.' directory iterator from my scripts)

script.xml

<?xml version="1.0" encoding="utf-8"?><ssma-script-file xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation=".\Schemas\A2SSConsoleScriptSchema.xsd"><config><output-providers>      <output-window suppress-messages="false" destination="file" file-name="./LogMessages.txt"/><upgrade-project action="yes"/><user-input-popup mode="continue"/><data-migration-connection source-use-last-used="false"
                                 target-server="$SQLServerName$"/><progress-reporting enable="true"
                          report-messages="true"
                          report-progress="every-1%"/><reconnect-manager on-source-reconnect="reconnect-to-last-used-server" 
							           on-target-reconnect="generate-an-error"/><object-overwrite action="overwrite" /><log-verbosity level="error"/></output-providers></config><script-commands><create-new-project project-folder="$project_folder$" 
						project-name="$project_name$" 
						overwrite-if-exists="true"
						project-type="$project-type$" /><load-access-database database-file="$AccessDbFolder$\$AccessDatabaseFile$"/><connect-target-database server="$SQLServerName$" /><map-schema source-schema="$AccessDatabase$" sql-server-schema="$SQLServerDb$.dbo" /><convert-schema object-name="$AccessDatabase$" 
                        object-type="Databases" /><synchronize-target object-name="$SQLServerDb$.dbo"
                        on-error="report-each-as-warning"
                        report-errors-to="$SynchronizationReports$" /><migrate-data object-name="$AccessDatabase$.Tables"
                  object-type="category"
                  write-summary-report-to="$SummaryReports$"
                  report-errors="true"
                  verbose="true" /><link-tables><metabase-object object-name="$AccessDatabase$.Tables" object-type="category"/></link-tables><save-project /><close-project if-modified="save" /></script-commands></ssma-script-file>

variables.xml

<?xml version="1.0" encoding="utf-8"?><variables xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation=".\Schemas\ConsoleScriptVariablesSchema.xsd"><variable name="$WorkingFolder$"  value="."/><variable-group name="AccessConnection"><variable name="$AccessDbFolder$" value="\\US_SERVER1\admin$$"/><variable name="$AccessDatabase$" value="Test_Access_Database.mdb"/><variable name="$AccessDatabaseFile$" value="$AccessDatabase$.accdb"/></variable-group><variable-group name="SQLServerConnection"><variable name="$SQLServerName$" value="(local)"/><variable name="$SQLServerDb$"  value="TEST_SQL_DB"/></variable-group><variable-group name="TEST_SQL_DB"><variable name="$project_folder$" value="$WorkingFolder$\$project_name$"/><variable name="$project_name$" value="TEST_SQL_DB_TEST1"/><variable name="$project-type$" value="sql-server-2008"/><variable name="$ConvertARReportsFolder$"  value="$WorkingFolder$\$AssessmentReportFolderName$"/><variable name="$SynchronizationReports$" value="$WorkingFolder$"/><variable name="$SaveScriptFolder$" value="$WorkingFolder$"/><variable name="$AssessmentReportFolderName$"       value="AssessmentReports"/><variable name="$AssessmentReports$"                value="$WorkingFolder$\$AssessmentReportFolderName$"/><variable name="$SummaryReports$"                   value="$WorkingFolder$"/></variable-group></variables>

server.xml

<?xml version="1.0" encoding="utf-8"?><servers xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation=".\Schemas\A2SSConsoleScriptServersSchema.xsd"><sql-server name="(local)"><windows-authentication><database value ="$SQLServerDb$"/><server value ="$SQLServerName$"/><encrypt value="true"/><trust-server-certificate value="true"/></windows-authentication></sql-server>  </servers>

Log Results:

[Command Line Processor: Mandatory] [6156/1] [2013-02-04 12:53:03]: Microsoft SSMA for Access v5.2.1257
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: Start Validating command sequence....
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: Validating command sequence finished....
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: #### Start processing command sequence...
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: ## Processing command #1
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: ## Command code: create-new-project 
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: CommandStarted was called with command code: create-new-project
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: Creating project 'TEST_SQL_DB_TEST1' in folder '.\TEST_SQL_DB_TEST1'
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 1%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 2%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 3%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 4%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 5%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 6%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 7%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 8%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 9%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 10%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 11%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 12%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 13%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 14%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 15%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 16%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 17%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 18%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 19%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 20%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 21%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:03]: WriteCommandResult was called with result code 'progress-pct', and value: 22%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 23%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 24%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 25%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 26%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 27%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 28%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 29%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 30%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 31%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 32%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 33%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 34%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 35%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 36%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 37%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 38%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 39%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 40%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 41%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 42%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 43%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 44%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 45%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 46%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 47%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 48%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 49%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 50%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 51%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 52%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 53%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 54%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 55%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 56%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 57%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 58%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 59%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 60%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 61%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 62%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 63%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 64%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 65%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 66%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 67%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 68%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 69%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 70%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 71%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 72%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 73%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 74%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 75%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 76%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 77%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 78%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 79%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 80%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 81%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 82%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 83%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 84%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 85%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 86%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 87%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 88%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 89%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 90%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 91%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 92%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 93%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 94%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 95%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 96%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 97%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 98%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 99%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 100%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: Project created
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: CommandFinished was called
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: ## Command processed
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: ## Processing command #2
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: ## Command code: load-access-database 
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: CommandStarted was called with command code: load-access-database
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteWarningMessage was called with message: No files found with pattern '\\US_SERVER1\admin$\Test_Access_Database.mdb.accdb'
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: CommandFinished was called
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: ## Command processed
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: ## Processing command #3
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: ## Command code: connect-target-database 
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: CommandStarted was called with command code: connect-target-database
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: Establishing connection to sql-server server '(local)'
[Generic: Error] [6156/3] [2013-02-04 12:53:04]: Exception: The remote server returned an error: (407) Proxy Authentication Required.
 site: System.Net.WebResponse GetResponse()
 source: System
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.SSMA.Framework.Generic.SQM.SqmFileUploader.DoUpload()
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 1%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 2%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 3%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 4%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 5%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 6%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 7%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 8%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 9%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 10%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 11%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 12%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 13%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 14%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 15%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 16%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 17%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 18%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 19%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 20%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 21%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 22%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 23%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 24%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 25%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 26%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 27%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 28%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 29%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 30%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 31%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 32%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 33%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 34%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 35%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 36%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 37%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 38%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 39%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 40%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 41%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 42%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 43%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 44%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 45%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 46%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 47%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 48%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 49%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 50%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 51%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 52%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 53%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 54%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 55%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 56%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 57%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 58%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 59%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 60%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 61%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 62%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 63%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 64%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 65%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 66%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 67%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 68%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 69%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 70%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 71%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 72%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 73%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 74%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 75%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 76%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 77%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 78%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 79%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 80%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 81%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 82%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 83%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 84%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 85%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 86%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 87%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 88%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 89%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 90%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 91%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 92%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 93%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 94%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 95%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 96%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 97%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 98%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 99%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: WriteCommandResult was called with result code 'progress-pct', and value: 100%
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: CommandFinished was called
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: ## Command processed
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: ## Processing command #4
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: ## Command code: map-schema 
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: CommandStarted was called with command code: map-schema
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: ReportFatalException was called
[Command Line Processor: Info] [6156/1] [2013-02-04 12:53:04]: Exception: Access Database was not found by name 'Test_Access_Database'
 site: System.Collections.Generic.List`1[Microsoft.SSMA.Framework.Generic.XTree.XNode] SearchInMetabase(Microsoft.SSMA.Framework.Generic.Collectors.XMetabase, Microsoft.SSMA.Framework.Generic.SqlBase.CompoundObjectPath, Microsoft.SSMA.Framework.Generic.SSMAWorkspace.DefaultSSMAWorkspace)
 source: SSMAforAccessConsole
   at Microsoft.SSMA.GUI.Access2SqlServer.CommandProcessor.CommandProcessors.ObjectSearchHelper.SearchInMetabase(XMetabase metabase, CompoundObjectPath objectPath, DefaultSSMAWorkspace workspace)
   at Microsoft.SSMA.GUI.Generic.CommandProcessor.CommandProcessors.SchemaMappingAbstractProcessor.ProcessCommandImpl(XNode command)
   at Microsoft.SSMA.GUI.Generic.CommandProcessor.CommandProcessors.CommandAbstractProcessor.ProcessCommand(XNode command)
   at Microsoft.SSMA.GUI.Generic.CommandProcessor.AbstractCommandProcessor.ProcessCommand(XNode command)
   at Microsoft.SSMA.GUI.Generic.CommandProcessor.AbstractCommandProcessor.ProcessCommandSequence(XNode commandList)
   at Microsoft.SSMA.GUI.Generic.CommandProcessor.AbstractCommandProcessor.ProcessCommandFile(String scriptFile, String serversFile, List`1 variableFiles, Int32& exitCode)
[Command Line Processor: Error] [6156/1] [2013-02-04 12:53:04]: ## ERROR: Access Database was not found by name 'Test_Access_Database'
[Command Line Processor: Error] [6156/1] [2013-02-04 12:53:04]: Exception: Access Database was not found by name 'Test_Access_Database'

 site: System.Collections.Generic.List`1[Microsoft.SSMA.Framework.Generic.XTree.XNode] SearchInMetabase(Microsoft.SSMA.Framework.Generic.Collectors.XMetabase, Microsoft.SSMA.Framework.Generic.SqlBase.CompoundObjectPath, Microsoft.SSMA.Framework.Generic.SSMAWorkspace.DefaultSSMAWorkspace)
 source: SSMAforAccessConsole
   at Microsoft.SSMA.GUI.Access2SqlServer.CommandProcessor.CommandProcessors.ObjectSearchHelper.SearchInMetabase(XMetabase metabase, CompoundObjectPath objectPath, DefaultSSMAWorkspace workspace)
   at Microsoft.SSMA.GUI.Generic.CommandProcessor.CommandProcessors.SchemaMappingAbstractProcessor.ProcessCommandImpl(XNode command)
   at Microsoft.SSMA.GUI.Generic.CommandProcessor.CommandProcessors.CommandAbstractProcessor.ProcessCommand(XNode command)
   at Microsoft.SSMA.GUI.Generic.CommandProcessor.AbstractCommandProcessor.ProcessCommand(XNode command)
   at Microsoft.SSMA.GUI.Generic.CommandProcessor.AbstractCommandProcessor.ProcessCommandSequence(XNode commandList)
   at Microsoft.SSMA.GUI.Generic.CommandProcessor.AbstractCommandProcessor.ProcessCommandFile(String scriptFile, String serversFile, List`1 variableFiles, Int32& exitCode)
[Generic: Error] [6156/3] [2013-02-04 12:53:04]: Exception: The remote server returned an error: (407) Proxy Authentication Required.
 site: System.Net.WebResponse GetResponse()
 source: System
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.SSMA.Framework.Generic.SQM.SqmFileUploader.DoUpload()
[Generic: Error] [6156/1] [2013-02-04 12:53:05]: Exception: The remote server returned an error: (407) Proxy Authentication Required.
 site: System.Net.WebResponse GetResponse()
 source: System
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.SSMA.Framework.Generic.SQM.SqmFileUploader.DoUpload()

System Specs:

Windows 7 (64 bit)

Microsoft Office 2010

Microsoft SQL Server 2008

Microsoft SQL Server Migration Assistant v5.2.1257

If you need any further information I will gladly supply it.

All tips, help, and assistance are appreciated.

Thank you for your valued time.

Akshay Pate

I wants to convert the firebird data into MS SQL Sever 2008 R2 data.Because my old data are in firebird my system how moved on to SQL Server 2008 R2. Any Migration techniques are available to it with ease . I don't want any  third party software to do that.

Thanks in advance.

Hiall,

I have migrated the llinked server(copied the script and executed on new server 2012) but the issue is when I try to retrive data this error has been thrown

OLE DB provider "SQLNCLI11" for linked server "BroraDb" returned message "Client unable to establish connection".

Msg 22, Level 16, State 1, Line 0
SQL Server Native Client 11.0 does not support connections to SQL Server 2000 or earlier versions.

please let me know If there is any other possible way to transfer the linked servers.