Link to Oracle database

Hi all,
I have installed Oracle client tool on the SQL server and have checked the tns file. Everythings look fine, even from the server I can run SQL Plus and connect to the Oracle database. When I create a link and try to refresh tables under linked serve, I ge
t this error: Error 7399:OLE DB provider 'MSDAORA' reported an error. I reinstalled MDAC 2.8, but I get the same error.
Any help would be appreciated.
Shahri
That's a generic error. Try turning on trace flag 7300 or
us SQL Profiler to capture the OLEDB Errors event. This
should give you to get more information about the error.
Additionally, you'll want to check the following article:
HOW TO: Set Up and Troubleshoot a Linked Server to Oracle in
SQL Server
http://support.microsoft.com/?id=280106
-Sue
On Wed, 16 Jun 2004 08:43:37 -0700, Shahri
<Shahri@.discussions.microsoft.com> wrote:

>Hi all,
>I have installed Oracle client tool on the SQL server and have checked the tns file. Everythings look fine, even from the server I can run SQL Plus and connect to the Oracle database. When I create a link and try to refresh tables under linked serve, I g
et this error: Error 7399:OLE DB provider 'MSDAORA' reported an error. I reinstalled MDAC 2.8, but I get the same error.
>Any help would be appreciated.
>Shahri

Link to Oracle database

Hi all,
I have installed Oracle client tool on the SQL server and have checked the t
ns file. Everythings look fine, even from the server I can run SQL Plus and
connect to the Oracle database. When I create a link and try to refresh tabl
es under linked serve, I ge
t this error: Error 7399:OLE DB provider 'MSDAORA' reported an error. I rein
stalled MDAC 2.8, but I get the same error.
Any help would be appreciated.
ShahriThat's a generic error. Try turning on trace flag 7300 or
us SQL Profiler to capture the OLEDB Errors event. This
should give you to get more information about the error.
Additionally, you'll want to check the following article:
HOW TO: Set Up and Troubleshoot a Linked Server to Oracle in
SQL Server
http://support.microsoft.com/?id=280106
-Sue
On Wed, 16 Jun 2004 08:43:37 -0700, Shahri
<Shahri@.discussions.microsoft.com> wrote:

>Hi all,
>I have installed Oracle client tool on the SQL server and have checked the tns file
. Everythings look fine, even from the server I can run SQL Plus and connect to the
Oracle database. When I create a link and try to refresh tables under linked serve,
I g
et this error: Error 7399:OLE DB provider 'MSDAORA' reported an error. I reinstalled MDAC 2.
8, but I get the same error.
>Any help would be appreciated.
>Shahri

Link to Oracel database

Hi all
I am running SQL Server 2000 Enterprise Edition and I want to create a link server to an oracle database. I have installed Oracle client on the server, but when try to test the connection using Oracle Net Configuration Assistant, I'm getting error: "TNS:listener could not resolve SERVICE_NAME given in connect description"
I have read article 280106 (troubleshooting) that didn't help
I appreciate any guidance
RayThe Net Assistant doesn't always generate correct
tnsnames.ora and listener.ora files. You most likely have
something missing in one of these files.
Make sure the Oracle home is specified correctly and that
you have a SID_LIST_LISTENER entry which specifies the sid
that the listener is listening for.
-Sue
On Wed, 9 Jun 2004 12:46:10 -0700, Ray
<anonymous@.discussions.microsoft.com> wrote:
>Hi all,
>I am running SQL Server 2000 Enterprise Edition and I want to create a link server to an oracle database. I have installed Oracle client on the server, but when try to test the connection using Oracle Net Configuration Assistant, I'm getting error: "TNS:listener could not resolve SERVICE_NAME given in connect description".
>I have read article 280106 (troubleshooting) that didn't help.
>I appreciate any guidance.
>Ray

Link to Oracel database

