Running A Stored Procedure From Enterprise manager?

How do I run a stored procedure from within the Enterprise Manager?
ThanksWell you don't. You can use Query Analyzer though. click on the tools menu
and choose Query analyzer.
Andrew J. Kelly SQL MVP
"Chris Moore" <chris@.dblayoutdotcom> wrote in message
news:Xns97D3A5559BC6cabubba@.207.46.248.16...
> How do I run a stored procedure from within the Enterprise Manager?
> Thanks|||Ok. That is already what I am doing.
Thanks.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in
news:#Cz3liEhGHA.4304@.TK2MSFTNGP05.phx.gbl:

> Well you don't. You can use Query Analyzer though. click on the
> tools menu and choose Query analyzer.
>sql

Running 2000 and 2005 Sql Server on 1 machine

I'm currently running SQL Server 2000 and 2005 on one machine at least I
think I am. I have Enterprise Manager and all the other components for 2000
on my laptop. I also loaded SQL Server 2005 with the .NET application from a
CD that I got from a Microsoft convention a long time ago. Basically, my
problem is when I click on the SQL SERVER 2005 Management Studio and run a
SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
database in 2005 and the mdf and ldf files are stored in the C:\...\Microsoft
SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory. What
am I doing wrong? Can 2000 and 2005 not run on the same box? This is
preventing me from changing the database compatiblity level to 90 because it
doesn't show up. Can anyone help? or suggest what I should do?
-- TCI guess you are connecting to your SQL Server 2000 Instance using SQL Server
Management Studio. That's why it tells you it's 2000 when you run SELECT
@.@.VERSION.
Go to SQL Server Configuration Manager and see if your SQL Server 2005
instance is running. And connect to that instance using SSMS. So, you'll be
able to create databases compatibility level 90.
--
Ekrem Ã?nsoy
"Terrance" <Terrance@.discussions.microsoft.com> wrote in message
news:8EC78FDB-283B-4391-A9D9-6BEB46BC7F9C@.microsoft.com...
> I'm currently running SQL Server 2000 and 2005 on one machine at least I
> think I am. I have Enterprise Manager and all the other components for
> 2000
> on my laptop. I also loaded SQL Server 2005 with the .NET application from
> a
> CD that I got from a Microsoft convention a long time ago. Basically, my
> problem is when I click on the SQL SERVER 2005 Management Studio and run a
> SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
> database in 2005 and the mdf and ldf files are stored in the
> C:\...\Microsoft
> SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory.
> What
> am I doing wrong? Can 2000 and 2005 not run on the same box? This is
> preventing me from changing the database compatiblity level to 90 because
> it
> doesn't show up. Can anyone help? or suggest what I should do?
> -- TC|||Hi Terrance
Along with the other posts!! The second instance (i.e. SQL 2005) would be
installed as a named instance, therefore you should know what instance has
been connected to.
I would not expect the SQL Server 2000 instance to know if the
...\MSSQL.1\BIN directory as the MSSQL.1 directory naming was introduced in
SQL 2005. Even for the SQL 2005 instance you would expect the database files
to be put into ...\MSSQL.1\MSSQL\DATA How are you creating this database?
For a
SQL 2005 instance you can right click the instance in SSMS and choose
properties then the Database Settings will tell you the default data and log
directories, a CREATE DATABASE in a query window without specifying any of
the file names will use these directories.
To see or set the databases compatability level use sp_dbcmptlevel
EXEC sp_dbcmptlevel AdventureWorks;
GO
EXEC sp_dbcmptlevel AdventureWorks, 90;
GO
It is best to change compatibility while no users are connected to the
database!
John
"Terrance" wrote:
> I'm currently running SQL Server 2000 and 2005 on one machine at least I
> think I am. I have Enterprise Manager and all the other components for 2000
> on my laptop. I also loaded SQL Server 2005 with the .NET application from a
> CD that I got from a Microsoft convention a long time ago. Basically, my
> problem is when I click on the SQL SERVER 2005 Management Studio and run a
> SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
> database in 2005 and the mdf and ldf files are stored in the C:\...\Microsoft
> SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory. What
> am I doing wrong? Can 2000 and 2005 not run on the same box? This is
> preventing me from changing the database compatiblity level to 90 because it
> doesn't show up. Can anyone help? or suggest what I should do?
> -- TC

Running 2000 and 2005 Sql Server on 1 machine

