DTS import renames my SPs to previous names

I am using SQL Server 7 SP4.

I have created a blank database in which i am trying to import using DTS
wizard all tables/views/stored procedures without any DATA (records).

I keep getting different errors when importing the views and/or the SPs.
I've tried many things unsuccessfully.

Now even after the error msg of the DTS, i see some of the SPs under
their previous names.

In other words, let's say i have an SP called zprocDeleteProduct and
this SP was previously called procDeleteProduct.

When i check the 2nd database, i see the SP as zprocDeleteProduct
instead of seeing it as procDeleteProduct.

I have other SPs that are being imported with their previous names.

I have renamed these SPs from within Access XP. I don't create SPs
in SQL EM or SQL Query Analyzer.

How can i fix this problem? I don't want to import SPs under their previous
names.

Thank youOpen query analyzer, and execute "sp_helptext zprocDeleteProduct" (or
procDeleteProduct). the output will be the text of the SP. The name
that appears immediatley after the "CREATE PROCEDURE" is the name your
SPs will be imported as. may also want to check your sysobjects table
to verify that names match.
FYI - MS Access isn't "a handy tool to administer SQL Server". Use
Query Analyzer as much as possible, use MMC (Enterprise Manager) as
SELDOM as possible, and use Access never. :-)
Alexey

"serge" <sergea@.nospam.ehmail.com> wrote in message news:<JoUcb.6681$1H3.465640@.news20.bellglobal.com>...
> I am using SQL Server 7 SP4.
> I have created a blank database in which i am trying to import using DTS
> wizard all tables/views/stored procedures without any DATA (records).
> I keep getting different errors when importing the views and/or the SPs.
> I've tried many things unsuccessfully.
> Now even after the error msg of the DTS, i see some of the SPs under
> their previous names.
> In other words, let's say i have an SP called zprocDeleteProduct and
> this SP was previously called procDeleteProduct.
> When i check the 2nd database, i see the SP as zprocDeleteProduct
> instead of seeing it as procDeleteProduct.
> I have other SPs that are being imported with their previous names.
> I have renamed these SPs from within Access XP. I don't create SPs
> in SQL EM or SQL Query Analyzer.
> How can i fix this problem? I don't want to import SPs under their previous
> names.
> Thank you|||Oh, and by the way - if you are transferring objects without data -
use the "Generate SQL Script" wizard in Enterprise Manager, then run
that script in Query Analyzer on the target database. DTS is useful
for data migration, not object migration.
Alexey

"serge" <sergea@.nospam.ehmail.com> wrote in message news:<JoUcb.6681$1H3.465640@.news20.bellglobal.com>...
> I am using SQL Server 7 SP4.
> I have created a blank database in which i am trying to import using DTS
> wizard all tables/views/stored procedures without any DATA (records).
> I keep getting different errors when importing the views and/or the SPs.
> I've tried many things unsuccessfully.
> Now even after the error msg of the DTS, i see some of the SPs under
> their previous names.
> In other words, let's say i have an SP called zprocDeleteProduct and
> this SP was previously called procDeleteProduct.
> When i check the 2nd database, i see the SP as zprocDeleteProduct
> instead of seeing it as procDeleteProduct.
> I have other SPs that are being imported with their previous names.
> I have renamed these SPs from within Access XP. I don't create SPs
> in SQL EM or SQL Query Analyzer.
> How can i fix this problem? I don't want to import SPs under their previous
> names.
> Thank you|||I will use the Query Analyzer to transfer the scripts instead of DTS.

Thanks Alexey

"Alexey Aksyonenko" <Alexey.Aksyonenko@.coanetwork.com> wrote in message
news:1449e414.0309260637.6840efa@.posting.google.co m...
> Oh, and by the way - if you are transferring objects without data -
> use the "Generate SQL Script" wizard in Enterprise Manager, then run
> that script in Query Analyzer on the target database. DTS is useful
> for data migration, not object migration.
> Alexey