Importing or attaching a database

I had to reinstall sql7 and I now need to access my old
database. It is in the mssql7 data directory, but it does
not show up under enterprise manager. Is there a way
to "import" it?
Thanks for any helpTry using sp_attach_db. See SQL Server Books Online for more information on
this procedure, and examples.
--
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"GB" <anonymous@.discussions.microsoft.com> wrote in message
news:2aa3f01c465ec$74153290$a301280a@.phx.gbl...
> I had to reinstall sql7 and I now need to access my old
> database. It is in the mssql7 data directory, but it does
> not show up under enterprise manager. Is there a way
> to "import" it?
> Thanks for any help

Importing old data into asp_tables...?

I have created an application that uses the login, create, etc login components in .net. How hard is it to convert all my old users, passwords, usertypes into the new tables. It almost looks like I have to do them by hand and created a new guid(userid), along with the same guid in the aspnet_usersinroles and aspnet_Membership. Is there a script to do this programatically?

Hi,

You can use t-sql cursor to go record by record thru your old table and inserting to asp.net tables. The difficult part is passwords. I think it would be too difficult to decode and encode password in t-sql.

So, probably first import data and then use asp.net to re-encode passwords. As far as I know there are no utilities to do it automatically.

Importing ISAM data into SQLServer

Hello,
My company has some old ISAM datasets we need to resuscitate. We
would like to import the data into SQLServer. It looks like there are
some ISAM ODBC drivers available, but I was wondering how well it
works.
There would seem to be a step where you have to specify how the input
record is parsed into SQLServer columns. Is this easier in some
drivers than other?
Any input from people who have gone through this exercise would be
appreciated.
Bart
There are different types of ISAM files so it all depends.
The drivers can make a big difference in performance, ease
of use, etc.whenever you work with any other flavors of data
sources. I've done some that have been straightforward and
pretty easy. I've done others that have been painful. Most
of the vendors will give you trial versions - that's usually
the best way to find out what's going to work best for your
needs.
-Sue
On 8 May 2007 14:16:17 -0700, barthome1@.comcast.net wrote:

>Hello,
>My company has some old ISAM datasets we need to resuscitate. We
>would like to import the data into SQLServer. It looks like there are
>some ISAM ODBC drivers available, but I was wondering how well it
>works.
>There would seem to be a step where you have to specify how the input
>record is parsed into SQLServer columns. Is this easier in some
>drivers than other?
>Any input from people who have gone through this exercise would be
>appreciated.
>Bart

Importing ISAM data into SQLServer

Hello,
My company has some old ISAM datasets we need to resuscitate. We
would like to import the data into SQLServer. It looks like there are
some ISAM ODBC drivers available, but I was wondering how well it
works.
There would seem to be a step where you have to specify how the input
record is parsed into SQLServer columns. Is this easier in some
drivers than other?
Any input from people who have gone through this exercise would be
appreciated.
BartThere are different types of ISAM files so it all depends.
The drivers can make a big difference in performance, ease
of use, etc.whenever you work with any other flavors of data
sources. I've done some that have been straightforward and
pretty easy. I've done others that have been painful. Most
of the vendors will give you trial versions - that's usually
the best way to find out what's going to work best for your
needs.
-Sue
On 8 May 2007 14:16:17 -0700, barthome1@.comcast.net wrote:

>Hello,
>My company has some old ISAM datasets we need to resuscitate. We
>would like to import the data into SQLServer. It looks like there are
>some ISAM ODBC drivers available, but I was wondering how well it
>works.
>There would seem to be a step where you have to specify how the input
>record is parsed into SQLServer columns. Is this easier in some
>drivers than other?
>Any input from people who have gone through this exercise would be
>appreciated.
>Bartsql

Importing data into SQL

With SQL 2000 there was an Import/Export facility for importing data into a Sql database. Could somebody tell me how to import an old database which could be in Csv text or Paradox into my new SQL 2005 tables. Thanks

In Management Studio, connect to any sql server instance, right-click on a database > tasks > import data

This will take you do the import/export wizard

|||

Start -> Run -> dtswizard.exe will also bring up the Import Export Wizard for you.

Importing data from Btrieve to SQL - Migrating data to new SQL ser

I have an old Btrieve database written by some programmer in the distant
past. It's currently running on an old 3.11 novell server. That applictation
being updated every day.
I need to get that data out of the old Btrieve DB and into a new SQL
database.
What an easy way (tool) to migrate this data over into one or more SQL tables?
thanks
Jim
You will need the DDF files if you do not already have them to use
ODBC. If you need to build these you can take a look at BtSearch32 at
www.nssdd.com. It helps you analyze the structure and build the DDF
files. It will also export to dbase or ascii formats.
Gil

Importing data from Btrieve to SQL - Migrating data to new SQL ser

