existing 32 bit apps through to SQL Server 2005 64 bit

Hi,
we would like to trial our enterprise workforce management application (32
bit VB ActiveX app that currently connects to SQL Server 2000 via ADO)
connecting to SQL Server 2005 64bit server running Win 2003 64 bit.
Do I need to make any changes to application or client access software (ado
etc...) on the clients? or is it as simple as "roll in new 2005 64 server,
convert the database to 2005 64 format [if required] and change the
connection string on the client and watch it fly"...
excuse my ignorance but I need to make sure before signing off on the
business case.
Regards
Steve32-bit or 64-bit is not the problem here: moving the database from SQL
Server 2000 32-bit to 2005 64-bit just requires a detach/attach or
backup/restore.
The issue is if SQL Server 2005 is supported by your application. You need
to contact your application vendor to see if the application is certified for
SQL Server 2005.
Ben Nevarez, MCDBA, OCP
Database Administrator
"Steve" wrote:
> Hi,
> we would like to trial our enterprise workforce management application (32
> bit VB ActiveX app that currently connects to SQL Server 2000 via ADO)
> connecting to SQL Server 2005 64bit server running Win 2003 64 bit.
> Do I need to make any changes to application or client access software (ado
> etc...) on the clients? or is it as simple as "roll in new 2005 64 server,
> convert the database to 2005 64 format [if required] and change the
> connection string on the client and watch it fly"...
> excuse my ignorance but I need to make sure before signing off on the
> business case.
> Regards
> Steve|||thanks Ben,
since it is an in-house Visual Basic 6.0 application that uses ADO for
database connectivity, I would imaging that SQL Server 2005 is support by
Visual Basic and ADO...
"Ben Nevarez" wrote:
> 32-bit or 64-bit is not the problem here: moving the database from SQL
> Server 2000 32-bit to 2005 64-bit just requires a detach/attach or
> backup/restore.
> The issue is if SQL Server 2005 is supported by your application. You need
> to contact your application vendor to see if the application is certified for
> SQL Server 2005.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "Steve" wrote:
> > Hi,
> > we would like to trial our enterprise workforce management application (32
> > bit VB ActiveX app that currently connects to SQL Server 2000 via ADO)
> > connecting to SQL Server 2005 64bit server running Win 2003 64 bit.
> >
> > Do I need to make any changes to application or client access software (ado
> > etc...) on the clients? or is it as simple as "roll in new 2005 64 server,
> > convert the database to 2005 64 format [if required] and change the
> > connection string on the client and watch it fly"...
> >
> > excuse my ignorance but I need to make sure before signing off on the
> > business case.
> >
> > Regards
> > Steve|||Just because it's an in house VB app doesn't guarantee compatibility.
Although nearly all your old SQL statements are supported, some syntax and
stored procedures have changed. For example the old outer join syntax of
use *= in the where clause is no longer available. Test your application.
Danny
"Steve" <Steve@.discussions.microsoft.com> wrote in message
news:DB94DA15-C4EE-4F1D-835E-34D6CF82E612@.microsoft.com...
> thanks Ben,
> since it is an in-house Visual Basic 6.0 application that uses ADO for
> database connectivity, I would imaging that SQL Server 2005 is support
> by
> Visual Basic and ADO...
> "Ben Nevarez" wrote:
>> 32-bit or 64-bit is not the problem here: moving the database from SQL
>> Server 2000 32-bit to 2005 64-bit just requires a detach/attach or
>> backup/restore.
>> The issue is if SQL Server 2005 is supported by your application. You
>> need
>> to contact your application vendor to see if the application is certified
>> for
>> SQL Server 2005.
>> Ben Nevarez, MCDBA, OCP
>> Database Administrator
>>
>> "Steve" wrote:
>> > Hi,
>> > we would like to trial our enterprise workforce management application
>> > (32
>> > bit VB ActiveX app that currently connects to SQL Server 2000 via ADO)
>> > connecting to SQL Server 2005 64bit server running Win 2003 64 bit.
>> >
>> > Do I need to make any changes to application or client access software
>> > (ado
>> > etc...) on the clients? or is it as simple as "roll in new 2005 64
>> > server,
>> > convert the database to 2005 64 format [if required] and change the
>> > connection string on the client and watch it fly"...
>> >
>> > excuse my ignorance but I need to make sure before signing off on the
>> > business case.
>> >
>> > Regards
>> > Steve|||Run SQL Server 2005 Upgrade Advisor and follow the recommendations.
Implement your test environment to test your application.
Ben Nevarez, MCDBA, OCP
Database Administrator
"Danny" wrote:
> Just because it's an in house VB app doesn't guarantee compatibility.
> Although nearly all your old SQL statements are supported, some syntax and
> stored procedures have changed. For example the old outer join syntax of
> use *= in the where clause is no longer available. Test your application.
> Danny
>
> "Steve" <Steve@.discussions.microsoft.com> wrote in message
> news:DB94DA15-C4EE-4F1D-835E-34D6CF82E612@.microsoft.com...
> > thanks Ben,
> > since it is an in-house Visual Basic 6.0 application that uses ADO for
> > database connectivity, I would imaging that SQL Server 2005 is support
> > by
> > Visual Basic and ADO...
> >
> > "Ben Nevarez" wrote:
> >
> >>
> >> 32-bit or 64-bit is not the problem here: moving the database from SQL
> >> Server 2000 32-bit to 2005 64-bit just requires a detach/attach or
> >> backup/restore.
> >>
> >> The issue is if SQL Server 2005 is supported by your application. You
> >> need
> >> to contact your application vendor to see if the application is certified
> >> for
> >> SQL Server 2005.
> >>
> >> Ben Nevarez, MCDBA, OCP
> >> Database Administrator
> >>
> >>
> >> "Steve" wrote:
> >>
> >> > Hi,
> >> > we would like to trial our enterprise workforce management application
> >> > (32
> >> > bit VB ActiveX app that currently connects to SQL Server 2000 via ADO)
> >> > connecting to SQL Server 2005 64bit server running Win 2003 64 bit.
> >> >
> >> > Do I need to make any changes to application or client access software
> >> > (ado
> >> > etc...) on the clients? or is it as simple as "roll in new 2005 64
> >> > server,
> >> > convert the database to 2005 64 format [if required] and change the
> >> > connection string on the client and watch it fly"...
> >> >
> >> > excuse my ignorance but I need to make sure before signing off on the
> >> > business case.
> >> >
> >> > Regards
> >> > Steve
>
>|||thanks ben and danny, much appreciated feedback
Steve
"Ben Nevarez" wrote:
> Run SQL Server 2005 Upgrade Advisor and follow the recommendations.
> Implement your test environment to test your application.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "Danny" wrote:
> > Just because it's an in house VB app doesn't guarantee compatibility.
> > Although nearly all your old SQL statements are supported, some syntax and
> > stored procedures have changed. For example the old outer join syntax of
> > use *= in the where clause is no longer available. Test your application.
> >
> > Danny
> >
> >
> > "Steve" <Steve@.discussions.microsoft.com> wrote in message
> > news:DB94DA15-C4EE-4F1D-835E-34D6CF82E612@.microsoft.com...
> > > thanks Ben,
> > > since it is an in-house Visual Basic 6.0 application that uses ADO for
> > > database connectivity, I would imaging that SQL Server 2005 is support
> > > by
> > > Visual Basic and ADO...
> > >
> > > "Ben Nevarez" wrote:
> > >
> > >>
> > >> 32-bit or 64-bit is not the problem here: moving the database from SQL
> > >> Server 2000 32-bit to 2005 64-bit just requires a detach/attach or
> > >> backup/restore.
> > >>
> > >> The issue is if SQL Server 2005 is supported by your application. You
> > >> need
> > >> to contact your application vendor to see if the application is certified
> > >> for
> > >> SQL Server 2005.
> > >>
> > >> Ben Nevarez, MCDBA, OCP
> > >> Database Administrator
> > >>
> > >>
> > >> "Steve" wrote:
> > >>
> > >> > Hi,
> > >> > we would like to trial our enterprise workforce management application
> > >> > (32
> > >> > bit VB ActiveX app that currently connects to SQL Server 2000 via ADO)
> > >> > connecting to SQL Server 2005 64bit server running Win 2003 64 bit.
> > >> >
> > >> > Do I need to make any changes to application or client access software
> > >> > (ado
> > >> > etc...) on the clients? or is it as simple as "roll in new 2005 64
> > >> > server,
> > >> > convert the database to 2005 64 format [if required] and change the
> > >> > connection string on the client and watch it fly"...
> > >> >
> > >> > excuse my ignorance but I need to make sure before signing off on the
> > >> > business case.
> > >> >
> > >> > Regards
> > >> > Steve
> >
> >
> >