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.

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

Adressing memory above 1,7 Gb in SQL

Hi everyone,
We are using W2k3 standard x 64 edition in combination with SQL2000 standard
edition.
W2k with SQL2000 systems are also in use.
These machines have 4Gb of RAM, but i can't seem to get SQL to use more than
1,7Gb.
Tried the /3Gb switch in boot.ini en AWE enabled in sp_configure.
Nothing works, am i doing something strange or wrong ?
Rob
How do you check the memory used ? Performance monitor or Task Manager?
Task Manager will show you a wrong value if you use more than 2 Gb of
RAM.
Also how much memory is used by other Apps and/or OS.
Markus
|||Hi Rob,
Unfortunately SQL 2000 Standard Edition has a limit of 2GB worth of memory.
You can check the Maximum Capacity Specifications here:
http://msdn.microsoft.com/library/de...ar_ts_8dbn.asp
Let me know if I can help any further.
Adam J Warne, MCDBA
"Rob Vos" wrote:

> Hi everyone,
> We are using W2k3 standard x 64 edition in combination with SQL2000 standard
> edition.
> W2k with SQL2000 systems are also in use.
> These machines have 4Gb of RAM, but i can't seem to get SQL to use more than
> 1,7Gb.
> Tried the /3Gb switch in boot.ini en AWE enabled in sp_configure.
> Nothing works, am i doing something strange or wrong ?
> --
> Rob
|||Thanks Adam. Now i need to get back to my supplier, he sold me 4 Gb system
with SQL standard.
Rob
"Adam Warne" wrote:
[vbcol=seagreen]
> Hi Rob,
> Unfortunately SQL 2000 Standard Edition has a limit of 2GB worth of memory.
> You can check the Maximum Capacity Specifications here:
> http://msdn.microsoft.com/library/de...ar_ts_8dbn.asp
> Let me know if I can help any further.
> --
> Adam J Warne, MCDBA
>
> "Rob Vos" wrote:

Adressing memory above 1,7 Gb in SQL

Hi everyone,
We are using W2k3 standard x 64 edition in combination with SQL2000 standard
edition.
W2k with SQL2000 systems are also in use.
These machines have 4Gb of RAM, but i can't seem to get SQL to use more than
1,7Gb.
Tried the /3Gb switch in boot.ini en AWE enabled in sp_configure.
Nothing works, am i doing something strange or wrong ?
--
RobHow do you check the memory used ? Performance monitor or Task Manager?
Task Manager will show you a wrong value if you use more than 2 Gb of
RAM.
Also how much memory is used by other Apps and/or OS.
Markus|||Hi Rob,
Unfortunately SQL 2000 Standard Edition has a limit of 2GB worth of memory.
You can check the Maximum Capacity Specifications here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp
Let me know if I can help any further.
--
Adam J Warne, MCDBA
"Rob Vos" wrote:
> Hi everyone,
> We are using W2k3 standard x 64 edition in combination with SQL2000 standard
> edition.
> W2k with SQL2000 systems are also in use.
> These machines have 4Gb of RAM, but i can't seem to get SQL to use more than
> 1,7Gb.
> Tried the /3Gb switch in boot.ini en AWE enabled in sp_configure.
> Nothing works, am i doing something strange or wrong ?
> --
> Rob|||Thanks Adam. Now i need to get back to my supplier, he sold me 4 Gb system
with SQL standard.
--
Rob
"Adam Warne" wrote:
> Hi Rob,
> Unfortunately SQL 2000 Standard Edition has a limit of 2GB worth of memory.
> You can check the Maximum Capacity Specifications here:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp
> Let me know if I can help any further.
> --
> Adam J Warne, MCDBA
>
> "Rob Vos" wrote:
> > Hi everyone,
> >
> > We are using W2k3 standard x 64 edition in combination with SQL2000 standard
> > edition.
> > W2k with SQL2000 systems are also in use.
> >
> > These machines have 4Gb of RAM, but i can't seem to get SQL to use more than
> > 1,7Gb.
> >
> > Tried the /3Gb switch in boot.ini en AWE enabled in sp_configure.
> >
> > Nothing works, am i doing something strange or wrong ?
> >
> > --
> > Rob

Adressing memory above 1,7 Gb in SQL

Hi everyone,
We are using W2k3 standard x 64 edition in combination with SQL2000 standard
edition.
W2k with SQL2000 systems are also in use.
These machines have 4Gb of RAM, but i can't seem to get SQL to use more than
1,7Gb.
Tried the /3Gb switch in boot.ini en AWE enabled in sp_configure.
Nothing works, am i doing something strange or wrong ?
RobHow do you check the memory used ? Performance monitor or Task Manager?
Task Manager will show you a wrong value if you use more than 2 Gb of
RAM.
Also how much memory is used by other Apps and/or OS.
Markus|||Hi Rob,
Unfortunately SQL 2000 Standard Edition has a limit of 2GB worth of memory.
You can check the Maximum Capacity Specifications here:
http://msdn.microsoft.com/library/d...br />
8dbn.asp
Let me know if I can help any further.
Adam J Warne, MCDBA
"Rob Vos" wrote:

> Hi everyone,
> We are using W2k3 standard x 64 edition in combination with SQL2000 standa
rd
> edition.
> W2k with SQL2000 systems are also in use.
> These machines have 4Gb of RAM, but i can't seem to get SQL to use more th
an
> 1,7Gb.
> Tried the /3Gb switch in boot.ini en AWE enabled in sp_configure.
> Nothing works, am i doing something strange or wrong ?
> --
> Rob|||Thanks Adam. Now i need to get back to my supplier, he sold me 4 Gb system
with SQL standard.
Rob
"Adam Warne" wrote:
[vbcol=seagreen]
> Hi Rob,
> Unfortunately SQL 2000 Standard Edition has a limit of 2GB worth of memory
.
> You can check the Maximum Capacity Specifications here:
> http://msdn.microsoft.com/library/d... />
s_8dbn.asp
> Let me know if I can help any further.
> --
> Adam J Warne, MCDBA
>
> "Rob Vos" wrote:
>