I'm currently running SQL Server 2000 and 2005 on one machine at least I
think I am. I have Enterprise Manager and all the other components for 2000
on my laptop. I also loaded SQL Server 2005 with the .NET application from a
CD that I got from a Microsoft convention a long time ago. Basically, my
problem is when I click on the SQL SERVER 2005 Management Studio and run a
SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
database in 2005 and the mdf and ldf files are stored in the C:\...\Microsoft
SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory. What
am I doing wrong? Can 2000 and 2005 not run on the same box? This is
preventing me from changing the database compatiblity level to 90 because it
doesn't show up. Can anyone help? or suggest what I should do?
-- TC
I guess you are connecting to your SQL Server 2000 Instance using SQL Server
Management Studio. That's why it tells you it's 2000 when you run SELECT
@.@.VERSION.
Go to SQL Server Configuration Manager and see if your SQL Server 2005
instance is running. And connect to that instance using SSMS. So, you'll be
able to create databases compatibility level 90.
Ekrem ?nsoy
"Terrance" <Terrance@.discussions.microsoft.com> wrote in message
news:8EC78FDB-283B-4391-A9D9-6BEB46BC7F9C@.microsoft.com...
> I'm currently running SQL Server 2000 and 2005 on one machine at least I
> think I am. I have Enterprise Manager and all the other components for
> 2000
> on my laptop. I also loaded SQL Server 2005 with the .NET application from
> a
> CD that I got from a Microsoft convention a long time ago. Basically, my
> problem is when I click on the SQL SERVER 2005 Management Studio and run a
> SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
> database in 2005 and the mdf and ldf files are stored in the
> C:\...\Microsoft
> SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory.
> What
> am I doing wrong? Can 2000 and 2005 not run on the same box? This is
> preventing me from changing the database compatiblity level to 90 because
> it
> doesn't show up. Can anyone help? or suggest what I should do?
> -- TC
|||Hi Terrance
Along with the other posts!! The second instance (i.e. SQL 2005) would be
installed as a named instance, therefore you should know what instance has
been connected to.
I would not expect the SQL Server 2000 instance to know if the
...\MSSQL.1\BIN directory as the MSSQL.1 directory naming was introduced in
SQL 2005. Even for the SQL 2005 instance you would expect the database files
to be put into ...\MSSQL.1\MSSQL\DATA How are you creating this database?
For a
SQL 2005 instance you can right click the instance in SSMS and choose
properties then the Database Settings will tell you the default data and log
directories, a CREATE DATABASE in a query window without specifying any of
the file names will use these directories.
To see or set the databases compatability level use sp_dbcmptlevel
EXEC sp_dbcmptlevel AdventureWorks;
GO
EXEC sp_dbcmptlevel AdventureWorks, 90;
GO
It is best to change compatibility while no users are connected to the
database!
John
"Terrance" wrote:

> I'm currently running SQL Server 2000 and 2005 on one machine at least I
> think I am. I have Enterprise Manager and all the other components for 2000
> on my laptop. I also loaded SQL Server 2005 with the .NET application from a
> CD that I got from a Microsoft convention a long time ago. Basically, my
> problem is when I click on the SQL SERVER 2005 Management Studio and run a
> SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
> database in 2005 and the mdf and ldf files are stored in the C:\...\Microsoft
> SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory. What
> am I doing wrong? Can 2000 and 2005 not run on the same box? This is
> preventing me from changing the database compatiblity level to 90 because it
> doesn't show up. Can anyone help? or suggest what I should do?
> -- TC

Running 2000 and 2005 Sql Server on 1 machine