Hi all,
I am running SQL Server 2000 Enterprise Edition and I want to create a link server to an oracle database. I have installed Oracle client on the server, but when try to test the connection using Oracle Net Configuration Assistant, I'm getting error: "TNS:l
istener could not resolve SERVICE_NAME given in connect description".
I have read article 280106 (troubleshooting) that didn't help.
I appreciate any guidance.
Ray
The Net Assistant doesn't always generate correct
tnsnames.ora and listener.ora files. You most likely have
something missing in one of these files.
Make sure the Oracle home is specified correctly and that
you have a SID_LIST_LISTENER entry which specifies the sid
that the listener is listening for.
-Sue
On Wed, 9 Jun 2004 12:46:10 -0700, Ray
<anonymous@.discussions.microsoft.com> wrote:

>Hi all,
>I am running SQL Server 2000 Enterprise Edition and I want to create a link server to an oracle database. I have installed Oracle client on the server, but when try to test the connection using Oracle Net Configuration Assistant, I'm getting error: "TNS:
listener could not resolve SERVICE_NAME given in connect description".
>I have read article 280106 (troubleshooting) that didn't help.
>I appreciate any guidance.
>Ray

Link to Oracel database

Hi all,
I am running SQL Server 2000 Enterprise Edition and I want to create a link
server to an oracle database. I have installed Oracle client on the server,
but when try to test the connection using Oracle Net Configuration Assistant
, I'm getting error: "TNS:l
istener could not resolve SERVICE_NAME given in connect description".
I have read article 280106 (troubleshooting) that didn't help.
I appreciate any guidance.
RayThe Net Assistant doesn't always generate correct
tnsnames.ora and listener.ora files. You most likely have
something missing in one of these files.
Make sure the Oracle home is specified correctly and that
you have a SID_LIST_LISTENER entry which specifies the sid
that the listener is listening for.
-Sue
On Wed, 9 Jun 2004 12:46:10 -0700, Ray
<anonymous@.discussions.microsoft.com> wrote:

>Hi all,
>I am running SQL Server 2000 Enterprise Edition and I want to create a link server
to an oracle database. I have installed Oracle client on the server, but when try to
test the connection using Oracle Net Configuration Assistant, I'm getting error: "T
NS:
listener could not resolve SERVICE_NAME given in connect description".
>I have read article 280106 (troubleshooting) that didn't help.
>I appreciate any guidance.
>Ray

Link server error The provider did not give any information about the error

Hi!

We have a test server (win 2003) in which MSSQL server is installed.In my system (win XP)I installed MYSQL server ,MY sql odbc driver.Now all I want is to create a linked server on MSSQL server so that data on Both server can be in sync.When even a new record in inserted in MYSQL it should be replicated to MSSQL srvr tabl immeditely

I tried to create a linked server but every time I got this error

Error 7399:OLEDB PROVIDER'MSDASQL' reported an error.The provider did not give any information about the error.OLE DB error trace[OLE/DB provider 'MSDASQL' IDBInitilize ::Initialize returned 0x80004005: The provider did not give any information about the error.]

Here is what I have done
sp_addlinkedserver @.server = 'localhost', @.srvproduct = 'MYSQL', @.provider= 'MSDASQL', @.datasrc ='localhost',@.location ='ipadd of my sqlserver',@.provstr ='DriverDriver={MySQL ODBC 3.51 driver};Server=ip add of mysql server;Port=3306;Option=131072;Stmt=;Database=testDB;Uid=root;Pwd=1234asdf' ,@.catalog = 'testDB'
Pls suggest what to do.I am trying for past 2 week but nothing came fruitful..sigh!!

Hi,

1. sp_addlinkedserver should not be returning this error. This error should occur when you try to access the linked server.

2. Can you check the permissions on the odbc driver files and make sure that they have the right permissions?

3. Can it be that the connection information that you specified in the connection string is incorrect?

4. You can also try to create a system DSN ( test the connection ) and use it in the linked server definition using the @.datasource parameter of sp_addlinkedserver( @.datasrc = N'YOU_DATASOURCE_NAME' ).

Hope this helps.

Thanks,
Rakesh

Limited Functionality on Side-by-Side Install

