Showing posts with label driver. Show all posts
Showing posts with label driver. Show all posts

Thursday, March 22, 2012

Adventures with 64 bit SQL servers and legacy systems

First of all, thanks to everyone who helped me figure out how to run a
legacy DTS with a 32 bit driver on a 64 bit server. In case anyone
else has this problelm, you also have to download this from Microsoft:
Microsoft SQL Server 2000 DTS Designer Components
Now, my question is this: We have two critical procedures that use the
open query via linked server. I don't think I can modify this to use
DTS. I am having trouble creating a linked server with the 32 bit
driver. It works on the 2000 box and I have had difficulty finding
documentation of how to successfully do this. Erro is as follows:
Cannot initialize the data source object of OLE DB provider - Is there
any way I can modify the default drivers - I need the old 32 bit ODBC
driver that doesn't appear in the list to pull in our Thorougbred
Basic legacy data...
Thanks - any ideas would be appreciated.
"Kristina" <KristinaDBA@.gmail.com> wrote in message
news:1174072527.860042.123270@.n76g2000hsh.googlegr oups.com...
> First of all, thanks to everyone who helped me figure out how to run a
> legacy DTS with a 32 bit driver on a 64 bit server. In case anyone
> else has this problelm, you also have to download this from Microsoft:
> Microsoft SQL Server 2000 DTS Designer Components
> Now, my question is this: We have two critical procedures that use the
> open query via linked server. I don't think I can modify this to use
> DTS. I am having trouble creating a linked server with the 32 bit
> driver. It works on the 2000 box and I have had difficulty finding
> documentation of how to successfully do this. Erro is as follows:
> Cannot initialize the data source object of OLE DB provider - Is there
> any way I can modify the default drivers - I need the old 32 bit ODBC
> driver that doesn't appear in the list to pull in our Thorougbred
> Basic legacy data...
> Thanks - any ideas would be appreciated.
>
You can't use a 32bit OleDb provider in 64bit SQL Server. But you can
always run a 32bit instance of SQL 2005 on 64bit Windows.
David
|||On Mar 16, 5:05 pm, "David Browne" <davidbaxterbrowne no potted
m...@.hotmail.com> wrote:
> "Kristina" <Kristina...@.gmail.com> wrote in message
> news:1174072527.860042.123270@.n76g2000hsh.googlegr oups.com...
>
>
>
>
>
> You can't use a 32bit OleDb provider in 64bit SQL Server. But you can
> always run a 32bit instance of SQL 2005 on 64bit Windows.
> David- Hide quoted text -
> - Show quoted text -
I know, that was my suggestion, but I was out-voted by the network
administrators...thanks for the reply. I will have to find a way to
work around this.

Adventures with 64 bit SQL servers and legacy systems

First of all, thanks to everyone who helped me figure out how to run a
legacy DTS with a 32 bit driver on a 64 bit server. In case anyone
else has this problelm, you also have to download this from Microsoft:
Microsoft SQL Server 2000 DTS Designer Components
Now, my question is this: We have two critical procedures that use the
open query via linked server. I don't think I can modify this to use
DTS. I am having trouble creating a linked server with the 32 bit
driver. It works on the 2000 box and I have had difficulty finding
documentation of how to successfully do this. Erro is as follows:
Cannot initialize the data source object of OLE DB provider - Is there
any way I can modify the default drivers - I need the old 32 bit ODBC
driver that doesn't appear in the list to pull in our Thorougbred
Basic legacy data...
Thanks - any ideas would be appreciated."Kristina" <KristinaDBA@.gmail.com> wrote in message
news:1174072527.860042.123270@.n76g2000hsh.googlegroups.com...
> First of all, thanks to everyone who helped me figure out how to run a
> legacy DTS with a 32 bit driver on a 64 bit server. In case anyone
> else has this problelm, you also have to download this from Microsoft:
> Microsoft SQL Server 2000 DTS Designer Components
> Now, my question is this: We have two critical procedures that use the
> open query via linked server. I don't think I can modify this to use
> DTS. I am having trouble creating a linked server with the 32 bit
> driver. It works on the 2000 box and I have had difficulty finding
> documentation of how to successfully do this. Erro is as follows:
> Cannot initialize the data source object of OLE DB provider - Is there
> any way I can modify the default drivers - I need the old 32 bit ODBC
> driver that doesn't appear in the list to pull in our Thorougbred
> Basic legacy data...
> Thanks - any ideas would be appreciated.
>
You can't use a 32bit OleDb provider in 64bit SQL Server. But you can
always run a 32bit instance of SQL 2005 on 64bit Windows.
David|||On Mar 16, 5:05 pm, "David Browne" <davidbaxterbrowne no potted
m...@.hotmail.com> wrote:
> "Kristina" <Kristina...@.gmail.com> wrote in message
> news:1174072527.860042.123270@.n76g2000hsh.googlegroups.com...
>
>
>
>
>
>
>
> You can't use a 32bit OleDb provider in 64bit SQL Server. But you can
> always run a 32bit instance of SQL 2005 on 64bit Windows.
> David- Hide quoted text -
> - Show quoted text -
I know, that was my suggestion, but I was out-voted by the network
administrators...thanks for the reply. I will have to find a way to
work around this.