I'm currently running SQL Server 2000 and 2005 on one machine at least I
think I am. I have Enterprise Manager and all the other components for 2000
on my laptop. I also loaded SQL Server 2005 with the .NET application from a
CD that I got from a Microsoft convention a long time ago. Basically, my
problem is when I click on the SQL SERVER 2005 Management Studio and run a
SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
database in 2005 and the mdf and ldf files are stored in the C:\...\Microsof
t
SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory. What
am I doing wrong? Can 2000 and 2005 not run on the same box? This is
preventing me from changing the database compatiblity level to 90 because it
doesn't show up. Can anyone help? or suggest what I should do?
-- TCI guess you are connecting to your SQL Server 2000 Instance using SQL Server
Management Studio. That's why it tells you it's 2000 when you run SELECT
@.@.VERSION.
Go to SQL Server Configuration Manager and see if your SQL Server 2005
instance is running. And connect to that instance using SSMS. So, you'll be
able to create databases compatibility level 90.
Ekrem ?nsoy
"Terrance" <Terrance@.discussions.microsoft.com> wrote in message
news:8EC78FDB-283B-4391-A9D9-6BEB46BC7F9C@.microsoft.com...
> I'm currently running SQL Server 2000 and 2005 on one machine at least I
> think I am. I have Enterprise Manager and all the other components for
> 2000
> on my laptop. I also loaded SQL Server 2005 with the .NET application from
> a
> CD that I got from a Microsoft convention a long time ago. Basically, my
> problem is when I click on the SQL SERVER 2005 Management Studio and run a
> SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
> database in 2005 and the mdf and ldf files are stored in the
> C:\...\Microsoft
> SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory.
> What
> am I doing wrong? Can 2000 and 2005 not run on the same box? This is
> preventing me from changing the database compatiblity level to 90 because
> it
> doesn't show up. Can anyone help? or suggest what I should do?
> -- TC|||Hi Terrance
Along with the other posts!! The second instance (i.e. SQL 2005) would be
installed as a named instance, therefore you should know what instance has
been connected to.
I would not expect the SQL Server 2000 instance to know if the
...\MSSQL.1\BIN directory as the MSSQL.1 directory naming was introduced in
SQL 2005. Even for the SQL 2005 instance you would expect the database files
to be put into ...\MSSQL.1\MSSQL\DATA How are you creating this database?
For a
SQL 2005 instance you can right click the instance in SSMS and choose
properties then the Database Settings will tell you the default data and log
directories, a CREATE DATABASE in a query window without specifying any of
the file names will use these directories.
To see or set the databases compatability level use sp_dbcmptlevel
EXEC sp_dbcmptlevel AdventureWorks;
GO
EXEC sp_dbcmptlevel AdventureWorks, 90;
GO
It is best to change compatibility while no users are connected to the
database!
John
"Terrance" wrote:

> I'm currently running SQL Server 2000 and 2005 on one machine at least I
> think I am. I have Enterprise Manager and all the other components for 200
0
> on my laptop. I also loaded SQL Server 2005 with the .NET application from
a
> CD that I got from a Microsoft convention a long time ago. Basically, my
> problem is when I click on the SQL SERVER 2005 Management Studio and run a
> SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
> database in 2005 and the mdf and ldf files are stored in the C:\...\Micros
oft
> SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory. Wha
t
> am I doing wrong? Can 2000 and 2005 not run on the same box? This is
> preventing me from changing the database compatiblity level to 90 because
it
> doesn't show up. Can anyone help? or suggest what I should do?
> -- TCsql

Run Time parameter query

Why is it that I can create a parameter query in Enterprise Manager but
cannot repeat this in query analyser? How could I create a run time parameter
query (in my parlance a query that allows users to input values)!?
Thanks
SamOn Tue, 18 Jan 2005 03:29:03 -0800, Sam wrote:
>Why is it that I can create a parameter query in Enterprise Manager but
>cannot repeat this in query analyser? How could I create a run time parameter
>query (in my parlance a query that allows users to input values)!?
>Thanks
>Sam
Hi Sam,
This can't be done. Interaction with the end user (like asking for a
parameter) must be handled by the client application.
EM apparently has some support for asking parameter values. QA doesn't.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||SQL Server is a back-end server. It cannot ask a user for any parameters since SQL Server runs only
on the server. Possibly EM has some facility to ask for a parameter value, but that would be a
feature in EM. In SQL Server, you typically use stored procedures, where a stored procedure can take
a number of parameters, where the parameters are used inside the query or queries inside the
procedure.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:3755656C-5C1E-4AB5-9018-68B80F3FA855@.microsoft.com...
> Why is it that I can create a parameter query in Enterprise Manager but
> cannot repeat this in query analyser? How could I create a run time parameter
> query (in my parlance a query that allows users to input values)!?
> Thanks
> Sam
>sql

Run Time parameter query

Why is it that I can create a parameter query in Enterprise Manager but
cannot repeat this in query analyser? How could I create a run time parameter
query (in my parlance a query that allows users to input values)!?
Thanks
Sam
On Tue, 18 Jan 2005 03:29:03 -0800, Sam wrote:

