Hi, I am looking for a way to transfer data from sql server to sql server ce. I am using sql server management studio express wich has no export/import wizard. How can I accomplish this task? are there any tools available? thanks
I have developed a set of tools that can help you with this. Please note that 3.5 is not supported yet.|||Thanks! I will check it out!
|||Jo?o, I have tried your tools. But when i try to run it it says it can't open the device database. I want to export the sql 2005 database to a .sdf file. When I check the 'local' checkbox I still get the same error.
Is there any other way to port sql ce databases to sql server?
|||You must install SQL Compact Edition 3.1 on your desktop in order to use the "Local" checkbox.|||Great! it works! thanks. Does it also migrate foreign keys to sql ce?
|||It migrates PRIMARY KEY and FOREIGN KEY constraints. UNIQUE constraints are not migrated (they may show up as UNIQUE INDEX) nor are column defaults (due to the SQL language difference between engines, especially Access). IDENTITY columns are correctly migrated.
Showing posts with label transfer. Show all posts
Showing posts with label transfer. Show all posts
Wednesday, March 28, 2012
Migrating data from sql server to sql server ce
Hi, I am looking for a way to transfer data from sql server to sql server ce. I am using sql server management studio express wich has no export/import wizard. How can I accomplish this task? are there any tools available? thanks
I have developed a set of tools that can help you with this. Please note that 3.5 is not supported yet.|||Thanks! I will check it out!
|||Jo?o, I have tried your tools. But when i try to run it it says it can't open the device database. I want to export the sql 2005 database to a .sdf file. When I check the 'local' checkbox I still get the same error.
Is there any other way to port sql ce databases to sql server?
|||You must install SQL Compact Edition 3.1 on your desktop in order to use the "Local" checkbox.|||Great! it works! thanks. Does it also migrate foreign keys to sql ce?
|||It migrates PRIMARY KEY and FOREIGN KEY constraints. UNIQUE constraints are not migrated (they may show up as UNIQUE INDEX) nor are column defaults (due to the SQL language difference between engines, especially Access). IDENTITY columns are correctly migrated.sql
I have developed a set of tools that can help you with this. Please note that 3.5 is not supported yet.|||Thanks! I will check it out!
|||Jo?o, I have tried your tools. But when i try to run it it says it can't open the device database. I want to export the sql 2005 database to a .sdf file. When I check the 'local' checkbox I still get the same error.
Is there any other way to port sql ce databases to sql server?
|||You must install SQL Compact Edition 3.1 on your desktop in order to use the "Local" checkbox.|||Great! it works! thanks. Does it also migrate foreign keys to sql ce?
|||It migrates PRIMARY KEY and FOREIGN KEY constraints. UNIQUE constraints are not migrated (they may show up as UNIQUE INDEX) nor are column defaults (due to the SQL language difference between engines, especially Access). IDENTITY columns are correctly migrated.sql
Monday, March 26, 2012
Migrate w/o upgrade wizard
Hello,
I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
Upgrade Wizard's named pipe transfer to work in two server environment
(one of them is the latest WinNT4 and the other - the latest Win2K).
I've simply lost my patience reading white papers and trying to get it
running. So now I'm thinking of doing w/o it.
I think the easiest way would be to: (1) install a replica of original
6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
machine upgrade (using wizard), (3) from the spare SQL2K transfer master
and msdb stuff and new DB's to a production SQL2K.
This approach might be inept though. What would be the best/tested way
to go?
Many thanks,
Pablo
Hi,
Yes, I agree with your approach. But I suggest you to do the activity in
your SQL 6.5 machine itself. Because the SQL 2000 installing will not
touch/tamper SQL 2000. This will be a totally new copy.
Steps
1. Install SQL 2000 and sp3a in the SQL 6.5 machine, provided you have
enough space in hard disk to do upgrade
(We should have atleast 1.5 times data space in SQL 6.5)
2. Run the upgrade wizard on all system and required user databases
3. Once the upgrade is successful , you can move all the SQL 2000 databases
to New machine with SQL 2000 and SP3a.
4. Once the SQL 2000 is up in new Server, Change the SQL server name using
SP_DROPSERVER <Old_Server_name>
and SP_ADDSERVER <Server>,LOCAL
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_email.cc> wrote in message
news:uEf0aF8KEHA.620@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
> Upgrade Wizard's named pipe transfer to work in two server environment
> (one of them is the latest WinNT4 and the other - the latest Win2K).
> I've simply lost my patience reading white papers and trying to get it
> running. So now I'm thinking of doing w/o it.
> I think the easiest way would be to: (1) install a replica of original
> 6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
> machine upgrade (using wizard), (3) from the spare SQL2K transfer master
> and msdb stuff and new DB's to a production SQL2K.
> This approach might be inept though. What would be the best/tested way
> to go?
> --
> Many thanks,
> Pablo
>
I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
Upgrade Wizard's named pipe transfer to work in two server environment
(one of them is the latest WinNT4 and the other - the latest Win2K).
I've simply lost my patience reading white papers and trying to get it
running. So now I'm thinking of doing w/o it.
I think the easiest way would be to: (1) install a replica of original
6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
machine upgrade (using wizard), (3) from the spare SQL2K transfer master
and msdb stuff and new DB's to a production SQL2K.
This approach might be inept though. What would be the best/tested way
to go?
Many thanks,
Pablo
Hi,
Yes, I agree with your approach. But I suggest you to do the activity in
your SQL 6.5 machine itself. Because the SQL 2000 installing will not
touch/tamper SQL 2000. This will be a totally new copy.
Steps
1. Install SQL 2000 and sp3a in the SQL 6.5 machine, provided you have
enough space in hard disk to do upgrade
(We should have atleast 1.5 times data space in SQL 6.5)
2. Run the upgrade wizard on all system and required user databases
3. Once the upgrade is successful , you can move all the SQL 2000 databases
to New machine with SQL 2000 and SP3a.
4. Once the SQL 2000 is up in new Server, Change the SQL server name using
SP_DROPSERVER <Old_Server_name>
and SP_ADDSERVER <Server>,LOCAL
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_email.cc> wrote in message
news:uEf0aF8KEHA.620@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
> Upgrade Wizard's named pipe transfer to work in two server environment
> (one of them is the latest WinNT4 and the other - the latest Win2K).
> I've simply lost my patience reading white papers and trying to get it
> running. So now I'm thinking of doing w/o it.
> I think the easiest way would be to: (1) install a replica of original
> 6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
> machine upgrade (using wizard), (3) from the spare SQL2K transfer master
> and msdb stuff and new DB's to a production SQL2K.
> This approach might be inept though. What would be the best/tested way
> to go?
> --
> Many thanks,
> Pablo
>
Migrate w/o upgrade wizard
Hello,
I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
Upgrade Wizard's named pipe transfer to work in two server environment
(one of them is the latest WinNT4 and the other - the latest Win2K).
I've simply lost my patience reading white papers and trying to get it
running. So now I'm thinking of doing w/o it.
I think the easiest way would be to: (1) install a replica of original
6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
machine upgrade (using wizard), (3) from the spare SQL2K transfer master
and msdb stuff and new DB's to a production SQL2K.
This approach might be inept though. What would be the best/tested way
to go?
--
Many thanks,
PabloHi,
Yes, I agree with your approach. But I suggest you to do the activity in
your SQL 6.5 machine itself. Because the SQL 2000 installing will not
touch/tamper SQL 2000. This will be a totally new copy.
Steps
1. Install SQL 2000 and sp3a in the SQL 6.5 machine, provided you have
enough space in hard disk to do upgrade
(We should have atleast 1.5 times data space in SQL 6.5)
2. Run the upgrade wizard on all system and required user databases
3. Once the upgrade is successful , you can move all the SQL 2000 databases
to New machine with SQL 2000 and SP3a.
4. Once the SQL 2000 is up in new Server, Change the SQL server name using
SP_DROPSERVER <Old_Server_name>
and SP_ADDSERVER <Server>,LOCAL
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_email.cc> wrote in message
news:uEf0aF8KEHA.620@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
> Upgrade Wizard's named pipe transfer to work in two server environment
> (one of them is the latest WinNT4 and the other - the latest Win2K).
> I've simply lost my patience reading white papers and trying to get it
> running. So now I'm thinking of doing w/o it.
> I think the easiest way would be to: (1) install a replica of original
> 6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
> machine upgrade (using wizard), (3) from the spare SQL2K transfer master
> and msdb stuff and new DB's to a production SQL2K.
> This approach might be inept though. What would be the best/tested way
> to go?
> --
> Many thanks,
> Pablo
>
I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
Upgrade Wizard's named pipe transfer to work in two server environment
(one of them is the latest WinNT4 and the other - the latest Win2K).
I've simply lost my patience reading white papers and trying to get it
running. So now I'm thinking of doing w/o it.
I think the easiest way would be to: (1) install a replica of original
6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
machine upgrade (using wizard), (3) from the spare SQL2K transfer master
and msdb stuff and new DB's to a production SQL2K.
This approach might be inept though. What would be the best/tested way
to go?
--
Many thanks,
PabloHi,
Yes, I agree with your approach. But I suggest you to do the activity in
your SQL 6.5 machine itself. Because the SQL 2000 installing will not
touch/tamper SQL 2000. This will be a totally new copy.
Steps
1. Install SQL 2000 and sp3a in the SQL 6.5 machine, provided you have
enough space in hard disk to do upgrade
(We should have atleast 1.5 times data space in SQL 6.5)
2. Run the upgrade wizard on all system and required user databases
3. Once the upgrade is successful , you can move all the SQL 2000 databases
to New machine with SQL 2000 and SP3a.
4. Once the SQL 2000 is up in new Server, Change the SQL server name using
SP_DROPSERVER <Old_Server_name>
and SP_ADDSERVER <Server>,LOCAL
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_email.cc> wrote in message
news:uEf0aF8KEHA.620@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
> Upgrade Wizard's named pipe transfer to work in two server environment
> (one of them is the latest WinNT4 and the other - the latest Win2K).
> I've simply lost my patience reading white papers and trying to get it
> running. So now I'm thinking of doing w/o it.
> I think the easiest way would be to: (1) install a replica of original
> 6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
> machine upgrade (using wizard), (3) from the spare SQL2K transfer master
> and msdb stuff and new DB's to a production SQL2K.
> This approach might be inept though. What would be the best/tested way
> to go?
> --
> Many thanks,
> Pablo
>
Migrate w/o upgrade wizard
Hello,
I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
Upgrade Wizard's named pipe transfer to work in two server environment
(one of them is the latest WinNT4 and the other - the latest Win2K).
I've simply lost my patience reading white papers and trying to get it
running. So now I'm thinking of doing w/o it.
I think the easiest way would be to: (1) install a replica of original
6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
machine upgrade (using wizard), (3) from the spare SQL2K transfer master
and msdb stuff and new DB's to a production SQL2K.
This approach might be inept though. What would be the best/tested way
to go?
Many thanks,
PabloHi,
Yes, I agree with your approach. But I suggest you to do the activity in
your SQL 6.5 machine itself. Because the SQL 2000 installing will not
touch/tamper SQL 2000. This will be a totally new copy.
Steps
1. Install SQL 2000 and sp3a in the SQL 6.5 machine, provided you have
enough space in hard disk to do upgrade
(We should have atleast 1.5 times data space in SQL 6.5)
2. Run the upgrade wizard on all system and required user databases
3. Once the upgrade is successful , you can move all the SQL 2000 databases
to New machine with SQL 2000 and SP3a.
4. Once the SQL 2000 is up in new Server, Change the SQL server name using
SP_DROPSERVER <Old_Server_name>
and SP_ADDSERVER <Server>,LOCAL
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_email.cc> wrote in message
news:uEf0aF8KEHA.620@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
> Upgrade Wizard's named pipe transfer to work in two server environment
> (one of them is the latest WinNT4 and the other - the latest Win2K).
> I've simply lost my patience reading white papers and trying to get it
> running. So now I'm thinking of doing w/o it.
> I think the easiest way would be to: (1) install a replica of original
> 6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
> machine upgrade (using wizard), (3) from the spare SQL2K transfer master
> and msdb stuff and new DB's to a production SQL2K.
> This approach might be inept though. What would be the best/tested way
> to go?
> --
> Many thanks,
> Pablo
>sql
I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
Upgrade Wizard's named pipe transfer to work in two server environment
(one of them is the latest WinNT4 and the other - the latest Win2K).
I've simply lost my patience reading white papers and trying to get it
running. So now I'm thinking of doing w/o it.
I think the easiest way would be to: (1) install a replica of original
6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
machine upgrade (using wizard), (3) from the spare SQL2K transfer master
and msdb stuff and new DB's to a production SQL2K.
This approach might be inept though. What would be the best/tested way
to go?
Many thanks,
PabloHi,
Yes, I agree with your approach. But I suggest you to do the activity in
your SQL 6.5 machine itself. Because the SQL 2000 installing will not
touch/tamper SQL 2000. This will be a totally new copy.
Steps
1. Install SQL 2000 and sp3a in the SQL 6.5 machine, provided you have
enough space in hard disk to do upgrade
(We should have atleast 1.5 times data space in SQL 6.5)
2. Run the upgrade wizard on all system and required user databases
3. Once the upgrade is successful , you can move all the SQL 2000 databases
to New machine with SQL 2000 and SP3a.
4. Once the SQL 2000 is up in new Server, Change the SQL server name using
SP_DROPSERVER <Old_Server_name>
and SP_ADDSERVER <Server>,LOCAL
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_email.cc> wrote in message
news:uEf0aF8KEHA.620@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I want to migrate my 6.5 DBs to SQL2K. Problem is that I can't get the
> Upgrade Wizard's named pipe transfer to work in two server environment
> (one of them is the latest WinNT4 and the other - the latest Win2K).
> I've simply lost my patience reading white papers and trying to get it
> running. So now I'm thinking of doing w/o it.
> I think the easiest way would be to: (1) install a replica of original
> 6.5 on a spare server along with a fresh copy of SQL2K, (2) do a single
> machine upgrade (using wizard), (3) from the spare SQL2K transfer master
> and msdb stuff and new DB's to a production SQL2K.
> This approach might be inept though. What would be the best/tested way
> to go?
> --
> Many thanks,
> Pablo
>sql
Monday, March 19, 2012
Migrate from ingres to SqlServer
I was given a project from my supervisor and i must complete it until Tuesday. I must transfer our ingres database into sql server database. So far i have done all the work with the tables, primary keys, views and data. I don’t know how to go on with the procedures and rules that i have to transfer. Is there anyone that had faced the same condition? What should i do?
Maria
I'm not aware of any easy way to do this, the SqlServer migration tools don't cover Ingres (see http://www.microsoft.com/sql/solutions/migration/default.mspx for what they do cover) so it may be that you just have to rewrite it all
. Maybe someone else knows more? It's quite a few years since I last used Ingres and things may have changed.
Monday, March 12, 2012
Migrate
I have developed a web application using MSDE. I do not have sql 2000. I now have to transfer this database to an asp host.
Is there a DTS package or osql commands that I can export the entire database sp and all to a sql script file.
Is there a DTS package or osql commands that I can export the entire database sp and all to a sql script file.
Regards
S(:You can create scripts for all of the database objects (tables, view, sprocs, etc.) but I don't believe you can create scripts for the data too. You can use DTS to copy the data, however, after you create the objects.
I haven't tried this with MSDE but with Sql Server databases you can detach them from your local database and physically copy the database files to the remote destination and then re-attach them there. The database has to be compatible with where you are attaching it and whether it considers MSDE files compatible is the question.
Subscribe to:
Posts (Atom)