SSMA Migration to Master

[Guest]

I've used the SSMA on two different machines, having good luck on one and not
on the other. The problem I'm having is that on my so successful machine, the
migration went to the proper SQL Server Database. On my unsuccessful machine,
the migration keeps going to the Master database, not the correct database.
I've got the Master un-selected and the new database selected.

I don't see why this is happening?

 

[privatenews]

Hello Elad,

I understand that you want to install client tools of SQL server 2005 on
workstation so that you could manage SQL Server from the client. If I'm
off-base, please let me know.

After consulting SBS engineers, they said there is setup CD for SQL 2005
included in SBS R2 Primier package (it is supposed to be CD2). You could
run setup program directly from the setup CD, and select to install "client
components" including connectivity components, management studio etc on
your clients.

It is not possible to just copy installed files on server to client to make
it works properly on client machines.

If anything is unclear or you have further questions on this, please feel
free to let's know. We look forward to your reply.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Sylvain Lafontaine]

You should post your question in the m.p.a.sqlupsizing newsgroup.

Did you apply the latest service pack to the second instance of SQL-Server?

One possibility could be that the logon that you are using doesn't have
sufficient rights to access the correct database on the second machine.

 

[privatenews]

Hello,

Sorry for the previous reply since it is for another thread.

I understand migration went to master database when you try to use SSMS for
Access on a specific machine. If it isn't correct, please let me know.

Based on my test, this issue could occur if the target schema is configured
to master in your project. You may want to try the following steps to
troubleshoot the issue:

1. Create a new project. Add the Access database you want to migrate

2. Click "Connect to server" toolbar, select the server you want, and
choose the database you want to migrate to, for example "mytest".

3. On the right panel, you shall see "target schema" is changed to
"mytest.dbo". If not, please click Modify, and select the proper database
and schema inside.

4. Try to convert the schema of the source Access database to destination
by right click the Access database->Convert Schema

5. Under the SQL Server node, select the SQL database you configured, and
right click the entry->Load to database

6. Right click the Access database ->Migrate data.

If anything is unclear, please feel free to let's know.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support



======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

 

[Guest]

I've got the transfer working properly now.

At the original successful machine, when connectiong to SQL Server I
selected the SQL Database name at that time and SSMA worked properly.

On my unsuccessful machine, the Database Listing did not dislay the database
I wanted to us, so I just connected to my Server with no database selected,
and then selected the database "after" connecting in the "SQL Server Metadata
Explorer" window. Apparently, selecting the SQL Server in this window does
not work.

Plus, only my tables are converting. None of my Queries are converting. All
I can tell there is that my queries are not converting because I have defined
"PARAMETERS" in all of my queries. One would think a simple Select statement
with a filter/parameter creiteria would also convert, but it does not. This
means I have to manually recreate 300+ queries. That is going to be a
daunting task, unless there is a workaround.

Any suggestions on that one?

Thanks.

 

[privatenews]

Hello,

I understand the original issue is resolved and I noticed another thread on
parameters queries you submitted. And Gil Lapid has mentioned query
upsizing is top priority for the next release of SSMA (10/30), and current
version has limitation on this feature. I apprciate your understanding and
patience.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


=====================================================


This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================