>Why is it that I can create a parameter query in Enterprise Manager but
>cannot repeat this in query analyser? How could I create a run time parameter
>query (in my parlance a query that allows users to input values)!?
>Thanks
>Sam
Hi Sam,
This can't be done. Interaction with the end user (like asking for a
parameter) must be handled by the client application.
EM apparently has some support for asking parameter values. QA doesn't.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
|||SQL Server is a back-end server. It cannot ask a user for any parameters since SQL Server runs only
on the server. Possibly EM has some facility to ask for a parameter value, but that would be a
feature in EM. In SQL Server, you typically use stored procedures, where a stored procedure can take
a number of parameters, where the parameters are used inside the query or queries inside the
procedure.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:3755656C-5C1E-4AB5-9018-68B80F3FA855@.microsoft.com...
> Why is it that I can create a parameter query in Enterprise Manager but
> cannot repeat this in query analyser? How could I create a run time parameter
> query (in my parlance a query that allows users to input values)!?
> Thanks
> Sam
>

Run Time parameter query

Why is it that I can create a parameter query in Enterprise Manager but
cannot repeat this in query analyser? How could I create a run time paramete
r
query (in my parlance a query that allows users to input values)!?
Thanks
SamOn Tue, 18 Jan 2005 03:29:03 -0800, Sam wrote:

>Why is it that I can create a parameter query in Enterprise Manager but
>cannot repeat this in query analyser? How could I create a run time paramet
er
>query (in my parlance a query that allows users to input values)!?
>Thanks
>Sam
Hi Sam,
This can't be done. Interaction with the end user (like asking for a
parameter) must be handled by the client application.
EM apparently has some support for asking parameter values. QA doesn't.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||SQL Server is a back-end server. It cannot ask a user for any parameters sin
ce SQL Server runs only
on the server. Possibly EM has some facility to ask for a parameter value, b
ut that would be a
feature in EM. In SQL Server, you typically use stored procedures, where a s
tored procedure can take
a number of parameters, where the parameters are used inside the query or qu
eries inside the
procedure.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:3755656C-5C1E-4AB5-9018-68B80F3FA855@.microsoft.com...
> Why is it that I can create a parameter query in Enterprise Manager but
> cannot repeat this in query analyser? How could I create a run time parame
ter
> query (in my parlance a query that allows users to input values)!?
> Thanks
> Sam
>

Run SQL Server Report from .Net WIndows App...

Does a report have to be run from the Report Manager (IIS), or can rdl files
be executed from .Net code in a Windows Application?
I quess what I am asking is, with Crystal and VB 6, I can lauch a report
through a control embedded in the exe file.
Is there a control to place in a Windows Form that can view a report without
haing a IIS Report Manager?
--
Thanks,
ThomasLL, MCDBAI'm pretty sure SQL Reporting Services 2005 will have a WinForms and a
WebForms viewer.
"Thomas.LeBlanc@.NoSpam.Com" wrote:
> Does a report have to be run from the Report Manager (IIS), or can rdl files
> be executed from .Net code in a Windows Application?
> I quess what I am asking is, with Crystal and VB 6, I can lauch a report
> through a control embedded in the exe file.
> Is there a control to place in a Windows Form that can view a report without
> haing a IIS Report Manager?
> --
> Thanks,
> ThomasLL, MCDBAsql

Run Reporting services from a netwrok share

I have reporting services installed on server A. I want to have iis on server
B point to the report manager on server A. I created a netwrok share on
server A and have iis pointed to this share. When I try to browse the report
manger I get:
Description: An error occurred during the processing of a configuration file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately.
Parser Error Message: Execution permission cannot be acquired
Is it possible to do what I am trying? Is there an easier way?No, you cannot do this. If you want to have report manager on a different
box than the database you can do that but you have to purchase an additional
license. If you want a web farm you can do that. You cannot use any network
file sharing to accomplish anything. The reason is, Report Manager is a
asp.net application. The reports do not exist as files, they are all stored
in the database (search for *.rdl on the server and you will not see any).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"lykerd" <lykerd@.discussions.microsoft.com> wrote in message
news:775ED6F2-F21A-4DA1-A3AE-5C09A3FFA94B@.microsoft.com...
>I have reporting services installed on server A. I want to have iis on
>server
> B point to the report manager on server A. I created a netwrok share on
> server A and have iis pointed to this share. When I try to browse the
> report
> manger I get:
> Description: An error occurred during the processing of a configuration
> file
> required to service this request. Please review the specific error details
> below and modify your configuration file appropriately.
> Parser Error Message: Execution permission cannot be acquired
> Is it possible to do what I am trying? Is there an easier way?

Run DTS within a DTS

Hi

On Enterprise Manager have created two DTS packages:

1 = Transfer Data
2 = Process Cube

In total we have loads of these.

What I want to do is to create a DTS that will run the toehr 2 DTS in sucessions.

Now when I use the Execute Package Task facility to run the 2 DTS, it fails...or just hangs for an eternity.

Is there way to run (say) 7 Execute Package Tasks without the master DTS failing?Any help please.... searched the web with no valid answers to this issues

Run DTS from SQL server jobs..

Hi is it possible to run multiple DTS from a SQL server
job? I tried the SQL enterprise manager wizard to build a
job but it does not allow me to select a DTS job. Am I
doing anything wrong?You can schedule multiple packages to run from one job. Manually edit the
job, and add as many Operating system command steps as there are DTS
pacakges to run. You can use the dtsrunui.exe to get the proper command
line using the advanced button in the user interface. It can generate the
command line for you, and you can copy paste it into the job step.
Simon Worth
"Yaheya Quazi" <yquazi@.ucmerced.edu> wrote in message
news:5c4501c52400$71c39450$a401280a@.phx.gbl...
> Hi is it possible to run multiple DTS from a SQL server
> job? I tried the SQL enterprise manager wizard to build a
> job but it does not allow me to select a DTS job. Am I
> doing anything wrong?|||See the post a few items down titled Calling a DTS job thru a Stored
Procedure. That would allow you to specify as many jobs as you like.
"Yaheya Quazi" wrote:

> Hi is it possible to run multiple DTS from a SQL server
> job? I tried the SQL enterprise manager wizard to build a
> job but it does not allow me to select a DTS job. Am I
> doing anything wrong?
>

Run DDL Task failed when I try to BeginTransaction in it

Just try this:

1.Create a AS Connection Manager in a package, put the RetainSameConnection property into True.

2.Drag a Run DDL Task, and use the Connection in step1.

3.write the DDL query as this:

<Command>
<BeginTransaction />
</Command>

4.Run the package.

Result: It said a mistake like this:

Error: the element Command at 7 row, 38 column(Namespace urn:schemas-microsoft-com:xml-analysis) can not be displayed under Envelope/Body/Execute/Command.

Please help me, what's the hell of this?

Thanks.

Help,Help!

Thanks!

|||

Help, need help!

|||Help! Really need your help!!!|||

Can you provide some more information? what have you tried to debug.

did you try here?

http://www.topxml.com/MS-XML-Analysis/rn-219188_How-to-format-a-NotifyTableChange-command.aspx

what does your XML tag and attribute look like at 7 row, 38 column? can you post it?

|||

Thanks, but I dount that it's no business about the XML tag and attribute.

I think perhaps we just CANNOT BeginTransaction in a DDL task.

Please have a try like what I did, you will get the same result, I belive.

Thanks!

|||

Please save me!

Thanks, I am knocked down by this problem.

Run DDL Task failed when I try to BeginTransaction in it

Just try this:

1.Create a AS Connection Manager in a package, put the RetainSameConnection property into True.

2.Drag a Run DDL Task, and use the Connection in step1.

3.write the DDL query as this:

<Command>
<BeginTransaction />
</Command>

4.Run the package.

Result: It said a mistake like this:

Error: the element Command at 7 row, 38 column(Namespace urn:schemas-microsoft-com:xml-analysis) can not be displayed under Envelope/Body/Execute/Command.

Please help me, what's the hell of this?

Thanks.

Help,Help!

Thanks!

|||

Help, need help!

|||Help! Really need your help!!!|||

Can you provide some more information? what have you tried to debug.

did you try here?

http://www.topxml.com/MS-XML-Analysis/rn-219188_How-to-format-a-NotifyTableChange-command.aspx

what does your XML tag and attribute look like at 7 row, 38 column? can you post it?

|||

Thanks, but I dount that it's no business about the XML tag and attribute.

I think perhaps we just CANNOT BeginTransaction in a DDL task.

Please have a try like what I did, you will get the same result, I belive.

Thanks!

|||

Please save me!

Thanks, I am knocked down by this problem.

run a query against another server

Hi, I have got SSMSE installed and am seeing how I can use it for my work stuff rather than MSDE.

I used to import using Enterprise Manager tables from our corp servers into my local MSDE to work with.

I have managed to create the required tables in SQL Exprerss and can see I have a connection to my local server (SQL Express) and my corp server.

When I query sys.servers I only see SQL Express and not the corp one. How do I run a select query that selects from the corp and inserts into the local. I have all the insert fields etc but it errors stating the corp database is not in sys.serevrs?