I have an old Btrieve database written by some programmer in the distant
past. It's currently running on an old 3.11 novell server. That applictation
being updated every day.
I need to get that data out of the old Btrieve DB and into a new SQL
database.
What an easy way (tool) to migrate this data over into one or more SQL tables?
thanks
JimHi Jim,
Jim wrote:
> I have an old Btrieve database written by some programmer in the
> distant past. It's currently running on an old 3.11 novell server.
> That applictation being updated every day. I need to get that data
> out of the old Btrieve DB and into a new SQL database. What an easy
> way (tool) to migrate this data over into one or more SQL tables?
You should be able to use the Pervasive Btrieve ODBC driver included
with the product to migrate your data from Btrieve to your Microsoft SQL
Server. There's a good tutorial that covers this online at:
http://tinyurl.com/45m5t/
Hope this helps.|||Thanks, I'll take a look.
Good night.
Jim
"William R. Lorenz" wrote:
> Hi Jim,
> Jim wrote:
> > I have an old Btrieve database written by some programmer in the
> > distant past. It's currently running on an old 3.11 novell server.
> > That applictation being updated every day. I need to get that data
> > out of the old Btrieve DB and into a new SQL database. What an easy
> > way (tool) to migrate this data over into one or more SQL tables?
> You should be able to use the Pervasive Btrieve ODBC driver included
> with the product to migrate your data from Btrieve to your Microsoft SQL
> Server. There's a good tutorial that covers this online at:
> http://tinyurl.com/45m5t/
> Hope this helps.
>|||You will need the DDF files if you do not already have them to use
ODBC. If you need to build these you can take a look at BtSearch32 at
www.nssdd.com. It helps you analyze the structure and build the DDF
files. It will also export to dbase or ascii formats.
Gil

Importing ASCII file using DTS with no row delimiter

Hi,

I am trying to import a file using DTS that does not have any row delimiter. It is a file that was exported from an OLD OLD OLD Macintosh database program (now defunct) called TouchBase. The file uses quotes as text seperators, and tabs for the column delimiters.

Unfortunately, from what I can tell, there are now row delimiters, so the data just keeps going and going, ie like this:

"Bob Smith" "1234 Market Street" "San Diego" "CA" "Josh Smith" "1212 Anywhere Street" "San Diego" "CA" "Jane Smith" "1234 Jane Street" "San Diego" "CA"

Any idea how I can get this to import, or some way to add the delimiter to the file?May be you can use third party tools to the text file to add row delimiter.

And refer to this SQLDTS (http://www.sqldts.com/default.aspx?6,101,257,0,1) link to accomplish the task.|||I can't seem to find any 3rd party tools using google. I've opened the file using a freeware hex editor, and used global search and replace to add one, but then I found out that some records meet the search pattern i chose in the middle of the record, not the end, so that screwed the whole file up..

Very frustrating because I have multiple problems with the file:

#1 - The User used CRLF in a field called "Notes" which is just a free flowing field where the user can type as much or as little as they want in a little diary on the record.

#2 - The User also used tabs in the notes fields, which is throwing off the delimiter for the column.

#3 - The User used double quotes " inside the notes field so that is also throwing it off.

UGH.. Not sure how to fix this mess.|||how big is the file?|||File is about 2.5 megs.

Finally got it.

Used a freeware hex/ascii editor called xvi (search google for hex editor, it's the first one that comes up).

What I did first was stip all CRLF out of the file, since they were only in places where they shouldn't be, not at the end of each row.

Then I went through and did a global replace on all "<TAB>" and changed it to {~} (I first made sure she wasn't using those characters any where in the file!)

Then, I went and stripped all the tabs and all the quotes from the file.

Then i went back and replaced the {~} with "<TAB>" so they would be where they were supposed to.

Finally, I went and I added the CRLF to the end of each record. The way I did this was the last field in each record was a "Date last modified". I asked the client if they needed this, and they said no.

So, I took and used the "wildcard" feature in XVI and did a global replace. Searched for:

"MM/DD/YY"<TAB> and replaced with "MM/DD/YY"<CR><LF>

However, it was kinda tricky, I had to actually do 4 global replaces, because it's an old mac database, and it stored the data in M/D/YY format, MM/D/YY format, M/DD/YY format, and MM/DD/YY format, so there were 4 possible combinations of the way the date was stored for date last modified.

Thank god it worked!

I had 4 errors when importing, and of course SQL server aborts the import if there are any errors. I had to go back in the file and scroll down to the aproximate part where the error was, and look for the problem. Turns out there were 4 records that were missing a field, and that was throwing the whole import off, so I added the field in where apropriate, or just deleted the record.

All in all, this job took me about 15 hours to scrub the file, do all my home work, and get everything together.. Definately a great learning experience for me, and VERY rewarding that I finally got her data to her!!!!|||If you need to do alot of this type of, I would get Codewright. I think Borland now owns the product. It is pricey but well worth it.