Showing posts with label import. Show all posts
Showing posts with label import. Show all posts

Wednesday, March 7, 2012

Migration from SQL Server Enterprise Edition to SQL Express Edition 2005

Hi, I'm trying to import databases in sqlexpress edition 2005 from sql
enterprise edition. Any Idea? thank in advance
Backup and restore. Just be aware of the DB size limit of Express, namely
4GB.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"luca drink" <luca.bevilacqua@.gmail.com> wrote in message
news:1134147824.493604.266210@.g43g2000cwa.googlegr oups.com...
> Hi, I'm trying to import databases in sqlexpress edition 2005 from sql
> enterprise edition. Any Idea? thank in advance
>

Migration from SQL Server Enterprise Edition to SQL Express Edition 2005

Hi, I'm trying to import databases in sqlexpress edition 2005 from sql
enterprise edition. Any Idea? thank in advanceHi
I would expect this to work are you having problems?
John
"luca drink" wrote:
> Hi, I'm trying to import databases in sqlexpress edition 2005 from sql
> enterprise edition. Any Idea? thank in advance
>|||Backup and restore. Just be aware of the DB size limit of Express, namely
4GB.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"luca drink" <luca.bevilacqua@.gmail.com> wrote in message
news:1134147824.493604.266210@.g43g2000cwa.googlegroups.com...
> Hi, I'm trying to import databases in sqlexpress edition 2005 from sql
> enterprise edition. Any Idea? thank in advance
>

Migration from SQL Server Enterprise Edition to SQL Express Edition 2005

Hi, I'm trying to import databases in sqlexpress edition 2005 from sql
enterprise edition. Any Idea? thank in advanceBackup and restore. Just be aware of the DB size limit of Express, namely
4GB.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"luca drink" <luca.bevilacqua@.gmail.com> wrote in message
news:1134147824.493604.266210@.g43g2000cwa.googlegroups.com...
> Hi, I'm trying to import databases in sqlexpress edition 2005 from sql
> enterprise edition. Any Idea? thank in advance
>

Migration from Oracle 7.34 to SQL 2000

I'm attempting to move a database which currently exists on an old Oracle
7.34 instance and tried to use Data Import via DTS to SQL 2000.
The Oracle database consists of views, indexes,packages,triggers as well as
tables structures. I tried DTS using both the ODBC and OLE for Oracle and
only tables and data came over correctly.
Views it appears were converted into tables. Indexes not at all.
I'm using the Oracle 9.2 client on my workstation.
Any ideas on how I might be able to convert this database over from Oracle?
thks
You'll have to move the code, views, etc manually
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jack Snow" <mrbrew5510@.hotmail.com> wrote in message
news:tea_c.4190$lv3.2047604@.news4.srv.hcvlny.cv.ne t...
> I'm attempting to move a database which currently exists on an old Oracle
> 7.34 instance and tried to use Data Import via DTS to SQL 2000.
> The Oracle database consists of views, indexes,packages,triggers as well
as
> tables structures. I tried DTS using both the ODBC and OLE for Oracle and
> only tables and data came over correctly.
> Views it appears were converted into tables. Indexes not at all.
> I'm using the Oracle 9.2 client on my workstation.
> Any ideas on how I might be able to convert this database over from
Oracle?
>
> thks
>

Saturday, February 25, 2012

Migration from Oracle 7.34 to SQL 2000

I'm attempting to move a database which currently exists on an old Oracle
7.34 instance and tried to use Data Import via DTS to SQL 2000.
The Oracle database consists of views, indexes,packages,triggers as well as
tables structures. I tried DTS using both the ODBC and OLE for Oracle and
only tables and data came over correctly.
Views it appears were converted into tables. Indexes not at all.
I'm using the Oracle 9.2 client on my workstation.
Any ideas on how I might be able to convert this database over from Oracle?
thksYou'll have to move the code, views, etc manually
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jack Snow" <mrbrew5510@.hotmail.com> wrote in message
news:tea_c.4190$lv3.2047604@.news4.srv.hcvlny.cv.net...
> I'm attempting to move a database which currently exists on an old Oracle
> 7.34 instance and tried to use Data Import via DTS to SQL 2000.
> The Oracle database consists of views, indexes,packages,triggers as well
as
> tables structures. I tried DTS using both the ODBC and OLE for Oracle and
> only tables and data came over correctly.
> Views it appears were converted into tables. Indexes not at all.
> I'm using the Oracle 9.2 client on my workstation.
> Any ideas on how I might be able to convert this database over from
Oracle?
>
> thks
>

Migration from Access to Sql Server

Hi, I import my tables from Access to SQl Server 2000
actually MSDE with the SQL server tools.

