Using the migration wizard on 6.1 CE. To login I am using a native sql account I had the DBA set up. I am trying to migrate a database from and instance of SQL Server 2012 (not local).
The good news... following the "How to" I am able to successfully connect to our SQL server instance. I am (of course) also able to make a connection to my local instance of MySQL.
The first time through, I left the SQL Server database field blank as suggested by the How to. But no schema were listed. So, I went back to the SQL Server connection set up and specifically listed the database I wanted to migrate.
Then I re-tested the connection and again got confirmation that the connection was good.
Proceeding on, I got the warning below...
-- BEGIN SNIPPED WARNING ----------------------------------------------------
Starting...
Connect to source DBMS...
- Connecting to source...
Connecting to Mssql@DRIVER=SQL Server Native Client 11.0;SERVER=SJDWDEV,1433...
Opening ODBC connection to DRIVER={SQL Server Native Client 11.0};SERVER=SJDWDEV,1433;DATABASE={Data_Warehouse_SJ_Staging};UID=mysql;PWD=XXXX;...
Connected to Mssql@DRIVER=SQL Server Native Client 11.0;SERVER=SJDWDEV,1433, 11.0.3128.0
Connect to source DBMS done
Check target DBMS connection...
- Connecting to target...
Check target DBMS connection done
Retrieve schema list from source....
- Checking connection...
- Fetching catalog names...
WARNING: The following catalogs where not found: Data_Warehouse_SJ_Staging
- Fetching schema names...
- Finished
Retrieve schema list from source finished
Tasks finished with warnings and/or errors, view the logs for details
Finished performing tasks.
-- END SNIPPED WARNING ------------------------------------------------------
I am only making an educated guess here, but I suspect that my login account lacks the privileges that might be needed for the migration wizard?
Otherwise I cannot fathom why the migration wizard isn't picking up the database.
The account I asked the DBA to set up has privileges to connect to the server, login to the database (I have tested using this account on SMSS to login to SQL server and I can do so; further validation that the login account can indeed connect to the SQL Server instance).
However, I only asked for SELECT permissions for the account and am wondering if this might be the problem?
If so, can someone tell me what permissions are needed for this account in order
for the migration wizard to successfully read the database and list the schema?
Additionally, I have found out the hard way that sometimes, depending on what is going on behind the scenes, an account may need connection privileges to other databases - perhaps system databases such as 'master' or 'msdb'? Could this be an issue as well? Does the migration wizard need privileges on any of the system databases in SQL Server?
If permissions is not the issue, can someone explain why I can connect successfully to my SQL Server 2012 instance, but then the wizard cannot: a) read any of the databases on the instance (when database is left blank); b) read the specific database on the instance when it is explicitly spelled out?
Thanks very much in advance
Randy Volters
The good news... following the "How to" I am able to successfully connect to our SQL server instance. I am (of course) also able to make a connection to my local instance of MySQL.
The first time through, I left the SQL Server database field blank as suggested by the How to. But no schema were listed. So, I went back to the SQL Server connection set up and specifically listed the database I wanted to migrate.
Then I re-tested the connection and again got confirmation that the connection was good.
Proceeding on, I got the warning below...
-- BEGIN SNIPPED WARNING ----------------------------------------------------
Starting...
Connect to source DBMS...
- Connecting to source...
Connecting to Mssql@DRIVER=SQL Server Native Client 11.0;SERVER=SJDWDEV,1433...
Opening ODBC connection to DRIVER={SQL Server Native Client 11.0};SERVER=SJDWDEV,1433;DATABASE={Data_Warehouse_SJ_Staging};UID=mysql;PWD=XXXX;...
Connected to Mssql@DRIVER=SQL Server Native Client 11.0;SERVER=SJDWDEV,1433, 11.0.3128.0
Connect to source DBMS done
Check target DBMS connection...
- Connecting to target...
Check target DBMS connection done
Retrieve schema list from source....
- Checking connection...
- Fetching catalog names...
WARNING: The following catalogs where not found: Data_Warehouse_SJ_Staging
- Fetching schema names...
- Finished
Retrieve schema list from source finished
Tasks finished with warnings and/or errors, view the logs for details
Finished performing tasks.
-- END SNIPPED WARNING ------------------------------------------------------
I am only making an educated guess here, but I suspect that my login account lacks the privileges that might be needed for the migration wizard?
Otherwise I cannot fathom why the migration wizard isn't picking up the database.
The account I asked the DBA to set up has privileges to connect to the server, login to the database (I have tested using this account on SMSS to login to SQL server and I can do so; further validation that the login account can indeed connect to the SQL Server instance).
However, I only asked for SELECT permissions for the account and am wondering if this might be the problem?
If so, can someone tell me what permissions are needed for this account in order
for the migration wizard to successfully read the database and list the schema?
Additionally, I have found out the hard way that sometimes, depending on what is going on behind the scenes, an account may need connection privileges to other databases - perhaps system databases such as 'master' or 'msdb'? Could this be an issue as well? Does the migration wizard need privileges on any of the system databases in SQL Server?
If permissions is not the issue, can someone explain why I can connect successfully to my SQL Server 2012 instance, but then the wizard cannot: a) read any of the databases on the instance (when database is left blank); b) read the specific database on the instance when it is explicitly spelled out?
Thanks very much in advance
Randy Volters