Thanks

hi,

you have to define a "linked server"..

select the Server Objects->Linked Servers node in SSMSE in your local connection server... add a linked server pointing to the corp server providing the appropriate credentials..

you can then query the linked server providing the 4 part naming of the object like

SELECT * FROM linked_server_name.database_name.schema_name.object_name;

once you have the connection working, you can then INSERT SELECT into your local database..

regards

|||Hi, I tried this but get errors?

I can connect in server explorer within VS.NET 2005 Pro IDE and get the following information:

Provider=
.NET Framework Data Provider for SQL Server

Connection String=
Data Source=Virtue;Initial Catalog=orbital;Integrated Security=True

I do not get an option to choose this provider in the combobox on the New Linked Server page?

So I get this error?

TITLE: Microsoft SQL Server Management Studio Express

"The linked server has been created but failed a connection test. Do you want to keep the linked server?"

ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)

The OLE DB provider "SQLNCLI" for linked server "VIRTUE" reported an error. Authentication failed.
Cannot initialize the data source object of OLE DB provider "SQLNCLI" for linked server "VIRTUE".
OLE DB provider "SQLNCLI" for linked server "VIRTUE" returned message "Invalid authorization specification".
OLE DB provider "SQLNCLI" for linked server "VIRTUE" returned message "Invalid connection string attribute". (Microsoft SQL Server, Error: 7399)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3042&EvtSrc=MSSQLServer&EvtID=7399&LinkId=20476

|||

hi,

pachjo wrote:

Hi, I tried this but get errors?

I can connect in server explorer within VS.NET 2005 Pro IDE and get the following information:

Provider=
.NET Framework Data Provider for SQL Server

Connection String=
Data Source=Virtue;Initial Catalog=orbital;Integrated Security=True

I do not get an option to choose this provider in the combobox on the New Linked Server page?

this information is relative to the "Add connection" wizard in the Server Explorer, isn't it?

actually the .NET Framework Data Provider for SQL Server is SQL Native Client and, in my installation, it is obviously available in SSMSE as well as SQLNCLI..

So I get this error?

TITLE: Microsoft SQL Server Management Studio Express

"The linked server has been created but failed a connection test. Do you want to keep the linked server?"

ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)

The OLE DB provider "SQLNCLI" for linked server "VIRTUE" reported an error. Authentication failed.
Cannot initialize the data source object of OLE DB provider "SQLNCLI" for linked server "VIRTUE".
OLE DB provider "SQLNCLI" for linked server "VIRTUE" returned message "Invalid authorization specification".
OLE DB provider "SQLNCLI" for linked server "VIRTUE" returned message "Invalid connection string attribute". (Microsoft SQL Server, Error: 7399)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3042&EvtSrc=MSSQLServer&EvtID=7399&LinkId=20476

did you provide the correct credential info for the remote server?

regards

|||Well I can connect no problem through server explorer and accerss the data. I used the same connection string from there and tried various things such as:

Linked Server = Virtue
Provider=SQL Native Client
Product Name=Virtue (not sure what to put here?)
Data source=Virtue
Connection String=Data Source=Virtue;Initial Catalog=orbital;Integrated Security=True
Catalog=blank

I am unsure what I am doing wrong here?
|||

hi,

Linked Server: network name of the remote SQL Server instance

Provider = SQL Native Client

Product Name = Provider = SQL Native Client

then you can go on bypassing the additional info of the "General" tab of the "Add linked server" dialog...

in the "Security" tab select the appropriate mapping or specify a specif SQL Server login (Be made using this security context)..

regards

|||

This is really getting me down as I am getting no where

I set the details as above and tried entering my nt logon details in various ways to include/omit the domain name but still no joy!

What I dont get is within VS.NET it connects straight away without bother and I can acces the tables! ?

|||

HI,

OK I am sort of there, but not completely?

I have created a connection to the remote server and created a linked server to it using the same coalation as the remote.

But when I create the tables, import the date all is well until I try to run a script and I get a coaltion conflict?

The remote is SQL_Latin1_General_CP1_CI_AS but I get an error complaining about

Latin1_General_CI_AS?

When I look at the remote and the linked they both say SQL_Latin1_General_CP1_CI_AS so I don't know where SQL_Latin1_General_CI_AS is coming from?

Help anyone....

|||

Oh...hold the phone!

I think I have found it?

The local database has the wrong coalation so.......I will start again ;-)