Yes, the extended sproc was successfully recreated in 2005, and uses the full
path to the vs.net 2003/sql server 2000 created DLL...
[quoted text, click to view] "Oleksandr Chuchko" wrote:
> Are these extended sprocs were recreated in SQL Server 2005 using full path
> for xp's DLL?
>
> --
> WBR, Evergray
> --
> Words mean nothing...
>
>
> "gmone" <gmone@discussions.microsoft.com> wrote in message
> news:569B524F-58D2-4B7F-8C58-A472C95F3419@microsoft.com...
> > Greetings,
> >
> > We've recently migrated our database from SQL Server 2000 to SQL Server
> > 2005. Most of this migration has gone well with backup/restore, and a few
> > post steps...
> >
> > One last issue remains, I'm trying to run a stored procedure in 2005 that
> > calls an extended stored procedure that was created with VS.NET 2003, for
> > SQL
> > Server 2000, and am getting "Could not load the DLL or one of the DLLs it
> > references. Reason: 126(The specified module could not be found.)."
> >
> > The modules are present at the location specified. The DLL references the
> > C++ runtime libraries (from VS.NET 2003) which are also present at teh
> > location of the DLL for the extended stored proc. All seems proper...
> >
> > Should i expect to be able to do this, or is this not a directly supported
> > migration path?
> >
> > Any suggestions appreciated!
> >
> > Thanks,
> > Gary
> >
>
>
Are these extended sprocs were recreated in SQL Server 2005 using full path
for xp's DLL?
--
WBR, Evergray
--
Words mean nothing...
[quoted text, click to view] "gmone" <gmone@discussions.microsoft.com> wrote in message
news:569B524F-58D2-4B7F-8C58-A472C95F3419@microsoft.com...
> Greetings,
>
> We've recently migrated our database from SQL Server 2000 to SQL Server
> 2005. Most of this migration has gone well with backup/restore, and a few
> post steps...
>
> One last issue remains, I'm trying to run a stored procedure in 2005 that
> calls an extended stored procedure that was created with VS.NET 2003, for
> SQL
> Server 2000, and am getting "Could not load the DLL or one of the DLLs it
> references. Reason: 126(The specified module could not be found.)."
>
> The modules are present at the location specified. The DLL references the
> C++ runtime libraries (from VS.NET 2003) which are also present at teh
> location of the DLL for the extended stored proc. All seems proper...
>
> Should i expect to be able to do this, or is this not a directly supported
> migration path?
>
> Any suggestions appreciated!
>
> Thanks,
> Gary
>
