Import DB Objects

[trevorwilliams2]

I have a database that was beginning to show signs of corruption.

I am importing all of my database objects into a new DB.
Importing linked table objects, approximately 100, took almost 45 minutes but it did complete.

Importing queries, about 200, took about 1/2 hour and it hung on the last queries.

Modules went over fine.

I am now trying to pull my reports over 12 at a time and the performance is horrible. I am saving my forms for last.

Does anybody have any suggestions as to how I might be able to speed this up?

I am also running this on another copy on my server and am seeing the same results.

Using Access 2003

 

[papadba]

I have a database that was beginning to show signs of corruption.

How does a database "begin to show" corruption?

If all is not as it should be, it is already corrupted - unless i misunderstand something.

The performance concern you mention is probably because of the volume of work to be done versus the size/speed of the target cpu and disk. Is there a bigger/faster system you could use to run a test?

 

[trevorwilliams2]

Running this on a high end server as well, same results.
Normally importing queries & tables shoots right through, never seen it run so slow...

 

[trevorwilliams2]

One thing to mention. If I have 12 reports selected to import it seems to go through the first 11 ok and then seems to hang on the last one...

 

[Hap007]

Hi Trevor,

Question for you.

Is either the source db that you are importing from or the target db that you are creating located on a server.

I found that if you want to import or compact or convert a db, it is best to copy that source to your local disk and create the new db on your local drive. Doing this over the network can take much longer than if you do all on your local hard drive.

If I were you, I would create a copy of the source db.
Then, I would compact and repair that db.
Now, use the compacted db as your source.

Makesure to open your new db exclusive.

Once you have imported all elements, compile the code and then compact the new db.

Hope This Helps,
Hap...


Access Developer

http://www.fcs-software.com/fcsaccessdev.html

Access based Accounting Solutions - with free source code
Access Consultants forum

http://www.tek-tips.com/threadminder.cfm?pid=1121

 

[boblarson]

I would second Hap's suggestion. It is likely you are suffering from network bandwidth problems and so all of this should have been done locally and not over the wire to a server.

Bob Larson
FORMER Microsoft Access MVP (2008-2009, 2009-2010)
Free Tutorials/Samples/Tools:

http://www.btabdevelopment.com

 

[trevorwilliams2]

I finally slugged through this yesterday. It took about half of the day. The import was local.

I made copies and ran this on 2 other machines, all with the same results.

 

[boblarson]

The import was local.

But was the SOURCE (what you were importing FROM) on your local machine?


Bob Larson
FORMER Microsoft Access MVP (2008-2009, 2009-2010)
Free Tutorials/Samples/Tools:

http://www.btabdevelopment.com

 

[boblarson]

In my last post I should have said:

"But was the SOURCE (what you were importing FROM) AND DESTINATION (what you were importing TO) on your local machine?"



Bob Larson
FORMER Microsoft Access MVP (2008-2009, 2009-2010)
Free Tutorials/Samples/Tools:

http://www.btabdevelopment.com

 

[trevorwilliams2]

yes

 

[jsteph]

Are any of the queries Union, Cross-tab, or possibly pass-thru that has a stored procedure as a source?

What happens with those querys (or any query that does not have hard-coded, defined columns) is that when simply selecting for a Report's source or importing--these querys must *run completely*.

So a long, involved Pivot query or a union or pass-thru will have to run compeltely to import a report that contains that query.
--Jim

 

[jsteph]

...I should re-iterate that for a pass-thru it would be a pass-thru without defined colums--such as:
Exec 'my_stored_procedure'

If that proc takes 2 min to run, then you will wait 2 full min to import a report or form with that query as the source.
--Jim

 

[assets]

With network problem, are othe file having similar issue. I had a problem like this when I changed from 97 and running compact fixed some of the issues.

Never give up never give in.

There are no short cuts to anything worth doing