We are testing our SQL 2000 db on a test box in which we loaded SQL 2000 first and then installed SQL Server 2005 Enterprise Trial edition side by side. I am trying to execute new functions in SQL 2005 against the Northwind db to test and these functions are not recognized. What am I missing?

What specific functions are you trying to run? I'm also moving this thread to T-SQL so they can help answer your questions.

Thanks,
Sam

|||

Older sample databases like pubs, northwind are in 80 compatibility mode. So newer keywords or certain syntax of statements or functions behave differently in that compatibility mode. You can either change the compatibility mode of the northwind database by running "sp_dbcmptlevel 'Northwind', '90" or create a new database which will automatically be in 90 compat mode or use the new AdventureWorks sample database. For more details on older compatibility modes and what it affects, see the topic below:

http://msdn2.microsoft.com/en-us/library/ms178653.aspx

limited connections on the developer edition

hi all,

I installed sql server developer edition on

xp box. created a new ssis project and

then when i right click on control flow

then click new connections

i see only limited connection available.

how can i install the other connection option

such as oledb. etc.

thanks

joey

got it

my integration service

is running with limited rights

Limitations sql server 2000 Personal edition

SQL Server Personal edition
Enterprise Manager
on Win 2000
I have the above installed on my own computer
I have connected to a remote database using it's IP adress
I can see all the tables - eg NorthWind
With the appropriate login (Server Authentification) should I be able to
create a new database, Create new tables, see permissions and alter them ?
[I have ALSO TRIED www.aspenterprisemanager.com (we-based tool) same
situation can see but I cannaot do anything else!]
BUT have been told my login will allow this!!!!!
[I have also tried connecting through Query Analyser - no creates allowed]
Jim Bunton
Ok - sorted thsi no replies required thanks
"Jim Bunton" <jBunton@.BlueYonder.co.uk> wrote in message
news:XK37f.173379$RW.126302@.fe2.news.blueyonder.co .uk...
> SQL Server Personal edition
> Enterprise Manager
> on Win 2000
> I have the above installed on my own computer
> I have connected to a remote database using it's IP adress
> I can see all the tables - eg NorthWind
> With the appropriate login (Server Authentification) should I be able to
> create a new database, Create new tables, see permissions and alter them
?
> [I have ALSO TRIED www.aspenterprisemanager.com (we-based tool) same
> situation can see but I cannaot do anything else!]
> BUT have been told my login will allow this!!!!!
> [I have also tried connecting through Query Analyser - no creates allowed]
> --
>
> Jim Bunton
>

Limitations sql server 2000 Personal edition

SQL Server Personal edition
Enterprise Manager
on Win 2000
I have the above installed on my own computer
I have connected to a remote database using it's IP adress
I can see all the tables - eg NorthWind
With the appropriate login (Server Authentification) should I be able to
create a new database, Create new tables, see permissions and alter them ?
[I have ALSO TRIED www.aspenterprisemanager.com (we-based tool) same
situation can see but I cannaot do anything else!]
BUT have been told my login will allow this!!!!!
[I have also tried connecting through Query Analyser - no creates allowe
d]
--
Jim BuntonOk - sorted thsi no replies required thanks
"Jim Bunton" <jBunton@.BlueYonder.co.uk> wrote in message
news:XK37f.173379$RW.126302@.fe2.news.blueyonder.co.uk...
> SQL Server Personal edition
> Enterprise Manager
> on Win 2000
> I have the above installed on my own computer
> I have connected to a remote database using it's IP adress
> I can see all the tables - eg NorthWind
> With the appropriate login (Server Authentification) should I be able to
> create a new database, Create new tables, see permissions and alter them
?
> [I have ALSO TRIED www.aspenterprisemanager.com (we-based tool) same
> situation can see but I cannaot do anything else!]
> BUT have been told my login will allow this!!!!!
> [I have also tried connecting through Query Analyser - no creates allo
wed]
> --
>
> Jim Bunton
>

Limitations Server 2000 Personal Edition