Is there a way to have the same table name as in access
because in SQl server it seems I have to call my
tables that way : testdb.dbo.po instead of just po in VB access.
That means changing all my Querys :(

Also I installed sql server on 1 PC (WinXp Pro) on my network and install the client
tools on another PC (Win98) but how can I access SQL Server from that PC?
When I'm in VB and do a connection with the ADO object I don't get
any server listed in it??
My connection string use on my local PC with server on it is working fine.

StrSqlSrv = "Provider=SQLOLEDB.1;Integrated Security=SSPI;" & _
"Persist Security Info=False;Initial Catalog=imdedi;" & _
"Data Source=" & servername

Also Is it possible to package (With VB package) a program using MSDE so that it will
install MSDE and create all tables on the client PC?

Can DAO connects to sql server?

Thank you. I know... alot of questions :)> That means changing all my Querys :(

no it doesn't. try it. you can use

databasename.username.tablename

or just

tablename|||Hi, this is my connections that work fine with ADO
The only thing I do is changing the ConnectionString to my Sql Server
To make it work I have to use the .dbo thing....
This works ->> testdb.dbo.company

company.ConnectionString = StrSqlSrv
company.RecordSource = "SELECT compno,compname,telno FROM company ORDER BY compno;"

company.Refresh

Here is the error I get
A message box display Invalif Object Name company
When I click OK then
a run-time error"
(80040e37) Method 'Refresh' of Object 'IAdodc' failed|||Hi, I was able to access my tables without the .dbo
I was missing a user...

Migration ACCESS --> SQL date field

Hi,
I import an access table with date field in SQL with DTS import/export
wizard.
I got error : data overflow on date field. There is another way to do it ?In the DTS package, transform that column to varchar, and then run isdate()
against the new table to determine which rows need to be repaired.
"Sylvain Provencher" <sylvain.provencher@.nobelia.com> wrote in message
news:uZybbSLpDHA.2268@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I import an access table with date field in SQL with DTS import/export
> wizard.
> I got error : data overflow on date field. There is another way to do it ?
>

Monday, February 20, 2012

Migrating to 2005

Im trying to move from a 2000 server to 2005 server. However when I try to d
o
the import there is no option for selecting UDF's or stored procedures, just
tables and views...is there a way to get these over?..thanks
-JimI would detach the database(s) and then attach it on the 2005 instance, or
use backup/restore unless you have a specific reason for
exporting/importing.
See the Books Online topic "How to: Upgrade a Database Using Detach and
Attach (Transact-SQL) " for more info if you need it.
--
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Jim" <Jim@.discussions.microsoft.com> wrote in message
news:693C6609-EA67-4130-8EF8-024FD5318AAC@.microsoft.com...
> Im trying to move from a 2000 server to 2005 server. However when I try to
> do
> the import there is no option for selecting UDF's or stored procedures,
> just
> tables and views...is there a way to get these over?..thanks
> -Jim

Migrating Sybase to SQL Server 2000

I'm currently involving in a project in migrating from
Sybase to SQL Server 2000. I've been able to
successfully (and conveniently) import my tables/data.
My question involves the Stored Procedures. Can these
stored procedures be import w/ a wizard (i.e. the way my
tables/data have been converted)? Or must I manually
create new SP's in SQL Server, making the necessary
changes (Rollback trigger, transaction isolation levels,
etc.) on the fly?
I think that you must to do the necessary changes.
The sybase code is not totally compatible with sql2k.
After this forget sybase, please.
<anonymous@.discussions.microsoft.com> escreveu na mensagem
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?
|||Hi,
Have a look into the below article from MS:-
http://www.microsoft.com/resources/d...reskit/en-us/p
art2/c0661.mspx
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?
|||Yes, you must make the changes manually, but there should not be a whole lot
of changes...They are doc'd in the article mentioned previously.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?

Migrating Sybase to SQL Server 2000

I'm currently involving in a project in migrating from
Sybase to SQL Server 2000. I've been able to
successfully (and conveniently) import my tables/data.
My question involves the Stored Procedures. Can these
stored procedures be import w/ a wizard (i.e. the way my
tables/data have been converted)? Or must I manually
create new SP's in SQL Server, making the necessary
changes (Rollback trigger, transaction isolation levels,
etc.) on the fly?I think that you must to do the necessary changes.
The sybase code is not totally compatible with sql2k.
After this forget sybase, please.
<anonymous@.discussions.microsoft.com> escreveu na mensagem
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?|||Hi,
Have a look into the below article from MS:-
http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/p
art2/c0661.mspx
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?|||Yes, you must make the changes manually, but there should not be a whole lot
of changes...They are doc'd in the article mentioned previously.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?

Migrating Sybase to SQL Server 2000

I'm currently involving in a project in migrating from
Sybase to SQL Server 2000. I've been able to
successfully (and conveniently) import my tables/data.
My question involves the Stored Procedures. Can these
stored procedures be import w/ a wizard (i.e. the way my
tables/data have been converted)? Or must I manually
create new SP's in SQL Server, making the necessary
changes (Rollback trigger, transaction isolation levels,
etc.) on the fly?I think that you must to do the necessary changes.
The sybase code is not totally compatible with sql2k.
After this forget sybase, please.
<anonymous@.discussions.microsoft.com> escreveu na mensagem
news:16a0801c4481a$7b9a8410$a401280a@.phx
.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?|||Hi,
Have a look into the below article from MS:-
http://www.microsoft.com/resources/.../reskit/en-us/p
art2/c0661.mspx
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx
.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?|||Yes, you must make the changes manually, but there should not be a whole lot
of changes...They are doc'd in the article mentioned previously.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx
.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?