Tuesday, March 20, 2012

Adventures with 64 bit SQL servers and legacy systems

First of all, thanks to everyone who helped me figure out how to run a
legacy DTS with a 32 bit driver on a 64 bit server. In case anyone
else has this problelm, you also have to download this from Microsoft:
Microsoft SQL Server 2000 DTS Designer Components
Now, my question is this: We have two critical procedures that use the
open query via linked server. I don't think I can modify this to use
DTS. I am having trouble creating a linked server with the 32 bit
driver. It works on the 2000 box and I have had difficulty finding
documentation of how to successfully do this. Erro is as follows:
Cannot initialize the data source object of OLE DB provider - Is there
any way I can modify the default drivers - I need the old 32 bit ODBC
driver that doesn't appear in the list to pull in our Thorougbred
Basic legacy data...
Thanks - any ideas would be appreciated."Kristina" <KristinaDBA@.gmail.com> wrote in message
news:1174072527.860042.123270@.n76g2000hsh.googlegroups.com...
> First of all, thanks to everyone who helped me figure out how to run a
> legacy DTS with a 32 bit driver on a 64 bit server. In case anyone
> else has this problelm, you also have to download this from Microsoft:
> Microsoft SQL Server 2000 DTS Designer Components
> Now, my question is this: We have two critical procedures that use the
> open query via linked server. I don't think I can modify this to use
> DTS. I am having trouble creating a linked server with the 32 bit
> driver. It works on the 2000 box and I have had difficulty finding
> documentation of how to successfully do this. Erro is as follows:
> Cannot initialize the data source object of OLE DB provider - Is there
> any way I can modify the default drivers - I need the old 32 bit ODBC
> driver that doesn't appear in the list to pull in our Thorougbred
> Basic legacy data...
> Thanks - any ideas would be appreciated.
>
You can't use a 32bit OleDb provider in 64bit SQL Server. But you can
always run a 32bit instance of SQL 2005 on 64bit Windows.
David|||On Mar 16, 5:05 pm, "David Browne" <davidbaxterbrowne no potted
m...@.hotmail.com> wrote:
> "Kristina" <Kristina...@.gmail.com> wrote in message
> news:1174072527.860042.123270@.n76g2000hsh.googlegroups.com...
>
>
> > First of all, thanks to everyone who helped me figure out how to run a
> > legacy DTS with a 32 bit driver on a 64 bit server. In case anyone
> > else has this problelm, you also have to download this from Microsoft:
> > Microsoft SQL Server 2000 DTS Designer Components
> > Now, my question is this: We have two critical procedures that use the
> > open query via linked server. I don't think I can modify this to use
> > DTS. I am having trouble creating a linked server with the 32 bit
> > driver. It works on the 2000 box and I have had difficulty finding
> > documentation of how to successfully do this. Erro is as follows:
> > Cannot initialize the data source object of OLE DB provider - Is there
> > any way I can modify the default drivers - I need the old 32 bit ODBC
> > driver that doesn't appear in the list to pull in our Thorougbred
> > Basic legacy data...
> > Thanks - any ideas would be appreciated.
> You can't use a 32bit OleDb provider in 64bit SQL Server. But you can
> always run a 32bit instance of SQL 2005 on 64bit Windows.
> David- Hide quoted text -
> - Show quoted text -
I know, that was my suggestion, but I was out-voted by the network
administrators...thanks for the reply. I will have to find a way to
work around this.sql