Hi,
I am building an application for a client. The App has two separate .adp
frontends connecting to two differenet SQL databases. Now I have to get data
from each of the SQL databases for reporting.
It is possible to create another SQL database that links to the two existing
databases, mentioned above?
--
Regards,
AlanIt is possible, but not necessary. To get data from both dbs for reporting,
simply preface your query with the dbs name.
For example:
USE master
GO
SELECT TOP 5 * FROM Northwind.dbo.Customers
Andre|||This is a pretty open question. What do you mean, link exactly? Like do
you want to query them together? Or combine the data for reporting? And
how much data do you have?
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"Arguments are to be avoided: they are always vulgar and often convincing."
(Oscar Wilde)
"steel" <steel@.community.nospam> wrote in message
news:36AD2F00-AEC9-47DE-BFA4-65F0F886764D@.microsoft.com...
> Hi,
> I am building an application for a client. The App has two separate .adp
> frontends connecting to two differenet SQL databases. Now I have to get
> data
> from each of the SQL databases for reporting.
> It is possible to create another SQL database that links to the two
> existing
> databases, mentioned above?
> --
> Regards,
> Alan|||Hi Alan,
How are things going? If there are two different data source, you could
also Linked Table both. I would appreciate it if you could post here to let
us know the detail scenario of the issue. If you have any questions or
concerns, please don't hesitate to let me know. I look forward to hearing
from you, and I am happy to be of assistance.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael,
I am developing two Access .adp projects. The intention is to have them both
as separate marketable databases. A company purchasing one or both projects
would either setup a SQL server or a single project using MSDE.
One company would like to purchase both databases (i.e., purchase .adp
projects plus setup/purchase of SQL Server). The company would like to have
data flow between the two databases. So rather than make changes to our
databases I thougt we could develop a third database that stores or links th
e
other two databases together. Maybe this database would only contain Queries
linking the data. If the company required any table modifications these to
could be stored in the third database.
One problem we may encounter is during replication of the .adp projects as
the company has an off-site use for the projects but would like to merge the
data into the main SQL db's.
What are your thoughts?
p.s: Sorry if this type of advice isn't covered by MSDN support.
Alan
--
Regards,
Alan
"Michael Cheng [MSFT]" wrote:
> Hi Alan,
> How are things going? If there are two different data source, you could
> also Linked Table both. I would appreciate it if you could post here to le
t
> us know the detail scenario of the issue. If you have any questions or
> concerns, please don't hesitate to let me know. I look forward to hearing
> from you, and I am happy to be of assistance.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
>|||My advice would actually be to only have one database,especially if they are
very tightly bound to one another. Your install scripts could create the
database and or the objects at install time. The queries you create in the
database could be morphed as products are installed/deinstalled. This would
make it easier for the user to maintain in terms of backups and such, and
easier for you to create and everything.
You also might consider letting the database be any database, and give the
user scripts to add if they are advanced.
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"Arguments are to be avoided: they are always vulgar and often convincing."
(Oscar Wilde)
"steel" <steel@.community.nospam> wrote in message
news:1B6BDFFD-671C-4B6F-ABFE-73C7C4E69666@.microsoft.com...
> Hi Michael,
> I am developing two Access .adp projects. The intention is to have them
> both
> as separate marketable databases. A company purchasing one or both
> projects
> would either setup a SQL server or a single project using MSDE.
> One company would like to purchase both databases (i.e., purchase .adp
> projects plus setup/purchase of SQL Server). The company would like to
> have
> data flow between the two databases. So rather than make changes to our
> databases I thougt we could develop a third database that stores or links
> the
> other two databases together. Maybe this database would only contain
> Queries
> linking the data. If the company required any table modifications these to
> could be stored in the third database.
> One problem we may encounter is during replication of the .adp projects as
> the company has an off-site use for the projects but would like to merge
> the
> data into the main SQL db's.
> What are your thoughts?
> p.s: Sorry if this type of advice isn't covered by MSDN support.
> Alan
> --
> Regards,
> Alan
>
> "Michael Cheng [MSFT]" wrote:
>|||Hi Alan,
Thanks for your questions and kindly understanding.
Yes, for this issue is more likely an Advisory Services issue. Microsoft
Advisory Services provides short-term advice and guidance for problems not
covered by Problem Resolution Service as well as requests for consultative
assistance for design, development and deployment issues. You may call this
number to get Advisory Services: (800) 936-5200.
I understood your scenario as when customer want a customization table, you
would like to put it in another database other than your project. If I have
misunderstood your concern, please feel free to point it out.
Personally, I agreed with MVP Louis Davidson's suggestion having only one
database.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Showing posts with label connecting. Show all posts
Showing posts with label connecting. Show all posts
Wednesday, March 28, 2012
LinkedServer Failure to connect Oracle 8.1.7
The Error Occured while connecting to oracle from
SQLServer 2000 in WINDOWS 2003, I have tried with MDAC
2.8, MDAC 2.7 and restarted the Server, nothing is
working. We are always getting the Same Error
Error 7399: OLE DB Provider 'MSDAORA' Reported an error.
OLE DB error trace [OLE/DB Provider 'MSDAORA'
IDBInitialize::Initialize returned 0x80004005: ].
But i tried with one of the Windows 2000 machine, its
working fine, Please help...
Thanks in advance, NEED URgent HELP, Whole project gets
stopped because of THIS.
Thanks
Paul
I have the same problem.
If you find the solution, please post the message here.
Thanks.
Vlado
"Paul" <Paulr@.fieldpower.com> wrote in message
news:024501c49781$0fa9fb30$a501280a@.phx.gbl...
> The Error Occured while connecting to oracle from
> SQLServer 2000 in WINDOWS 2003, I have tried with MDAC
> 2.8, MDAC 2.7 and restarted the Server, nothing is
> working. We are always getting the Same Error
> Error 7399: OLE DB Provider 'MSDAORA' Reported an error.
> OLE DB error trace [OLE/DB Provider 'MSDAORA'
> IDBInitialize::Initialize returned 0x80004005: ].
> But i tried with one of the Windows 2000 machine, its
> working fine, Please help...
> Thanks in advance, NEED URgent HELP, Whole project gets
> stopped because of THIS.
> Thanks
> Paul
|||Try turning on trace flag 7300 to get a more detailed error
message. In Query Analyzer, execute the following:
Dbcc traceon (7300,3604)
and then try executing a query against oracle.
-Sue
On Fri, 10 Sep 2004 14:56:44 -0700, "Paul"
<Paulr@.fieldpower.com> wrote:
>The Error Occured while connecting to oracle from
>SQLServer 2000 in WINDOWS 2003, I have tried with MDAC
>2.8, MDAC 2.7 and restarted the Server, nothing is
>working. We are always getting the Same Error
>Error 7399: OLE DB Provider 'MSDAORA' Reported an error.
>OLE DB error trace [OLE/DB Provider 'MSDAORA'
>IDBInitialize::Initialize returned 0x80004005: ].
>But i tried with one of the Windows 2000 machine, its
>working fine, Please help...
>Thanks in advance, NEED URgent HELP, Whole project gets
>stopped because of THIS.
>Thanks
>Paul
|||I am also having the same problem on a Windows 2003 box and can't find a
resolution ANYWHERE!!!!! Linked Oracle Server on Windows 2000 box has been
working great all along. Come on Microsoft - what is the story? I have
seen hundreds and hundred of posts on this issue with no known resolution.
This is a widely used functionality. Anyone out there overcome it??
"Paul" wrote:
> The Error Occured while connecting to oracle from
> SQLServer 2000 in WINDOWS 2003, I have tried with MDAC
> 2.8, MDAC 2.7 and restarted the Server, nothing is
> working. We are always getting the Same Error
> Error 7399: OLE DB Provider 'MSDAORA' Reported an error.
> OLE DB error trace [OLE/DB Provider 'MSDAORA'
> IDBInitialize::Initialize returned 0x80004005: ].
> But i tried with one of the Windows 2000 machine, its
> working fine, Please help...
> Thanks in advance, NEED URgent HELP, Whole project gets
> stopped because of THIS.
> Thanks
> Paul
>
|||I just opened a crit sit with MS to get the answer to this. Here is the
fix with Windows 2003, SQL 2000, and Oracle 9i:
This is discussed in Q193893 and according to this the registry key "
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOC I] " should have
following
entries.
"OracleXaLib"="oraclient9.dll"
"OracleSqlLib"="orasql9.dll"
"OracleOciLib"="oci.dll"
I hope this helps.
Carrie
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
SQLServer 2000 in WINDOWS 2003, I have tried with MDAC
2.8, MDAC 2.7 and restarted the Server, nothing is
working. We are always getting the Same Error
Error 7399: OLE DB Provider 'MSDAORA' Reported an error.
OLE DB error trace [OLE/DB Provider 'MSDAORA'
IDBInitialize::Initialize returned 0x80004005: ].
But i tried with one of the Windows 2000 machine, its
working fine, Please help...
Thanks in advance, NEED URgent HELP, Whole project gets
stopped because of THIS.
Thanks
Paul
I have the same problem.
If you find the solution, please post the message here.
Thanks.
Vlado
"Paul" <Paulr@.fieldpower.com> wrote in message
news:024501c49781$0fa9fb30$a501280a@.phx.gbl...
> The Error Occured while connecting to oracle from
> SQLServer 2000 in WINDOWS 2003, I have tried with MDAC
> 2.8, MDAC 2.7 and restarted the Server, nothing is
> working. We are always getting the Same Error
> Error 7399: OLE DB Provider 'MSDAORA' Reported an error.
> OLE DB error trace [OLE/DB Provider 'MSDAORA'
> IDBInitialize::Initialize returned 0x80004005: ].
> But i tried with one of the Windows 2000 machine, its
> working fine, Please help...
> Thanks in advance, NEED URgent HELP, Whole project gets
> stopped because of THIS.
> Thanks
> Paul
|||Try turning on trace flag 7300 to get a more detailed error
message. In Query Analyzer, execute the following:
Dbcc traceon (7300,3604)
and then try executing a query against oracle.
-Sue
On Fri, 10 Sep 2004 14:56:44 -0700, "Paul"
<Paulr@.fieldpower.com> wrote:
>The Error Occured while connecting to oracle from
>SQLServer 2000 in WINDOWS 2003, I have tried with MDAC
>2.8, MDAC 2.7 and restarted the Server, nothing is
>working. We are always getting the Same Error
>Error 7399: OLE DB Provider 'MSDAORA' Reported an error.
>OLE DB error trace [OLE/DB Provider 'MSDAORA'
>IDBInitialize::Initialize returned 0x80004005: ].
>But i tried with one of the Windows 2000 machine, its
>working fine, Please help...
>Thanks in advance, NEED URgent HELP, Whole project gets
>stopped because of THIS.
>Thanks
>Paul
|||I am also having the same problem on a Windows 2003 box and can't find a
resolution ANYWHERE!!!!! Linked Oracle Server on Windows 2000 box has been
working great all along. Come on Microsoft - what is the story? I have
seen hundreds and hundred of posts on this issue with no known resolution.
This is a widely used functionality. Anyone out there overcome it??
"Paul" wrote:
> The Error Occured while connecting to oracle from
> SQLServer 2000 in WINDOWS 2003, I have tried with MDAC
> 2.8, MDAC 2.7 and restarted the Server, nothing is
> working. We are always getting the Same Error
> Error 7399: OLE DB Provider 'MSDAORA' Reported an error.
> OLE DB error trace [OLE/DB Provider 'MSDAORA'
> IDBInitialize::Initialize returned 0x80004005: ].
> But i tried with one of the Windows 2000 machine, its
> working fine, Please help...
> Thanks in advance, NEED URgent HELP, Whole project gets
> stopped because of THIS.
> Thanks
> Paul
>
|||I just opened a crit sit with MS to get the answer to this. Here is the
fix with Windows 2003, SQL 2000, and Oracle 9i:
This is discussed in Q193893 and according to this the registry key "
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOC I] " should have
following
entries.
"OracleXaLib"="oraclient9.dll"
"OracleSqlLib"="orasql9.dll"
"OracleOciLib"="oci.dll"
I hope this helps.
Carrie
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Friday, March 9, 2012
server Yields Inconsistent results
On SQL Server 2000 we are connecting to many AS/400 tables using Linked
Servers. We are developing a process which runs solely on SQL using Stored
Procedures. We are finding inconsistent results in the return of a query
utilizing a linked table. The query:
Insert into #tmpTableData(ControlID, ApplicationID, RVTBL, RVCNY, RVSTA,
RVPLN, PlanEffDt,PlanEndDt, RVOPT, PSDESC, PFORMN)
SELECT c.ControlID, c.ApplicationID, f.Field1, f.RVCNY, f.RVSTA, f.RVPLN,
dbo.udf_DTStr_FromDecimalMMDDYYYY (f.RVEFMM,f.RVEFDD,f.RVEFYY),
CASE When LEN(RTRIM(p.PLUSR6)) <> 0 Then cast(p.PLUSR6 as varchar(8))
ELSE Replace(convert(char(10) ,getdate() ,102) , '.' , '')
end,
f.RVOPT, p.PSDESC, p.PFORMN
FROM ( [Prod].LSPFCT.ABCTABLE f inner join [Prod].LSPFCT.PDFTABLE p
on f.RVPLN = p.PPLAN) inner join tblControlData c on f.FIELD1 =
c.BasePlanCode
WHERE c.RecordStatus = 5
And (f.RVSTA = '**' or f.RVSTA = c.IssueState)
On a given record, the join may result in 5 records, but if you run the same
query without any data changes or SP changes may result in 3 records. Next
time 5, etc. We did a test of pulling the AS/400 tables down to SQL Server
and began getting consistent results everytime. We see no error messages in
SQL Server logs. Any thoughts?I'm still looking for assistance on this issue. I thought as a Universal
Subscriber that Managed newsgroup submissions received a timely response.
Any support would be greatly appreciated. Thanks
"LisaConsult" wrote:
> On SQL Server 2000 we are connecting to many AS/400 tables using Linked
> Servers. We are developing a process which runs solely on SQL using Store
d
> Procedures. We are finding inconsistent results in the return of a query
> utilizing a linked table. The query:
> Insert into #tmpTableData(ControlID, ApplicationID, RVTBL, RVCNY, RVSTA,
> RVPLN, PlanEffDt,PlanEndDt, RVOPT, PSDESC, PFORMN)
> SELECT c.ControlID, c.ApplicationID, f.Field1, f.RVCNY, f.RVSTA, f.RVPLN,
> dbo.udf_DTStr_FromDecimalMMDDYYYY (f.RVEFMM,f.RVEFDD,f.RVEFYY),
> CASE When LEN(RTRIM(p.PLUSR6)) <> 0 Then cast(p.PLUSR6 as varchar(8))
> ELSE Replace(convert(char(10) ,getdate() ,102) , '.' , '')
> end,
> f.RVOPT, p.PSDESC, p.PFORMN
> FROM ( [Prod].LSPFCT.ABCTABLE f inner join [Prod].LSPFCT.PDFTABLE p
> on f.RVPLN = p.PPLAN) inner join tblControlData c on f.FIELD1 =
> c.BasePlanCode
> WHERE c.RecordStatus = 5
> And (f.RVSTA = '**' or f.RVSTA = c.IssueState)
> On a given record, the join may result in 5 records, but if you run the sa
me
> query without any data changes or SP changes may result in 3 records. Nex
t
> time 5, etc. We did a test of pulling the AS/400 tables down to SQL Serve
r
> and began getting consistent results everytime. We see no error messages
in
> SQL Server logs. Any thoughts?
Servers. We are developing a process which runs solely on SQL using Stored
Procedures. We are finding inconsistent results in the return of a query
utilizing a linked table. The query:
Insert into #tmpTableData(ControlID, ApplicationID, RVTBL, RVCNY, RVSTA,
RVPLN, PlanEffDt,PlanEndDt, RVOPT, PSDESC, PFORMN)
SELECT c.ControlID, c.ApplicationID, f.Field1, f.RVCNY, f.RVSTA, f.RVPLN,
dbo.udf_DTStr_FromDecimalMMDDYYYY (f.RVEFMM,f.RVEFDD,f.RVEFYY),
CASE When LEN(RTRIM(p.PLUSR6)) <> 0 Then cast(p.PLUSR6 as varchar(8))
ELSE Replace(convert(char(10) ,getdate() ,102) , '.' , '')
end,
f.RVOPT, p.PSDESC, p.PFORMN
FROM ( [Prod].LSPFCT.ABCTABLE f inner join [Prod].LSPFCT.PDFTABLE p
on f.RVPLN = p.PPLAN) inner join tblControlData c on f.FIELD1 =
c.BasePlanCode
WHERE c.RecordStatus = 5
And (f.RVSTA = '**' or f.RVSTA = c.IssueState)
On a given record, the join may result in 5 records, but if you run the same
query without any data changes or SP changes may result in 3 records. Next
time 5, etc. We did a test of pulling the AS/400 tables down to SQL Server
and began getting consistent results everytime. We see no error messages in
SQL Server logs. Any thoughts?I'm still looking for assistance on this issue. I thought as a Universal
Subscriber that Managed newsgroup submissions received a timely response.
Any support would be greatly appreciated. Thanks
"LisaConsult" wrote:
> On SQL Server 2000 we are connecting to many AS/400 tables using Linked
> Servers. We are developing a process which runs solely on SQL using Store
d
> Procedures. We are finding inconsistent results in the return of a query
> utilizing a linked table. The query:
> Insert into #tmpTableData(ControlID, ApplicationID, RVTBL, RVCNY, RVSTA,
> RVPLN, PlanEffDt,PlanEndDt, RVOPT, PSDESC, PFORMN)
> SELECT c.ControlID, c.ApplicationID, f.Field1, f.RVCNY, f.RVSTA, f.RVPLN,
> dbo.udf_DTStr_FromDecimalMMDDYYYY (f.RVEFMM,f.RVEFDD,f.RVEFYY),
> CASE When LEN(RTRIM(p.PLUSR6)) <> 0 Then cast(p.PLUSR6 as varchar(8))
> ELSE Replace(convert(char(10) ,getdate() ,102) , '.' , '')
> end,
> f.RVOPT, p.PSDESC, p.PFORMN
> FROM ( [Prod].LSPFCT.ABCTABLE f inner join [Prod].LSPFCT.PDFTABLE p
> on f.RVPLN = p.PPLAN) inner join tblControlData c on f.FIELD1 =
> c.BasePlanCode
> WHERE c.RecordStatus = 5
> And (f.RVSTA = '**' or f.RVSTA = c.IssueState)
> On a given record, the join may result in 5 records, but if you run the sa
me
> query without any data changes or SP changes may result in 3 records. Nex
t
> time 5, etc. We did a test of pulling the AS/400 tables down to SQL Serve
r
> and began getting consistent results everytime. We see no error messages
in
> SQL Server logs. Any thoughts?
server Yields inconsistent results
On SQL Server 2000 we are connecting to many AS/400 tables using Linked
Servers. We are developing a process which runs solely on SQL using Stored
Procedures. We are finding inconsistent results in the return of a query
utilizing a linked table. The query:
Insert into #tmpTableData(ControlID, ApplicationID, RVTBL, RVCNY, RVSTA,
RVPLN, PlanEffDt,PlanEndDt, RVOPT, PSDESC, PFORMN)
SELECT c.ControlID, c.ApplicationID, f.Field1, f.RVCNY, f.RVSTA, f.RVPLN,
dbo.udf_DTStr_FromDecimalMMDDYYYY (f.RVEFMM,f.RVEFDD,f.RVEFYY),
CASE When LEN(RTRIM(p.PLUSR6)) <> 0 Then cast(p.PLUSR6 as varchar(8))
ELSE Replace(convert(char(10) ,getdate() ,102) , '.' , '')
end,
f.RVOPT, p.PSDESC, p.PFORMN
FROM ( [Prod].LSPFCT.ABCTABLE f inner join [Prod].LSPFCT.PDFTABLE p
on f.RVPLN = p.PPLAN) inner join tblControlData c on f.FIELD1 =
c.BasePlanCode
WHERE c.RecordStatus = 5
And (f.RVSTA = '**' or f.RVSTA = c.IssueState)
On a given record, the join may result in 5 records, but if you run the same
query without any data changes or SP changes may result in 3 records. Next
time 5, etc. We did a test of pulling the AS/400 tables down to SQL Server
and began getting consistent results everytime. We see no error messages in
SQL Server logs. Any thoughts?Are you using sp_executesql with any params?
I noticed in-correct results when doing this from MSSQL to AS400.
Tim S|||We are in Query Analyzer, executing a storedprocedure which contains this
query. Any clues or resolutions would be appreciated.
"Tim" wrote:
> Are you using sp_executesql with any params?
> I noticed in-correct results when doing this from MSSQL to AS400.
> Tim S
>|||Hi Lisa,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood your results from Linked Server is
less than you expected randomly. If I have misunderstood your concern,
please feel free to point it out.
First of all, please double confirm that records are the same in original
database,I mean nobody else is updating the records. If so, It is really
strange when the result will be 3 records and then 5 records in the next
one.
Secondly, would you please help me collect more detailed scenario
information by answering the questions below?
- What's your database in AS/400? Is it IBM DB2?
- Does your network or AS/400 endure a high workload?
- Does the database in AS/400 is case sensitive?
- What is the OLE DB driver you are using?
Thirdly, please perform the steps below and let me know whether it will
make any contribution to your issue
1) Have you upgraded to the latest SQL Server 2000 service pack? We have
released SQL Server 2000 SP4 recently and you could download it here
http://www.microsoft.com/downloads/...fc8d-c20e-4446-
99a9-b7f0213f8bc5&DisplayLang=en
2) Please try using OPENQUERY instead of SELECT it from four part name
direcly
3) Please ensure the query will get the correct information while execute
in database of AS/400 directly.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:1F4Tyu3VFHA.3052@.TK2MSFTNGXA01.phx.gbl...
> 1) Have you upgraded to the latest SQL Server 2000 service pack? We have
> released SQL Server 2000 SP4 recently and you could download it here
> [url]http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-[/ur
l]
> 99a9-b7f0213f8bc5&DisplayLang=en
How about "next to latest SQL Server 2000 service pack"? SP 4 has an
outstanding issue or two that might affect you. SP 3a might be your best
bet in a production environment.|||Hi Michael,
Thanks for your post.
Yes my fault, I should have mentioned SP4 has an known issue now with AWE
for more than 2 GB memory, you may have noticed that we have such note in
the download page
Important Note: Microsoft has found an issue with the final build of SP4
that impacts customers who run SQL Server with Address Windowing Extensions
(AWE) support enabled. This issue only impacts computers with more than two
gigabytes (2 GB) of memory where AWE has been explicitly enabled. If you
have this configuration, you should not install SP4. Microsoft is currently
working on the problem and will issue an update soon.
Our SQL Development is working on a public hotfix package for this fix.
This will take longer to have the right tests done and get this properly
released with the hotfix installer. As stated in KB below this problem is
specific to customers that use AWE. The problem limits the amount of
physical memory that SQL Server can use for data cache. The bug only allows
SQL Server to use at maximum 50% of the physical memory in the server. You
can observe this behavior by looking at various perfmon counters including
SQL Server:Memory Manager/Total Server Memory (KB). On an SP3 SQL Server
this value can be up to the amount of physical memory on the computer, but
with SP4 it will never be more than 50% of physical RAM.
Refer the Knowledge Base article for more detailed information
BUG: Not all memory is available when AWE is enabled on a computer that is
running a 32-bit version of SQL Server 2000 SP4
http://support.microsoft.com/kb/899761
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||I've read that the hotfix will be available in approximately 7 days (I read
this on 5/16). Is there any update if it will be released soon?
Thanks
"Michael Cheng [MSFT]" wrote:
> Hi Michael,
> Thanks for your post.
> Yes my fault, I should have mentioned SP4 has an known issue now with AWE
> for more than 2 GB memory, you may have noticed that we have such note in
> the download page
> Important Note: Microsoft has found an issue with the final build of SP4
> that impacts customers who run SQL Server with Address Windowing Extension
s
> (AWE) support enabled. This issue only impacts computers with more than tw
o
> gigabytes (2 GB) of memory where AWE has been explicitly enabled. If you
> have this configuration, you should not install SP4. Microsoft is currentl
y
> working on the problem and will issue an update soon.
> Our SQL Development is working on a public hotfix package for this fix.
> This will take longer to have the right tests done and get this properly
> released with the hotfix installer. As stated in KB below this problem is
> specific to customers that use AWE. The problem limits the amount of
> physical memory that SQL Server can use for data cache. The bug only allow
s
> SQL Server to use at maximum 50% of the physical memory in the server. You
> can observe this behavior by looking at various perfmon counters including
> SQL Server:Memory Manager/Total Server Memory (KB). On an SP3 SQL Server
> this value can be up to the amount of physical memory on the computer, but
> with SP4 it will never be more than 50% of physical RAM.
> Refer the Knowledge Base article for more detailed information
> BUG: Not all memory is available when AWE is enabled on a computer that is
> running a 32-bit version of SQL Server 2000 SP4
> http://support.microsoft.com/kb/899761
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi,
Thanks for your question.
Unfortunately, I am afraid here is no hotfix available now. If it is ready,
we will find the hotfix in RESOLUTION section in KB article 899761.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Servers. We are developing a process which runs solely on SQL using Stored
Procedures. We are finding inconsistent results in the return of a query
utilizing a linked table. The query:
Insert into #tmpTableData(ControlID, ApplicationID, RVTBL, RVCNY, RVSTA,
RVPLN, PlanEffDt,PlanEndDt, RVOPT, PSDESC, PFORMN)
SELECT c.ControlID, c.ApplicationID, f.Field1, f.RVCNY, f.RVSTA, f.RVPLN,
dbo.udf_DTStr_FromDecimalMMDDYYYY (f.RVEFMM,f.RVEFDD,f.RVEFYY),
CASE When LEN(RTRIM(p.PLUSR6)) <> 0 Then cast(p.PLUSR6 as varchar(8))
ELSE Replace(convert(char(10) ,getdate() ,102) , '.' , '')
end,
f.RVOPT, p.PSDESC, p.PFORMN
FROM ( [Prod].LSPFCT.ABCTABLE f inner join [Prod].LSPFCT.PDFTABLE p
on f.RVPLN = p.PPLAN) inner join tblControlData c on f.FIELD1 =
c.BasePlanCode
WHERE c.RecordStatus = 5
And (f.RVSTA = '**' or f.RVSTA = c.IssueState)
On a given record, the join may result in 5 records, but if you run the same
query without any data changes or SP changes may result in 3 records. Next
time 5, etc. We did a test of pulling the AS/400 tables down to SQL Server
and began getting consistent results everytime. We see no error messages in
SQL Server logs. Any thoughts?Are you using sp_executesql with any params?
I noticed in-correct results when doing this from MSSQL to AS400.
Tim S|||We are in Query Analyzer, executing a storedprocedure which contains this
query. Any clues or resolutions would be appreciated.
"Tim" wrote:
> Are you using sp_executesql with any params?
> I noticed in-correct results when doing this from MSSQL to AS400.
> Tim S
>|||Hi Lisa,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood your results from Linked Server is
less than you expected randomly. If I have misunderstood your concern,
please feel free to point it out.
First of all, please double confirm that records are the same in original
database,I mean nobody else is updating the records. If so, It is really
strange when the result will be 3 records and then 5 records in the next
one.
Secondly, would you please help me collect more detailed scenario
information by answering the questions below?
- What's your database in AS/400? Is it IBM DB2?
- Does your network or AS/400 endure a high workload?
- Does the database in AS/400 is case sensitive?
- What is the OLE DB driver you are using?
Thirdly, please perform the steps below and let me know whether it will
make any contribution to your issue
1) Have you upgraded to the latest SQL Server 2000 service pack? We have
released SQL Server 2000 SP4 recently and you could download it here
http://www.microsoft.com/downloads/...fc8d-c20e-4446-
99a9-b7f0213f8bc5&DisplayLang=en
2) Please try using OPENQUERY instead of SELECT it from four part name
direcly
3) Please ensure the query will get the correct information while execute
in database of AS/400 directly.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:1F4Tyu3VFHA.3052@.TK2MSFTNGXA01.phx.gbl...
> 1) Have you upgraded to the latest SQL Server 2000 service pack? We have
> released SQL Server 2000 SP4 recently and you could download it here
> [url]http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-[/ur
l]
> 99a9-b7f0213f8bc5&DisplayLang=en
How about "next to latest SQL Server 2000 service pack"? SP 4 has an
outstanding issue or two that might affect you. SP 3a might be your best
bet in a production environment.|||Hi Michael,
Thanks for your post.
Yes my fault, I should have mentioned SP4 has an known issue now with AWE
for more than 2 GB memory, you may have noticed that we have such note in
the download page
Important Note: Microsoft has found an issue with the final build of SP4
that impacts customers who run SQL Server with Address Windowing Extensions
(AWE) support enabled. This issue only impacts computers with more than two
gigabytes (2 GB) of memory where AWE has been explicitly enabled. If you
have this configuration, you should not install SP4. Microsoft is currently
working on the problem and will issue an update soon.
Our SQL Development is working on a public hotfix package for this fix.
This will take longer to have the right tests done and get this properly
released with the hotfix installer. As stated in KB below this problem is
specific to customers that use AWE. The problem limits the amount of
physical memory that SQL Server can use for data cache. The bug only allows
SQL Server to use at maximum 50% of the physical memory in the server. You
can observe this behavior by looking at various perfmon counters including
SQL Server:Memory Manager/Total Server Memory (KB). On an SP3 SQL Server
this value can be up to the amount of physical memory on the computer, but
with SP4 it will never be more than 50% of physical RAM.
Refer the Knowledge Base article for more detailed information
BUG: Not all memory is available when AWE is enabled on a computer that is
running a 32-bit version of SQL Server 2000 SP4
http://support.microsoft.com/kb/899761
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||I've read that the hotfix will be available in approximately 7 days (I read
this on 5/16). Is there any update if it will be released soon?
Thanks
"Michael Cheng [MSFT]" wrote:
> Hi Michael,
> Thanks for your post.
> Yes my fault, I should have mentioned SP4 has an known issue now with AWE
> for more than 2 GB memory, you may have noticed that we have such note in
> the download page
> Important Note: Microsoft has found an issue with the final build of SP4
> that impacts customers who run SQL Server with Address Windowing Extension
s
> (AWE) support enabled. This issue only impacts computers with more than tw
o
> gigabytes (2 GB) of memory where AWE has been explicitly enabled. If you
> have this configuration, you should not install SP4. Microsoft is currentl
y
> working on the problem and will issue an update soon.
> Our SQL Development is working on a public hotfix package for this fix.
> This will take longer to have the right tests done and get this properly
> released with the hotfix installer. As stated in KB below this problem is
> specific to customers that use AWE. The problem limits the amount of
> physical memory that SQL Server can use for data cache. The bug only allow
s
> SQL Server to use at maximum 50% of the physical memory in the server. You
> can observe this behavior by looking at various perfmon counters including
> SQL Server:Memory Manager/Total Server Memory (KB). On an SP3 SQL Server
> this value can be up to the amount of physical memory on the computer, but
> with SP4 it will never be more than 50% of physical RAM.
> Refer the Knowledge Base article for more detailed information
> BUG: Not all memory is available when AWE is enabled on a computer that is
> running a 32-bit version of SQL Server 2000 SP4
> http://support.microsoft.com/kb/899761
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi,
Thanks for your question.
Unfortunately, I am afraid here is no hotfix available now. If it is ready,
we will find the hotfix in RESOLUTION section in KB article 899761.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Wednesday, March 7, 2012
server using Windows authentication
Hi,
I´m having problems with using Windows authentication with a linked server.
When connecting to the linked server I receive the error:
Error 18452: Login failed for user 'domain/name of a local windows account
on the linked server'. Reason: Not associated with a trusted SQL Server
connection.
When I change to mixed mode on the linked server everything works fine, but
this is not an option that I want to use. How do I make this work with
Windows authentication?
Best regards,
WencheThis is a security delegation issue. Please take a look at this article for
more info.
http://msdn.microsoft.com/library/en-us/adminsql/ad_security_2gmm.asp?frame=true
-oj
Rac v2.2 & QALite!
http://www.rac4sql.net
"Wenche" <weels@.dne.com> wrote in message
news:uiBMiHVkDHA.1708@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I´m having problems with using Windows authentication with a linked
server.
> When connecting to the linked server I receive the error:
> Error 18452: Login failed for user 'domain/name of a local windows account
> on the linked server'. Reason: Not associated with a trusted SQL Server
> connection.
> When I change to mixed mode on the linked server everything works fine,
but
> this is not an option that I want to use. How do I make this work with
> Windows authentication?
> Best regards,
> Wenche
>
I´m having problems with using Windows authentication with a linked server.
When connecting to the linked server I receive the error:
Error 18452: Login failed for user 'domain/name of a local windows account
on the linked server'. Reason: Not associated with a trusted SQL Server
connection.
When I change to mixed mode on the linked server everything works fine, but
this is not an option that I want to use. How do I make this work with
Windows authentication?
Best regards,
WencheThis is a security delegation issue. Please take a look at this article for
more info.
http://msdn.microsoft.com/library/en-us/adminsql/ad_security_2gmm.asp?frame=true
-oj
Rac v2.2 & QALite!
http://www.rac4sql.net
"Wenche" <weels@.dne.com> wrote in message
news:uiBMiHVkDHA.1708@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I´m having problems with using Windows authentication with a linked
server.
> When connecting to the linked server I receive the error:
> Error 18452: Login failed for user 'domain/name of a local windows account
> on the linked server'. Reason: Not associated with a trusted SQL Server
> connection.
> When I change to mixed mode on the linked server everything works fine,
but
> this is not an option that I want to use. How do I make this work with
> Windows authentication?
> Best regards,
> Wenche
>
server to Oracle -OLE/DB Provider 'MSDAORA' IDBInitialize
Hi All
We have a WIN NT 4.0 Server with SQL 7.0 (7.00.961) Connecting to Oracle 8 DB using linked server . With Trace flag 7300 on we get an error message as follows.We are using Oracle 9 i Clien
Thank you , Shaj
DBCC execution completed. If DBCC printed error messages, contact your system administrator
Server: Msg 7399, Level 16, State 1, Line
OLE DB provider 'MSDAORA' reported an error.
[OLE/DB provider returned message: An Oracle Error occured, but message could not be determined
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005: ]provide product name as oracle.give tnsname for the db
which you are trying to connect as datasource..
in the security tab give remote user.password appropriate
for the db which you are trying to connect..this will
resolve your issue
>--Original Message--
>Hi All ,
>We have a WIN NT 4.0 Server with SQL 7.0 (7.00.961)
Connecting to Oracle 8 DB using linked server . With Trace
flag 7300 on we get an error message as follows.We are
using Oracle 9 i Client
>Thank you , Shaji
>DBCC execution completed. If DBCC printed error messages,
contact your system administrator.
>Server: Msg 7399, Level 16, State 1, Line 1
>OLE DB provider 'MSDAORA' reported an error.
>[OLE/DB provider returned message: An Oracle Error
occured, but message could not be determined]
>OLE DB error trace [OLE/DB Provider 'MSDAORA'
IDBInitialize::Initialize returned 0x80004005: ].
>.
>|||We use MS OLE DB Provider for Oracle with following parameter
Product name : Oracl
Data Source : DEVP
Provider string :MSDAORA
With relevant Remote user name and Password . The issue still remain the same. :
Thank you for the fast respons
Shaj|||With it being an initialization error, you may want to make
sure the provider is registered - try registering
msdora.dll. If you get any errors, try reinstalling mdac.
You may also want to refer to the following:
HOW TO: Set Up and Troubleshoot a Linked Server to Oracle in
SQL Server
http://support.microsoft.com/?id=280106
-Sue
On Tue, 20 Apr 2004 00:41:02 -0700, "Shaji"
<anonymous@.discussions.microsoft.com> wrote:
>We use MS OLE DB Provider for Oracle with following parameters
>Product name : Oracle
>Data Source : DEVP
>Provider string :MSDAORA
>With relevant Remote user name and Password . The issue still remain the same. :(
>Thank you for the fast response
>Shaji
>
We have a WIN NT 4.0 Server with SQL 7.0 (7.00.961) Connecting to Oracle 8 DB using linked server . With Trace flag 7300 on we get an error message as follows.We are using Oracle 9 i Clien
Thank you , Shaj
DBCC execution completed. If DBCC printed error messages, contact your system administrator
Server: Msg 7399, Level 16, State 1, Line
OLE DB provider 'MSDAORA' reported an error.
[OLE/DB provider returned message: An Oracle Error occured, but message could not be determined
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005: ]provide product name as oracle.give tnsname for the db
which you are trying to connect as datasource..
in the security tab give remote user.password appropriate
for the db which you are trying to connect..this will
resolve your issue
>--Original Message--
>Hi All ,
>We have a WIN NT 4.0 Server with SQL 7.0 (7.00.961)
Connecting to Oracle 8 DB using linked server . With Trace
flag 7300 on we get an error message as follows.We are
using Oracle 9 i Client
>Thank you , Shaji
>DBCC execution completed. If DBCC printed error messages,
contact your system administrator.
>Server: Msg 7399, Level 16, State 1, Line 1
>OLE DB provider 'MSDAORA' reported an error.
>[OLE/DB provider returned message: An Oracle Error
occured, but message could not be determined]
>OLE DB error trace [OLE/DB Provider 'MSDAORA'
IDBInitialize::Initialize returned 0x80004005: ].
>.
>|||We use MS OLE DB Provider for Oracle with following parameter
Product name : Oracl
Data Source : DEVP
Provider string :MSDAORA
With relevant Remote user name and Password . The issue still remain the same. :
Thank you for the fast respons
Shaj|||With it being an initialization error, you may want to make
sure the provider is registered - try registering
msdora.dll. If you get any errors, try reinstalling mdac.
You may also want to refer to the following:
HOW TO: Set Up and Troubleshoot a Linked Server to Oracle in
SQL Server
http://support.microsoft.com/?id=280106
-Sue
On Tue, 20 Apr 2004 00:41:02 -0700, "Shaji"
<anonymous@.discussions.microsoft.com> wrote:
>We use MS OLE DB Provider for Oracle with following parameters
>Product name : Oracle
>Data Source : DEVP
>Provider string :MSDAORA
>With relevant Remote user name and Password . The issue still remain the same. :(
>Thank you for the fast response
>Shaji
>
Friday, February 24, 2012
server to Oracle -OLE/DB Provider 'MSDAORA' IDBInitialize
Hi All ,
We have a WIN NT 4.0 Server with SQL 7.0 (7.00.961) Connecting to Oracle 8 DB using linked server . With Trace flag 7300 on we get an error message as follows.We are using Oracle 9 i Client
Thank you , Shaji
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'MSDAORA' reported an error.
[OLE/DB provider returned message: An Oracle Error occured, but message could not be determined]
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005: ].
We use MS OLE DB Provider for Oracle with following parameters
Product name : Oracle
Data Source : DEVP
Provider string :MSDAORA
With relevant Remote user name and Password . The issue still remain the same.
Thank you for the fast response
Shaji
|||With it being an initialization error, you may want to make
sure the provider is registered - try registering
msdora.dll. If you get any errors, try reinstalling mdac.
You may also want to refer to the following:
HOW TO: Set Up and Troubleshoot a Linked Server to Oracle in
SQL Server
http://support.microsoft.com/?id=280106
-Sue
On Tue, 20 Apr 2004 00:41:02 -0700, "Shaji"
<anonymous@.discussions.microsoft.com> wrote:
>We use MS OLE DB Provider for Oracle with following parameters
>Product name : Oracle
>Data Source : DEVP
>Provider string :MSDAORA
>With relevant Remote user name and Password . The issue still remain the same.
>Thank you for the fast response
>Shaji
>
We have a WIN NT 4.0 Server with SQL 7.0 (7.00.961) Connecting to Oracle 8 DB using linked server . With Trace flag 7300 on we get an error message as follows.We are using Oracle 9 i Client
Thank you , Shaji
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'MSDAORA' reported an error.
[OLE/DB provider returned message: An Oracle Error occured, but message could not be determined]
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005: ].
We use MS OLE DB Provider for Oracle with following parameters
Product name : Oracle
Data Source : DEVP
Provider string :MSDAORA
With relevant Remote user name and Password . The issue still remain the same.
Thank you for the fast response
Shaji
|||With it being an initialization error, you may want to make
sure the provider is registered - try registering
msdora.dll. If you get any errors, try reinstalling mdac.
You may also want to refer to the following:
HOW TO: Set Up and Troubleshoot a Linked Server to Oracle in
SQL Server
http://support.microsoft.com/?id=280106
-Sue
On Tue, 20 Apr 2004 00:41:02 -0700, "Shaji"
<anonymous@.discussions.microsoft.com> wrote:
>We use MS OLE DB Provider for Oracle with following parameters
>Product name : Oracle
>Data Source : DEVP
>Provider string :MSDAORA
>With relevant Remote user name and Password . The issue still remain the same.
>Thank you for the fast response
>Shaji
>
server to Oracle 9i
I'm connecting to Oracle 8i databases from SQL Server through Linked Server. Now I need to connect to Oracle9i databases from the same SQL Server. What currently I'm doing is: (already installed Oracle 9i client tools on the Server machine) changing the r
egistry setting of "[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxO CI]"
to the respective Oracle 9i DLLs, overriding Oracle 8i DLLS.
Again, if I want to connect to Oracle 8i databases, again I'm changing the registry to point to the 8i DLLs.
My question is: is there any possibility of connecting to both Oracle 8i and 9i databases from one SQL Server machine?
Thanks..
Siva
"Siva" <siva116@.yahoo.com> wrote in message
news:19BE8276-E801-490F-B9B5-EC46DDC600CA@.microsoft.com...
> I'm connecting to Oracle 8i databases from SQL Server through Linked
Server. Now I need to connect to Oracle9i databases from the same SQL
Server. What currently I'm doing is: (already installed Oracle 9i client
tools on the Server machine) changing the registry setting of
"[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxO CI]"
> to the respective Oracle 9i DLLs, overriding Oracle 8i DLLS.
> Again, if I want to connect to Oracle 8i databases, again I'm changing the
registry to point to the 8i DLLs.
> My question is: is there any possibility of connecting to both Oracle 8i
and 9i databases from one SQL Server machine?
The Oracle client version is not tied to the Oracle server version. Either
client version should be able to connect to either server version, so just
user the Oracle 9i client.
David
egistry setting of "[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxO CI]"
to the respective Oracle 9i DLLs, overriding Oracle 8i DLLS.
Again, if I want to connect to Oracle 8i databases, again I'm changing the registry to point to the 8i DLLs.
My question is: is there any possibility of connecting to both Oracle 8i and 9i databases from one SQL Server machine?
Thanks..
Siva
"Siva" <siva116@.yahoo.com> wrote in message
news:19BE8276-E801-490F-B9B5-EC46DDC600CA@.microsoft.com...
> I'm connecting to Oracle 8i databases from SQL Server through Linked
Server. Now I need to connect to Oracle9i databases from the same SQL
Server. What currently I'm doing is: (already installed Oracle 9i client
tools on the Server machine) changing the registry setting of
"[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxO CI]"
> to the respective Oracle 9i DLLs, overriding Oracle 8i DLLS.
> Again, if I want to connect to Oracle 8i databases, again I'm changing the
registry to point to the 8i DLLs.
> My question is: is there any possibility of connecting to both Oracle 8i
and 9i databases from one SQL Server machine?
The Oracle client version is not tied to the Oracle server version. Either
client version should be able to connect to either server version, so just
user the Oracle 9i client.
David
server to Oracle 9i
I'm connecting to Oracle 8i databases from SQL Server through Linked Server. Now I need to connect to Oracle9i databases from the same SQL Server. What currently I'm doing is: (already installed Oracle 9i client tools on the Server machine) changing the registry setting of "[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOCI]
to the respective Oracle 9i DLLs, overriding Oracle 8i DLLS.
Again, if I want to connect to Oracle 8i databases, again I'm changing the registry to point to the 8i DLLs
My question is: is there any possibility of connecting to both Oracle 8i and 9i databases from one SQL Server machine
Thanks.
Siva"Siva" <siva116@.yahoo.com> wrote in message
news:19BE8276-E801-490F-B9B5-EC46DDC600CA@.microsoft.com...
> I'm connecting to Oracle 8i databases from SQL Server through Linked
Server. Now I need to connect to Oracle9i databases from the same SQL
Server. What currently I'm doing is: (already installed Oracle 9i client
tools on the Server machine) changing the registry setting of
"[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOCI]"
> to the respective Oracle 9i DLLs, overriding Oracle 8i DLLS.
> Again, if I want to connect to Oracle 8i databases, again I'm changing the
registry to point to the 8i DLLs.
> My question is: is there any possibility of connecting to both Oracle 8i
and 9i databases from one SQL Server machine?
The Oracle client version is not tied to the Oracle server version. Either
client version should be able to connect to either server version, so just
user the Oracle 9i client.
David
to the respective Oracle 9i DLLs, overriding Oracle 8i DLLS.
Again, if I want to connect to Oracle 8i databases, again I'm changing the registry to point to the 8i DLLs
My question is: is there any possibility of connecting to both Oracle 8i and 9i databases from one SQL Server machine
Thanks.
Siva"Siva" <siva116@.yahoo.com> wrote in message
news:19BE8276-E801-490F-B9B5-EC46DDC600CA@.microsoft.com...
> I'm connecting to Oracle 8i databases from SQL Server through Linked
Server. Now I need to connect to Oracle9i databases from the same SQL
Server. What currently I'm doing is: (already installed Oracle 9i client
tools on the Server machine) changing the registry setting of
"[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOCI]"
> to the respective Oracle 9i DLLs, overriding Oracle 8i DLLS.
> Again, if I want to connect to Oracle 8i databases, again I'm changing the
registry to point to the 8i DLLs.
> My question is: is there any possibility of connecting to both Oracle 8i
and 9i databases from one SQL Server machine?
The Oracle client version is not tied to the Oracle server version. Either
client version should be able to connect to either server version, so just
user the Oracle 9i client.
David
server to Oracle 9i
I'm connecting to Oracle 8i databases from SQL Server through Linked Server.
Now I need to connect to Oracle9i databases from the same SQL Server. What
currently I'm doing is: (already installed Oracle 9i client tools on the Ser
ver machine) changing the r
egistry setting of "& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSDTC\MTxOCI]
"
to the respective Oracle 9i DLLs, overriding Oracle 8i DLLS.
Again, if I want to connect to Oracle 8i databases, again I'm changing the r
egistry to point to the 8i DLLs.
My question is: is there any possibility of connecting to both Oracle 8i and
9i databases from one SQL Server machine?
Thanks..
Siva"Siva" <siva116@.yahoo.com> wrote in message
news:19BE8276-E801-490F-B9B5-EC46DDC600CA@.microsoft.com...
> I'm connecting to Oracle 8i databases from SQL Server through Linked
Server. Now I need to connect to Oracle9i databases from the same SQL
Server. What currently I'm doing is: (already installed Oracle 9i client
tools on the Server machine) changing the registry setting of
"& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSDTC\MTxOCI]"
> to the respective Oracle 9i DLLs, overriding Oracle 8i DLLS.
> Again, if I want to connect to Oracle 8i databases, again I'm changing the
registry to point to the 8i DLLs.
> My question is: is there any possibility of connecting to both Oracle 8i
and 9i databases from one SQL Server machine?
The Oracle client version is not tied to the Oracle server version. Either
client version should be able to connect to either server version, so just
user the Oracle 9i client.
David
Now I need to connect to Oracle9i databases from the same SQL Server. What
currently I'm doing is: (already installed Oracle 9i client tools on the Ser
ver machine) changing the r
egistry setting of "& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSDTC\MTxOCI]
"
to the respective Oracle 9i DLLs, overriding Oracle 8i DLLS.
Again, if I want to connect to Oracle 8i databases, again I'm changing the r
egistry to point to the 8i DLLs.
My question is: is there any possibility of connecting to both Oracle 8i and
9i databases from one SQL Server machine?
Thanks..
Siva"Siva" <siva116@.yahoo.com> wrote in message
news:19BE8276-E801-490F-B9B5-EC46DDC600CA@.microsoft.com...
> I'm connecting to Oracle 8i databases from SQL Server through Linked
Server. Now I need to connect to Oracle9i databases from the same SQL
Server. What currently I'm doing is: (already installed Oracle 9i client
tools on the Server machine) changing the registry setting of
"& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSDTC\MTxOCI]"
> to the respective Oracle 9i DLLs, overriding Oracle 8i DLLS.
> Again, if I want to connect to Oracle 8i databases, again I'm changing the
registry to point to the 8i DLLs.
> My question is: is there any possibility of connecting to both Oracle 8i
and 9i databases from one SQL Server machine?
The Oracle client version is not tied to the Oracle server version. Either
client version should be able to connect to either server version, so just
user the Oracle 9i client.
David
Subscribe to:
Posts (Atom)