Showing posts with label legacy. Show all posts
Showing posts with label legacy. Show all posts

Wednesday, March 28, 2012

importing users into membership database

Hi, i have a new site built in .net using the login/membership system. i have a legacy database (access) of users from the previous site with email, name, password, etc.

Is it possible to import this data straight into my new membership tables through some insert statement, software or through some other way?

You can do it in code. Use the method CreateUser.

That is: Membership.CreateUser(...

Monday, March 19, 2012

Importing existing DTS packages.

There doesn't seem to be a specific group covering legacy subsystems so I thought I would post this in here.

I have several hundred of these to import that are going to be left to run as they are until such time somebody has the time to migrate them to SSIS.

I have to say I'm not look forward to doing them one at a time using the brain dead UI (it folds up folders behind itself causing another two mouse click between each import). Is there a way of automating this import?

Thanks.

DTS packages are stored in exactly the same location in 2005 as they were in 2000, after all it is just a backward compatibility feature. If you upgraded a system there would be no change, If you are migrating as part of the "upgrade" then just copy the contents of msdb..sysdtspackages.

This may explain more about DTS storage

Transferring DTS Packages
(http://www.sqldts.com/default.aspx?204)

|||

Thanks for the guidance.

I actually found a utility by following your link above. The tool is called DTSbackup2000. It's more than a backup tool as it also transfers DTS packages between servers, including SQL Server 2005 targets.

Here is a direct link to the download: http://www.sqldts.com/download/DTSBackup2000.msi

It has worked for me and saved me a lot of clicky, clicky with the UI!

Importing Excel 2007 and/ or DBF files into SQl server 2005

Greetings,

I'm having a tough time importing some of my legacy database into sql.
I have a number of dbase (IV) files I need to get into SQL. I have tried building a SSIS package with either an foxpro oledb connection or a jet 4.0 one, none of them work bec. of inconsistencies in the data format in my tables (e.g. date fields, etc).

I have tried to save the .dbfs as excel 2007 files, taking advantage of the larger space that comes with '07. Problem is you can't use the import/export wizard with 2007 for some reason and I haven't been able to create a package with the access 12 oledb as I have read.

I have to get some crucial data out of that old system and into the new one and I can't seem to be able to import them properly.

Any hints on what I should do ? (maybe I'm doing something awfully wrong)

Thank you for taking the time to answer my question,
Val

If you have SP2 installed, you should be able to load data from Excel 2007 format using the I/E wizard. Do not use the Excel connection, but use the new OLE DB provider for Office 2007. You will need to set extended properties to "Excel 12.0".

Let me know if you need more assistance.

Thanks.

|||

Try by looking at this : http://msdn2.microsoft.com/en-us/library/aa337084.aspx and also you'll need to configure your connection manually to connect. Set up a Jet OLEDB Connection - point to your folder containing the DBase files. Click the "All" button and change the "Extended Properties" to "DBASE IV".