SQL Server Personal edition
Enterprise Manager
on Win 2000
I have the above installed on my own computer
I have connected to a remote database using it's IP adress
I can see all the tables - eg NorthWind
With the appropriate login (Server Authentification) should I be able to
create a new database, Create new tables, see permissions and alter them ?
[I have ALSO TRIED www.aspenterprisemanager.com (we-based tool) same
situation can see but I cannaot do anything else!]
BUT have been told my login will allow this!!!!!
[I have also tried connecting through Query Analyser - no creates allowed]
Jim Bunton
It looks like you have read permissions only
http://sqlservercode.blogspot.com/
"Jim Bunton" wrote:

> SQL Server Personal edition
> Enterprise Manager
> on Win 2000
> I have the above installed on my own computer
> I have connected to a remote database using it's IP adress
> I can see all the tables - eg NorthWind
> With the appropriate login (Server Authentification) should I be able to
> create a new database, Create new tables, see permissions and alter them ?
> [I have ALSO TRIED www.aspenterprisemanager.com (we-based tool) same
> situation can see but I cannaot do anything else!]
> BUT have been told my login will allow this!!!!!
> [I have also tried connecting through Query Analyser - no creates allowed]
> --
>
> Jim Bunton
>
>

Limitations of compatibility level SQL Server 2000 (80) under SQL

My org has a new SQL Server 2005 server and we've just installed a new
commercial database. After the consultant installed the db, I had a
good look around and realised it's set to a lower compatibility level.
The company that sourced the database assures us that it's 'fully
supported within a SQL Server 2005 environment'.
I trust that the application itself works fine as configured, but am
worried that we'll run into issues when we want to configure Reporting
Services and log shipping later in the year. I've done a bit of
research and it seems we won't have access to 'new' SS2005 features,
such as the database diagram tool and the new TABLESAMPLE clause, and
that the server will parse T-SQL differently depending on what
compatability level the database is set to. But I've yet to find how
(whether) this will affect things log shipping and Reporting Services.
Can anyone shed some light on this for me? I'd want this noted as
outstanding issue that they need to sort (our request for tender docs
specified SQL Server 2005 compatibility), but they seem to think it
meets this requirement even though it's running at a lower
compatibility level. I'd like to have some examples of SQL Server 2005
functions that we won't be able to use because of this.
Much appreciated.Yes - there are some features that will not work in compatibility mode.
Many of the neat performance reports in SSMS are not able to collect data on
databases in earlier compatibility mode. Compatibility mode is geared
towards syntax compatiblity and not as much about behavior compatibility.
This is because fundamentally, the engine has changed and will not emulate
the exact same behavior.
I do not recall seeing a link about all of the features that are affected by
this, but since compatibility mode is a database-level setting, you can
create a dummy DB at the desired db compat level and test it out.
Hope this helps!
Rick Heiges
SQL Server MVP
"RJGiskard" <rjgiskard@.googlemail.com> wrote in message
news:cd79f4ec-3464-41ee-ab75-a9450f8a735f@.d21g2000prf.googlegroups.com...
> My org has a new SQL Server 2005 server and we've just installed a new
> commercial database. After the consultant installed the db, I had a
> good look around and realised it's set to a lower compatibility level.
> The company that sourced the database assures us that it's 'fully
> supported within a SQL Server 2005 environment'.
> I trust that the application itself works fine as configured, but am
> worried that we'll run into issues when we want to configure Reporting
> Services and log shipping later in the year. I've done a bit of
> research and it seems we won't have access to 'new' SS2005 features,
> such as the database diagram tool and the new TABLESAMPLE clause, and
> that the server will parse T-SQL differently depending on what
> compatability level the database is set to. But I've yet to find how
> (whether) this will affect things log shipping and Reporting Services.
> Can anyone shed some light on this for me? I'd want this noted as
> outstanding issue that they need to sort (our request for tender docs
> specified SQL Server 2005 compatibility), but they seem to think it
> meets this requirement even though it's running at a lower
> compatibility level. I'd like to have some examples of SQL Server 2005
> functions that we won't be able to use because of this.
> Much appreciated.