Remove Fields Programatically

Is it possible to remove fields programatically from a report file at run time?

I have too many years worth or data being returned and it exceeds the width of an A4 page - So I want to allow the users to select the years that they wish to view via a checkedlistbox - but each time I remove the Columns from the dataTable that populates the report files I get an error as noted below

I'm using VS 2005 and CR shipped with it...

<error>
The field name is not known.
Error in Filed C:\documents and settings\<insert file path here>\rpt_siz_xty {EBEF8981-654C-42C7-9DDA-3AC4184771C8}.RPT:
Error in formula <sizYr01>.
If IsNull({sp_rpt_siz_xty;1.sizYr01}) Then space(12) Else Cstr({sp_rpt_siz_xty;1.sizYr01})
The field name is not known.
</error>

I've dome a fair amount of searching and can't seem to find any remove methods for the field definitions...

Anyone?I think the field u r deleting is used in a formula in report. U need to delete that formula also.|||Why do you want to do it at runtime?

Remove duplicate entries in a search

Is there a way to find only unique entries for a search. Currently I am
looking for jobs that a run for a give database, but the script will
return multiple job entries for the same job if the database is
reference many times in that job, (once per reference) is there a way
to weed out the duplicates?
Thanks.
-Matt-
<code>
select sj.name
from msdb.dbo.sysjobs sj join msdb.dbo.sysjobsteps sjs
on sj.job_id = sjs.job_id
where sjs.database_name = 'database_name' order by 'name'
</code>Try,
select sj.name
from msdb.dbo.sysjobs sj
where exists (
select *
from msdb.dbo.sysjobsteps sjs
where sjs.database_name = 'database_name' and sjs.job_id = sj.job_id
)
order by 'name'
go
You can also use "DISTINCT" in the original statement.
AMB
"Matthew" wrote:

> Is there a way to find only unique entries for a search. Currently I am
> looking for jobs that a run for a give database, but the script will
> return multiple job entries for the same job if the database is
> reference many times in that job, (once per reference) is there a way
> to weed out the duplicates?
> Thanks.
> -Matt-
>
> <code>
> select sj.name
> from msdb.dbo.sysjobs sj join msdb.dbo.sysjobsteps sjs
> on sj.job_id = sjs.job_id
> where sjs.database_name = 'database_name' order by 'name'
> </code>
>|||Thanks
Works perfectly.

Remote view

I was wondering if i should create a lil program that could run in the tray
showing status of jobs running on a SQL server. By that i mean if they are
enabled, runnable and so on. Are there anyone in here that can lead me to
some info related to that? I want to devlope it using C#.
I have been roaming the net for info about this but so far no luck. Is there
an API on the SQL server that enables me to do this?
Best regards
TrondThe SQL-DMO API should give you what you want for SQL7.0 and 2000.
However, DMO is a COM API so you may prefer instead to develop your
application with SMO, which is DMO's .NET replacement in SQL Server
2005.
http://msdn.microsoft.com/library/d.../>
01_2yi7.asp
David Portas
SQL Server MVP
--

Remote stored procedure

I am trying to run a stored procedure on a remote server and insert the
output into a table on the local machine.
The two servers are linked and I am using the code as follows
BEGIN DISTRIBUTED TRAN
insert into ServerA.Database.dbo.drv_total
exec ServerB.master.dbo.xp_fixeddrives
COMMIT TRAN
The MSDTC is started on both machines.
I am getting this error:
Server: Msg 7391, Level 16, State 1, Line 2
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in the
specified transaction coordinator. ]
Any thoughts?
TIA,
nivek
Hi Nivek,
Are you running on Windows 2003? If so, the following link may apply to you:
http://support.microsoft.com/default...b;en-us;329332
"The problem occurs because Microsoft Distributed Transaction Coordinator
(MS DTC) is not configured for network access. By default, the network access
settings of MS DTC are disabled on new installations of SQL Server 2000 on
computers running Windows Server 2003, Enterprise Edition. "
Best Regards,
Joe Sack
Author of "SQL Server 2000 Fast Answers..."
http://www.JoeSack.com
"nivek" wrote:

> I am trying to run a stored procedure on a remote server and insert the
> output into a table on the local machine.
> The two servers are linked and I am using the code as follows
> BEGIN DISTRIBUTED TRAN
> insert into ServerA.Database.dbo.drv_total
> exec ServerB.master.dbo.xp_fixeddrives
> COMMIT TRAN
> The MSDTC is started on both machines.
> I am getting this error:
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider 'SQLOLEDB'
> was unable to begin a distributed transaction.
> [OLE/DB provider returned message: New transaction cannot enlist in the
> specified transaction coordinator. ]
>
> Any thoughts?
>
> TIA,
> nivek
>
>
sql

Remote stored procedure

I am trying to run a stored procedure on a remote server and insert the
output into a table on the local machine.
The two servers are linked and I am using the code as follows
BEGIN DISTRIBUTED TRAN
insert into ServerA.Database.dbo.drv_total
exec ServerB.master.dbo.xp_fixeddrives
COMMIT TRAN
The MSDTC is started on both machines.
I am getting this error:
Server: Msg 7391, Level 16, State 1, Line 2
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in the
specified transaction coordinator. ]
Any thoughts?
TIA,
nivekHi Nivek,
Are you running on Windows 2003? If so, the following link may apply to you:
http://support.microsoft.com/default.aspx?scid=kb;en-us;329332
"The problem occurs because Microsoft Distributed Transaction Coordinator
(MS DTC) is not configured for network access. By default, the network access
settings of MS DTC are disabled on new installations of SQL Server 2000 on
computers running Windows Server 2003, Enterprise Edition. "
Best Regards,
Joe Sack
Author of "SQL Server 2000 Fast Answers..."
http://www.JoeSack.com
"nivek" wrote:
> I am trying to run a stored procedure on a remote server and insert the
> output into a table on the local machine.
> The two servers are linked and I am using the code as follows
> BEGIN DISTRIBUTED TRAN
> insert into ServerA.Database.dbo.drv_total
> exec ServerB.master.dbo.xp_fixeddrives
> COMMIT TRAN
> The MSDTC is started on both machines.
> I am getting this error:
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider 'SQLOLEDB'
> was unable to begin a distributed transaction.
> [OLE/DB provider returned message: New transaction cannot enlist in the
> specified transaction coordinator. ]
>
> Any thoughts?
>
> TIA,
> nivek
>
>

Remote SQL Server 2000 Perfmon Not Working

I have a SQL Server 2000 cluster running on x64 OS. I found the threads in the forum to run perfmon locally by using the x86 version of perfmon (mmc /32 perfmon). However, I cannot run a perfmon remotely from another machine and see the SQL Server perfmon data on any of the nodes in the cluster. The remote perfmon picks up all of the other perfmon variables but no SQL.

I found another thread where somebody asked this question but it wasn't answered. Thanks in advance.

Mark

there is no x64 counter.|||Absolutely correct. There is no x64 SQL 2000 counter which is why one must run the 32-bit version of perfmon. I can run the 32-bit perfmon locally on my cluster nodes and see the 32-bit SQL performance counters but I am unable to run perfmon from a remote machine, connect to one of my cluster nodes and see the SQL counters.|||

What do you mean by "remote computer"? Are you trying to do this across the Internet or VPN or what?

Perfmon depends on the "named pipes" protocol and will never work across the Internet because NetBios is blocked by most ISPs.

|||

We are in the process of setting up Operations Manager to collect perf data. Until then we are stuck with a management server that has perfmon running on it centrally collecting data from various servers. I can see other performance counters, just not the ones for SQL Server.

The management server and the SQL cluster are on the same LAN/subnet without any type of firewall between them. I have a test cluster that is doing the exact same thing.

Remote server Error...

Hi there. I'm getting the following error when trying to run a query on a
remote server I've set up:
Server 'SERVER_1' is not configured for DATA ACCESS.
I know this option is available for Linked Servers but I dont know why I'm
seeing this problem with a remote server. The Remote Server I've created has
RPC enabled ans is using a valid server name and login.
Any ideas?...Try executing:
exec sp_serveroption 'Server_1', 'data access', 'true'
-Sue
On Wed, 30 Mar 2005 09:49:03 -0800, len
<len@.discussions.microsoft.com> wrote:

>Hi there. I'm getting the following error when trying to run a query on a
>remote server I've set up:
>Server 'SERVER_1' is not configured for DATA ACCESS.
>I know this option is available for Linked Servers but I dont know why I'm
>seeing this problem with a remote server. The Remote Server I've created ha
s
>RPC enabled ans is using a valid server name and login.
>Any ideas?...

Remote Server

Hi all,

I am trying to locate some scripts for create/update and a nightly scripts that run to update some databases.

Now within the server itself there are no scripts that are running beside the normal system stored procedure.

I notice that the server is a remote server is it possible for the scripts that are running coming from another server.

Once I click on the server (NTBVM) and right click on the property RPC is check, and 'map remote logins to differents local logins' has the radio dial marked however when you look at the list below no information is recorded.

Please help

Thanking you in advanceGreetings, M'Lady! It's good to see you again.

While it is unlikely, it is possible that the scripts would run on another server.

Is this something you are investigating because it is happening now, or something you are planning so it will happen soon?

-PatP|||It something that I was asked to fix and give a time line.

One of the task is to modify registry settings for a OSI servlet(What is the world).

The network admin said that there are scripts that run and I've look everywhere for the scripts and can't find them.

The frontend of this tool call OSI and the backend is SQL. I wonder if I would be able to find the scripts in the tool itself.

I don't have a clue.

Thanks for responding so fast.

Lystra|||Ok, it is pretty easy to define OSI (http://searchnetworking.techtarget.com/sDefinition/0,,sid7_gci212725,00.html), and servlet (http://searchdatabase.techtarget.com/sDefinition/0,,sid13_gci212966,00.html), although it is somewhat peculiar to see them used together that way.

One thing that might help you is to run the SQL profiler overnight to see who/what connects to your server. That will at least give you a few "breadcrumbs" to start from!

Another "high probability" place to check is the SQL Agent running on the SQL Server. It is quite easy to schedule scripts (and many other things) to run as needed against your SQL server or other machines.

-PatP|||I have check the sql server agent nothing.

I will try profiler overnight.

Since servlet--is a small program that runs on a server, maybe the scripts are running from there?

Thanks

Lystra|||If there was nothing in the SQL Agent, the servlet would be my next guess. Do any of the network/admin/IT types have any kind of documentation for this system whatsoever? It sounds to me like you are the new kid on the block, being sent out to clean up a runaway freight train that has been careening unattended through the office for quite some time!

-PatP|||Yup, you can't be more right. This is my three week at this job. I could tell you the horror stories from the first week.

But I have to admit I love this job because it is pushing me to be a better dba. My last job was a contractor for the government and I was not able to use my troubleshooting skills to the fullest. Here I have to.

Lystra|||A friend of mine is in a similar situation in the DC area. She's been developing MS-Access for one of the government's largest construction contractors for an age. She's reached the point where she wants to go further than they are willing/able to manage, and she's trying to figure out what her next step should be...

Unfortunately, I've been out of the DC area for too long, so I've really lost touch with the IT/business community there. Oh well, can't win them all!

-PatP|||It's pretty much the same as you have left it.

Nothing have change.

Lystra

remote query

i am trying to do a remote query and when I run the query
it gives me this:
login failed for user '(null)'. Reason: Not associated
with a trusted SQL Server connection
My query statement
select * from openquery(server, 'select[table]
from database')
any help would be niceIt looks like a problem with how you have the security
mapping configured for your linked server. Make sure you
have this configured correctly with a valid login, password,
etc. You can find more information in books online under
linked servers.
-Sue
On Tue, 7 Oct 2003 13:36:32 -0700, "Jamie Elliott"
<jelliott@.alexlee.com> wrote:
>i am trying to do a remote query and when I run the query
>it gives me this:
>login failed for user '(null)'. Reason: Not associated
>with a trusted SQL Server connection
>My query statement
>select * from openquery(server, 'select[table]
>from database')
>any help would be nice|||Hi Jamie,
I agree with Sue. If you have Enterprise Manager, it is better to change
the security mapping in Security tab in linked server Properties. For
example, I would use a SQL login (allow that linked server to accept SQL
authentication) that can access linked SQL Server and select "Be made using
this security context", input the SQL login and password.
Bill Cheng
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
--
| Content-Class: urn:content-classes:message
| From: "Jamie Elliott" <jelliott@.alexlee.com>
| Sender: "Jamie Elliott" <jelliott@.alexlee.com>
| Subject: remote query
| Date: Tue, 7 Oct 2003 13:36:32 -0700
| Lines: 11
| Message-ID: <055701c38d12$b1c82ec0$a301280a@.phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcONErHIaJzjVVOxSfOfBlXPy1QDEQ==| Newsgroups: microsoft.public.sqlserver.server
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.server:310079
| NNTP-Posting-Host: TK2MSFTNGXA11 10.40.1.163
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| i am trying to do a remote query and when I run the query
| it gives me this:
|
| login failed for user '(null)'. Reason: Not associated
| with a trusted SQL Server connection
|
| My query statement
| select * from openquery(server, 'select[table]
| from database')
|
| any help would be nice
|

Remote queries using sp_executesql run inconsistently

This one has stumped me!
I recently implemented a process to monitor database usage and growth
on our production servers. I use on server as the "master" that
collects data from all the other servers into one database. The
problem I'm having is that only every other day the process completes
after having successfully collected data from all servers. On the
alternate days, only data from the "master" server is collected. I've
used some debugging code to determine that my process is successfully
communicating with each server each day, but I can reliably plan on the
every-other-day behavior.
I apologize if this explanantion is too vague. Here is some code...
This is the SP on the "master" server that contacts all the other
servers and collects the data (this is within a cursor that loops
through the list of server names as stored in a local table):
-- Creates the generic linked server
select @.svrlgn = lower(left(@.svr_nm, @.svr_nm_len))
exec sp_addlinkedserver 'MSSQL', '', 'SQLOLEDB', @.svr_nm
exec sp_addlinkedsrvlogin 'MSSQL', 'false', null, @.svrlgn, @.svrlgn
exec sp_serveroption 'MSSQL', 'rpc', 'true'
exec sp_serveroption 'MSSQL', 'rpc out', 'true'
set @.sqlstr = 'insert into temp_drives (DriveLetter, MBFree) exec
MSSQL.master..xp_fixeddrives; update temp_drives set ServerName = ''' +
@.svr_nm + ''' where ServerName = ''new'''
execute sp_executesql @.sqlstr
set @.sqlstr = 'exec master.dbo.mjr_GetDatabaseSize_Data'
execute MSSQL.master.dbo.sp_executesql @.sqlstr
-- clean-up
exec sp_droplinkedsrvlogin 'MSSQL',null
exec sp_dropserver 'MSSQL'Still reviewing your code, but just wondering why are you adding and
dropping links to the remote servers each time you run the job? Why not
just permanently link the servers?
Will get back to you on the rest when I can review your code in more detail.
Thx
"vogelm" <vogelm@.discussions.microsoft.com> wrote in message
news:1B4E5251-D928-4156-A19D-41F24C745456@.microsoft.com...
> This one has stumped me!
>
> I recently implemented a process to monitor database usage and growth
> on our production servers. I use on server as the "master" that
> collects data from all the other servers into one database. The
> problem I'm having is that only every other day the process completes
> after having successfully collected data from all servers. On the
> alternate days, only data from the "master" server is collected. I've
> used some debugging code to determine that my process is successfully
> communicating with each server each day, but I can reliably plan on the
> every-other-day behavior.
>
> I apologize if this explanantion is too vague. Here is some code...
>
> This is the SP on the "master" server that contacts all the other
> servers and collects the data (this is within a cursor that loops
> through the list of server names as stored in a local table):
>
> -- Creates the generic linked server
> select @.svrlgn = lower(left(@.svr_nm, @.svr_nm_len))
>
> exec sp_addlinkedserver 'MSSQL', '', 'SQLOLEDB', @.svr_nm
> exec sp_addlinkedsrvlogin 'MSSQL', 'false', null, @.svrlgn, @.svrlgn
> exec sp_serveroption 'MSSQL', 'rpc', 'true'
> exec sp_serveroption 'MSSQL', 'rpc out', 'true'
>
> set @.sqlstr = 'insert into temp_drives (DriveLetter, MBFree) exec
> MSSQL.master..xp_fixeddrives; update temp_drives set ServerName = ''' +
> @.svr_nm + ''' where ServerName = ''new'''
>
> execute sp_executesql @.sqlstr
>
> set @.sqlstr = 'exec master.dbo.mjr_GetDatabaseSize_Data'
> execute MSSQL.master.dbo.sp_executesql @.sqlstr
>
> -- clean-up
> exec sp_droplinkedsrvlogin 'MSSQL',null
> exec sp_dropserver 'MSSQL'
>|||We would prefer not to leave permanent linked servers out our servers if not
for a specific database or purpose; we've found that developers can sometime
s
abuse them. Also, the dynamic nature of the script allows us to add and
remove servers from the process more easily.
Thanks for reviewing my code. I look forward to your feedback!
"Michael C#" wrote:

> Still reviewing your code, but just wondering why are you adding and
> dropping links to the remote servers each time you run the job? Why not
> just permanently link the servers?
> Will get back to you on the rest when I can review your code in more detai
l.
> Thx
> "vogelm" <vogelm@.discussions.microsoft.com> wrote in message
> news:1B4E5251-D928-4156-A19D-41F24C745456@.microsoft.com...
>
>|||Nothing's jumping out at me, other than you're not fully-qualifying all of
the tables (i.e., temp_drives). Are you seeing anything in your Event Logs
on either the local computer or remote linked servers? My best guess would
be a security/login failure on the remote machine, but you'd have to check
the logs for that. Could be that the commands are timing out, for instance
if you're running intensive operations every other day like backups and
index rebuilds, etc. Look for any other activities that are occurring on
your server on days of failure. It might end up just being a case of
scheduling the job to run earlier or later in the day.
There might be additional info in the SQL Server Logs (under "Management" in
EM).
Let me know if you see anything in your logs.
"vogelm" <vogelm@.discussions.microsoft.com> wrote in message
news:B4EDC587-A45D-4FBE-9F28-F3C2FE46A7E1@.microsoft.com...
> We would prefer not to leave permanent linked servers out our servers if
> not
> for a specific database or purpose; we've found that developers can
> sometimes
> abuse them. Also, the dynamic nature of the script allows us to add and
> remove servers from the process more easily.
> Thanks for reviewing my code. I look forward to your feedback!
>
> "Michael C#" wrote:
>|||No, nothing in the event logs. The security is set up correctly. It could
be a timeout issue, but I would assume that I'd receive an error message in
that case.
Also, there are no other long-running jobs during this time, and no
processes that run only every other day.
I'm going to be adding a bit more code to the process this w, so
hopefully my additional testing will help to reveal the answer.
Thanks for your help
"Michael C#" wrote:

> Nothing's jumping out at me, other than you're not fully-qualifying all of
> the tables (i.e., temp_drives). Are you seeing anything in your Event Log
s
> on either the local computer or remote linked servers? My best guess woul
d
> be a security/login failure on the remote machine, but you'd have to check
> the logs for that. Could be that the commands are timing out, for instanc
e
> if you're running intensive operations every other day like backups and
> index rebuilds, etc. Look for any other activities that are occurring on
> your server on days of failure. It might end up just being a case of
> scheduling the job to run earlier or later in the day.
> There might be additional info in the SQL Server Logs (under "Management"
in
> EM).
> Let me know if you see anything in your logs.
> "vogelm" <vogelm@.discussions.microsoft.com> wrote in message
> news:B4EDC587-A45D-4FBE-9F28-F3C2FE46A7E1@.microsoft.com...
>
>|||Did you find a resolution on this?
"vogelm" <vogelm@.discussions.microsoft.com> wrote in message
news:277700A6-9FDD-44E7-847B-EF51E572387A@.microsoft.com...
> No, nothing in the event logs. The security is set up correctly. It
> could
> be a timeout issue, but I would assume that I'd receive an error message
> in
> that case.
> Also, there are no other long-running jobs during this time, and no
> processes that run only every other day.
> I'm going to be adding a bit more code to the process this w, so
> hopefully my additional testing will help to reveal the answer.
> Thanks for your help
> "Michael C#" wrote:
>|||No, not yet. This is only something I can work on when I have all my other
"regular" work done. :-(
"Michael C#" wrote:

> Did you find a resolution on this?
> "vogelm" <vogelm@.discussions.microsoft.com> wrote in message
> news:277700A6-9FDD-44E7-847B-EF51E572387A@.microsoft.com...
>
>

Remote profiling

I keep reading how you are supposed to run traces from a remote server, but I
don't see any way to do that using sp_trace_create. Can this only be done by
running SQL Profiler from the remove server?
Thanks,
Brandon
Where do you see this advice and what exactly do you mean by "run traces
from a remote server"? sp_trace_create like any sp will be run on the
server you are connected to regardless of where the client app is that
issued the statement. The preferred way to create the trace is to have it
output directly to a file on a locally attached drive (not a network share).
It does not matter where you start the trace from just where the file will
be. If you run Profiler this is different. It is a client app but requires
the trace information be sent back to the client for display and processing.
This can be very expensive in some cases and should only be used on light
loads or small periods of time. You can always take the file produced from
sp_trace_create and load it into profiler anywhere you like with no impact
on the server other than what it takes to copy the file to the client.
Andrew J. Kelly SQL MVP
"Brandon Lilly" <avarice@.nospam_swbell.net> wrote in message
news:AF8A2C1F-75AB-4F30-8951-433BB13EA988@.microsoft.com...
>I keep reading how you are supposed to run traces from a remote server, but
>I
> don't see any way to do that using sp_trace_create. Can this only be done
> by
> running SQL Profiler from the remove server?
> Thanks,
> Brandon
|||Is it possible to load the profiler client app on a system running SQL 2005
Express?
Thanks
Clyde
"Andrew J. Kelly" wrote:

> Where do you see this advice and what exactly do you mean by "run traces
> from a remote server"? sp_trace_create like any sp will be run on the
> server you are connected to regardless of where the client app is that
> issued the statement. The preferred way to create the trace is to have it
> output directly to a file on a locally attached drive (not a network share).
> It does not matter where you start the trace from just where the file will
> be. If you run Profiler this is different. It is a client app but requires
> the trace information be sent back to the client for display and processing.
> This can be very expensive in some cases and should only be used on light
> loads or small periods of time. You can always take the file produced from
> sp_trace_create and load it into profiler anywhere you like with no impact
> on the server other than what it takes to copy the file to the client.
> --
> Andrew J. Kelly SQL MVP
>
> "Brandon Lilly" <avarice@.nospam_swbell.net> wrote in message
> news:AF8A2C1F-75AB-4F30-8951-433BB13EA988@.microsoft.com...
>
>

Remote Executiong - SSIS

All,

Is it possible to run the ssis package from a remote box?

The SSIS package will be stored in a sql server (open for suggestions on this) . We have a seperate box which has a 3rd party scheduler application. All our current scheduled jobs are ran from this box. we want the ssis packages also to be called from this box, as it will be easier to maintain and keep track of the jobs running.

So, we want the SSIS package to be called from this scheduler box. Any ideas?

Thanks

You can create a job without schedule on SQL box, then invoke this job at the time defined by your own scheduler (e.g. start osql.exe to run sp_start_job).

http://blogs.msdn.com/michen/archive/2007/03/22/running-ssis-package-programmatically.aspx

|||

If I install the client tools for Sql Server 2005 in the scheduler box, will i be able to run the package from that box itself using DTEXEC?

The problem I see with sp_start_job is that, it looks it will just start the job and report a success as long as the job gets started. If the job fails during execution we will still not know anything about it and I cannot have a dependency of jobs based on that.

|||

Karunakaran wrote:

If I install the client tools for Sql Server 2005 in the scheduler box, will i be able to run the package from that box itself using DTEXEC?

Yes, but that box will require a SQL Server license.|||

Another question on the same lines, let me know if I need to post this in a seperate thread.

I write a console application referencing dts runtime classes, and I invoke the package from the console app. Now If I deploy this console application in a box where ssis is not installed, but .NET framework is installed will this work? or is it against the licensing terms?

Thanks
Karunakaran

|||

Karunakaran wrote:

Another question on the same lines, let me know if I need to post this in a seperate thread.

I write a console application referencing dts runtime classes, and I invoke the package from the console app. Now If I deploy this console application in a box where ssis is not installed, but .NET framework is installed will this work? or is it against the licensing terms?

Thanks
Karunakaran

No. SSIS runtime components are not redistributable. You'll need to install SSIS on that box, and that will require a license.|||Thanks for the clarifications, Phil.

Remote Error Problem

Hi all,
I created a report that uses resultset generated from integration service. I managed to run the report on BIDS and also by command prompt on both server pc and remote pc. (I created the report from remote pc and deploy the report from remote pc also). When I try to run the report from report server, the following error came up (I already enable remote errors):

An error has occurred during report processing.

Cannot create a connection to data source 'SSIS'.

5 Anyone have any idea how to solve it? or anywhere that I can find the meaning of the 5 below the error message? Thanks in advance.
Daren
Hi all,
Sorry to post another message here. Just to touch up on my question above. I create a custom data source to SSIS in Report Server and use Windows Integrated Security. Then the error occurs.
Daren
|||Nobody knows about this error?
Daren
|||Have you looked at the logfiles?
\Program Files\Microsoft SQL Server\MSSQL.[x]\Reporting Services\LogFiles
The logfiles get really big and complex, so the best way is to stop IIS and Reporting Services, move or delete the old logfiles, restart the IIS and Reporting Services, run your report and look into the logfiles. Usually you can find a bit more verbose Errormessages there.

|||Hi BenniG,
Sorry I took so long to reply, I managed to browse through the log and found the following content:
w3wp!processing!7!5/18/2006-09:27:24:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'., ;
Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
at MgdParser.CreatePackage(Boolean bNeutral, Boolean bRemote)
at Microsoft.SqlServer.Dts.DtsClient.DtsConnection.Open()
at Microsoft.ReportingServices.DataExtensions.ConnectionWrapper.Open()
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource dataSourceObj, ReportProcessingContext pc)
End of inner exception stack trace
w3wp!processing!7!5/18/2006-09:27:25:: e ERROR: Data source 'SSIS': An error has occurred. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
w3wp!processing!7!5/18/2006-09:27:25:: e ERROR: An exception has occurred in data source 'SSIS'. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
w3wp!processing!7!5/18/2006-09:27:25:: i INFO: Merge abort handler called for ID=-1. Aborting data sources ...
w3wp!processing!7!5/18/2006-09:27:25:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing., ;
Info: Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. > Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
End of inner exception stack trace
w3wp!webserver!7!05/18/2006-09:27:25:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: An error has occurred during report processing. > Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. > Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
But I still do not get what does System.ApplicationException: 5 means. Do you know anywhere that I can find the description of error #5 stated in the log or report server?
Daren
|||Can you post these messages to the SSIS forum? You should be able to get a better response there.|||ok. Thanks Tudor.
Daren

Remote Error Problem

Hi all,
I created a report that uses resultset generated from integration service. I managed to run the report on BIDS and also by command prompt on both server pc and remote pc. (I created the report from remote pc and deploy the report from remote pc also). When I try to run the report from report server, the following error came up (I already enable remote errors):

An error has occurred during report processing.

Cannot create a connection to data source 'SSIS'.

5 Anyone have any idea how to solve it? or anywhere that I can find the meaning of the 5 below the error message? Thanks in advance.
Darenanyone know the solution to it?
Daren

Remote Error Problem

Hi all,
I created a report that uses resultset generated from integration service. I managed to run the report on BIDS and also by command prompt on both server pc and remote pc. (I created the report from remote pc and deploy the report from remote pc also). When I try to run the report from report server, the following error came up (I already enable remote errors):

An error has occurred during report processing.

Cannot create a connection to data source 'SSIS'.

5 Anyone have any idea how to solve it? or anywhere that I can find the meaning of the 5 below the error message? Thanks in advance.
Daren
Hi all,
Sorry to post another message here. Just to touch up on my question above. I create a custom data source to SSIS in Report Server and use Windows Integrated Security. Then the error occurs.
Daren
|||Nobody knows about this error?
Daren
|||Have you looked at the logfiles?
\Program Files\Microsoft SQL Server\MSSQL.[x]\Reporting Services\LogFiles
The logfiles get really big and complex, so the best way is to stop IIS and Reporting Services, move or delete the old logfiles, restart the IIS and Reporting Services, run your report and look into the logfiles. Usually you can find a bit more verbose Errormessages there.

|||Hi BenniG,
Sorry I took so long to reply, I managed to browse through the log and found the following content:
w3wp!processing!7!5/18/2006-09:27:24:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'., ;
Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
at MgdParser.CreatePackage(Boolean bNeutral, Boolean bRemote)
at Microsoft.SqlServer.Dts.DtsClient.DtsConnection.Open()
at Microsoft.ReportingServices.DataExtensions.ConnectionWrapper.Open()
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource dataSourceObj, ReportProcessingContext pc)
End of inner exception stack trace
w3wp!processing!7!5/18/2006-09:27:25:: e ERROR: Data source 'SSIS': An error has occurred. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
w3wp!processing!7!5/18/2006-09:27:25:: e ERROR: An exception has occurred in data source 'SSIS'. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
w3wp!processing!7!5/18/2006-09:27:25:: i INFO: Merge abort handler called for ID=-1. Aborting data sources ...
w3wp!processing!7!5/18/2006-09:27:25:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing., ;
Info: Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. > Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
End of inner exception stack trace
w3wp!webserver!7!05/18/2006-09:27:25:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: An error has occurred during report processing. > Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. > Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'SSIS'. > System.ApplicationException: 5
But I still do not get what does System.ApplicationException: 5 means. Do you know anywhere that I can find the description of error #5 stated in the log or report server?
Daren
|||Can you post these messages to the SSIS forum? You should be able to get a better response there.|||ok. Thanks Tudor.
Daren

Remote Debugging in SSIS ?

Hello

I've just heard that Remote Debugging should be possible in SSIS, but how ?

Some of the projects we run require a lot of memory and it's sometimes slow to debug on the local machine ?

Yes i know i can reduce the input rows, but in some cases i need all the data for testing.

Does anyone know how to remote debug ?

Do you have Visual Studio installed?

-Satya SKJ

SQL Server MVP

|||Yes|||And then ?|||

cgpl,

Just to clarify, by remote debugging I assume you mean that you want to make a package execute on a remote machine whilst seeing things turn green/yellow/red on your local machine. Is that correct?

As far as I know, that isn't possible. But don't take my word for it. Where did you hear that it WAS possible?

-Jamie

|||

green/yellow/red yes

We had a meeting with Kevin Cox from Microsoft who told that remote debugging was possible (the way i understood it). Don't know if you know him, but he told that he would look in to it.

|||

No, I haven't heard of Kevin. if you hear anything back I'd be keen to hear it as well.

TIA

-Jamie

|||SSIS does not implement remote debugging. It was considered, but it was too costly to do. Maybe in the next version, if we'll have time.|||If possible, core be able to debug a script component task too...|||

We would appreciate if this could be considered as 'must have' functionallity. As we experience great disadvantages from not being able to remotely debug our ssis packages. Now we have to invest in more memory or servers to be able to provide our ssis development team with good performance. For each remote desktop session we will need to provide 1 gb of memory (visual studio, ssms, desktop etc) + memory for sql server 2005. When working with 8 ssis developers we would need 16gb + memory on our development server. Informatica/Business Obects/Oracle Warehouse builder all provide client/server development scenario's. Hopefully Microsoft will consider this functionallity as important for a new release of ssis.

Marc

|||

MarcvdW wrote:

We would appreciate if this could be considered as 'must have' functionallity. As we experience great disadvantages from not being able to remotely debug our ssis packages. Now we have to invest in more memory or servers to be able to provide our ssis development team with good performance. For each remote desktop session we will need to provide 1 gb of memory (visual studio, ssms, desktop etc) + memory for sql server 2005. When working with 8 ssis developers we would need 16gb + memory on our development server. Informatica/Business Obects/Oracle Warehouse builder all provide client/server development scenario's. Hopefully Microsoft will consider this functionallity as important for a new release of ssis.

Marc

Marc,

If you want this then the place to ask for it is http://connect.microsoft.com/sqlserver/feedback

-Jamie

|||Thanks Jamie, I wasn't aware of this option. I posted my feedback.|||

MarcvdW wrote:

Thanks Jamie, I wasn't aware of this option. I posted my feedback.

cool. Could you put the link up here? The more people that add their weight to it the more likely it is to happen. I will certainly add some comments.

|||

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=262144

Here it is.

Marc

Remote Debugging in SSIS ?

Hello

I've just heard that Remote Debugging should be possible in SSIS, but how ?

Some of the projects we run require a lot of memory and it's sometimes slow to debug on the local machine ?

Yes i know i can reduce the input rows, but in some cases i need all the data for testing.

Does anyone know how to remote debug ?

Do you have Visual Studio installed?

-Satya SKJ

SQL Server MVP

|||Yes|||And then ?|||

cgpl,

Just to clarify, by remote debugging I assume you mean that you want to make a package execute on a remote machine whilst seeing things turn green/yellow/red on your local machine. Is that correct?

As far as I know, that isn't possible. But don't take my word for it. Where did you hear that it WAS possible?

-Jamie

|||

green/yellow/red yes

We had a meeting with Kevin Cox from Microsoft who told that remote debugging was possible (the way i understood it). Don't know if you know him, but he told that he would look in to it.

|||

No, I haven't heard of Kevin. if you hear anything back I'd be keen to hear it as well.

TIA

-Jamie

|||SSIS does not implement remote debugging. It was considered, but it was too costly to do. Maybe in the next version, if we'll have time.|||If possible, core be able to debug a script component task too...|||

We would appreciate if this could be considered as 'must have' functionallity. As we experience great disadvantages from not being able to remotely debug our ssis packages. Now we have to invest in more memory or servers to be able to provide our ssis development team with good performance. For each remote desktop session we will need to provide 1 gb of memory (visual studio, ssms, desktop etc) + memory for sql server 2005. When working with 8 ssis developers we would need 16gb + memory on our development server. Informatica/Business Obects/Oracle Warehouse builder all provide client/server development scenario's. Hopefully Microsoft will consider this functionallity as important for a new release of ssis.

Marc

|||

MarcvdW wrote:

We would appreciate if this could be considered as 'must have' functionallity. As we experience great disadvantages from not being able to remotely debug our ssis packages. Now we have to invest in more memory or servers to be able to provide our ssis development team with good performance. For each remote desktop session we will need to provide 1 gb of memory (visual studio, ssms, desktop etc) + memory for sql server 2005. When working with 8 ssis developers we would need 16gb + memory on our development server. Informatica/Business Obects/Oracle Warehouse builder all provide client/server development scenario's. Hopefully Microsoft will consider this functionallity as important for a new release of ssis.

Marc

Marc,

If you want this then the place to ask for it is http://connect.microsoft.com/sqlserver/feedback

-Jamie

|||Thanks Jamie, I wasn't aware of this option. I posted my feedback.|||

MarcvdW wrote:

Thanks Jamie, I wasn't aware of this option. I posted my feedback.

cool. Could you put the link up here? The more people that add their weight to it the more likely it is to happen. I will certainly add some comments.

|||

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=262144

Here it is.

Marc

Remote Debugging in SSIS ?

Hello

I've just heard that Remote Debugging should be possible in SSIS, but how ?

Some of the projects we run require a lot of memory and it's sometimes slow to debug on the local machine ?

Yes i know i can reduce the input rows, but in some cases i need all the data for testing.

Does anyone know how to remote debug ?

Do you have Visual Studio installed?

-Satya SKJ

SQL Server MVP

|||Yes|||And then ?|||

cgpl,

Just to clarify, by remote debugging I assume you mean that you want to make a package execute on a remote machine whilst seeing things turn green/yellow/red on your local machine. Is that correct?

As far as I know, that isn't possible. But don't take my word for it. Where did you hear that it WAS possible?

-Jamie

|||

green/yellow/red yes

We had a meeting with Kevin Cox from Microsoft who told that remote debugging was possible (the way i understood it). Don't know if you know him, but he told that he would look in to it.

|||

No, I haven't heard of Kevin. if you hear anything back I'd be keen to hear it as well.

TIA

-Jamie

|||SSIS does not implement remote debugging. It was considered, but it was too costly to do. Maybe in the next version, if we'll have time.|||If possible, core be able to debug a script component task too...|||

We would appreciate if this could be considered as 'must have' functionallity. As we experience great disadvantages from not being able to remotely debug our ssis packages. Now we have to invest in more memory or servers to be able to provide our ssis development team with good performance. For each remote desktop session we will need to provide 1 gb of memory (visual studio, ssms, desktop etc) + memory for sql server 2005. When working with 8 ssis developers we would need 16gb + memory on our development server. Informatica/Business Obects/Oracle Warehouse builder all provide client/server development scenario's. Hopefully Microsoft will consider this functionallity as important for a new release of ssis.

Marc

|||

MarcvdW wrote:

We would appreciate if this could be considered as 'must have' functionallity. As we experience great disadvantages from not being able to remotely debug our ssis packages. Now we have to invest in more memory or servers to be able to provide our ssis development team with good performance. For each remote desktop session we will need to provide 1 gb of memory (visual studio, ssms, desktop etc) + memory for sql server 2005. When working with 8 ssis developers we would need 16gb + memory on our development server. Informatica/Business Obects/Oracle Warehouse builder all provide client/server development scenario's. Hopefully Microsoft will consider this functionallity as important for a new release of ssis.

Marc

Marc,

If you want this then the place to ask for it is http://connect.microsoft.com/sqlserver/feedback

-Jamie

|||Thanks Jamie, I wasn't aware of this option. I posted my feedback.|||

MarcvdW wrote:

Thanks Jamie, I wasn't aware of this option. I posted my feedback.

cool. Could you put the link up here? The more people that add their weight to it the more likely it is to happen. I will certainly add some comments.

|||

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=262144

Here it is.

Marc

Remote Connections using SQL Server 2005 Developers Enterprise Edition

I have a problem. I am using the developers version of SQL Server Enterprise edition.

I am trying to run a command in MS command prompt:

Aspnet_regsql -E -S localhost -ssadd -sstype p

After I execute this command, I receive a Name Pipe
error that under the default settings, SQL Server
doesn't allow remote connections. I took some steps
to try to resolve the problem:

1) I googled the interrnet to see if there was any one
else who ran into the same problem and if there was a
quick resolution.

2) I check SQL Server Books on line about SQL server
configuration manager and how to enable remote
connections using Name Pipes and TCP/IP.

3) I used C:\WINDOWS\system32\cliconfg.exe to enable
Name Pipes and TCPIP to be enable on the client.

4) I enabled SQl Server Browser to help me with my
problem

5) I stopped the Database engine, enable local and
remote connections using Name pipes and TCP/IP,then I
restarted the database engine along with SQl server
Agent.

6) I did check SQl Server error logs to see what port
it was listening on , but I thought that SQl Server
was suppose to listen on port 1433 by default, and
Name pipes /SQL/query.

7)I have check the error logs to see what port that SQL Server was listening to
and trying to use the port number in the client config utility. I am still getting the same error.

8) I tried to remove name pipes in the SQL Server Surface Manager and allow local and remote connections using only TCP/IP. I still get the same error. I did stop and restarted the Database Engine.

What steps have I not taken , and what should I do to correct this problem?

Hi,

have you refered below links?

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

http://support.microsoft.com/kb/914277/en-us

Hemantgiri S. Goswami

|||

Hi Hemantgiri,

Thank you for your reply.

I have reviewed the links that you recommended. I have completed most of the steps recommended. I am using a different firewall than Windows, and I will have to contact ZoneAlarm to receive more information about adding exceptions for SQL Server and SQL Server Browser. Usually, ZoneAlarm notify me to allow certain transactions to occur on my machine. I will ask the technical service people at ZoneAlarm why ZoneAlarm firewall was not informing me that it was blocking a remote connection to SQL Server from this machine. When I receive my requested information from ZoneAlarm and apply it to my firewall, I will let you know what happen next.

|||

Hi again,

I have taken the following steps to see if ZoneAlarm was presenting a problem. Please note that I have not heard from ZoneAlarm yet. I removed my wireless network card that I am using to conect to the internet. I disabled my ZoneAlarm and Windows firewall. I followed the steps in the article that was more focused on SQL Server Developer since I am not using SQL Express. I executed the command I mentioned earlier to see if I could connect to SQL Server remotely with out any firewall interference. I could not,and I received the same error. I did look at the other article that was more SQLExpress focused, but I am not sure how I would apply some commands in that article to SQL Server Developer. I have used the SQL Server Surface Configration to enable local and remote settings and using TCP/IP and Name Pipes. It shows that the radio buttons for both are selected, so I know that those choices are selected. As far as selecting a port, I am asking you what would be the SQLCMD command version for SQL Developer? The one for SQL Express is stated in the article, is there a similar one that I can use for SQL Developer? I tried to set the port using clientconfig.exe but that doesn't seem to work.

|||

Hi,

AFAIK their is no difference for the editions , you can perform the same steps.

Hemantgiri S. Goswami

|||

Hi everyone,

I am still looking into this situation. I do not know what to run the SQLCMD for SQL Developer. One article has it for SQL Express : SQLCMD -E -S YourServer\SQLEXPRESS,port #. My question is would I enter SQLCMD -E -S myserver\SQLDEVELOPER,port# or is there another way to state this?

|||

Hi everyone,

I have uninstalled the version of SQL Server 2005 and used an advanced version of SQL Express 2005. I have been successful in configuring remote connections and enabling Named Pipes and TCP/IP using this version. Even though I was not told by the previous version of SQL server 2005, I think that I did not correctly add myself to the Admin group to have the rights to change from local to local /remote connections and enable Named Pipes and TCP/IP. I will test my theory when I install my Standard edition of SQL Server 2005 during May or June.

I would like to thank everyone who replied to my post or who thought hard on a solution to my problem, but have not replied at this time.

Remote Connections using SQL Server 2005 Developers Enterprise Edition

I have a problem. I am using the developers version of SQL Server Enterprise edition.

I am trying to run a command in MS command prompt:

Aspnet_regsql -E -S localhost -ssadd -sstype p

After I execute this command, I receive a Name Pipe
error that under the default settings, SQL Server
doesn't allow remote connections. I took some steps
to try to resolve the problem:

1) I googled the interrnet to see if there was any one
else who ran into the same problem and if there was a
quick resolution.

2) I check SQL Server Books on line about SQL server
configuration manager and how to enable remote
connections using Name Pipes and TCP/IP.

3) I used C:\WINDOWS\system32\cliconfg.exe to enable
Name Pipes and TCPIP to be enable on the client.

4) I enabled SQl Server Browser to help me with my
problem

5) I stopped the Database engine, enable local and
remote connections using Name pipes and TCP/IP,then I
restarted the database engine along with SQl server
Agent.

6) I did check SQl Server error logs to see what port
it was listening on , but I thought that SQl Server
was suppose to listen on port 1433 by default, and
Name pipes /SQL/query.

7)I have check the error logs to see what port that SQL Server was listening to
and trying to use the port number in the client config utility. I am still getting the same error.

8) I tried to remove name pipes in the SQL Server Surface Manager and allow local and remote connections using only TCP/IP. I still get the same error. I did stop and restarted the Database Engine.

What steps have I not taken , and what should I do to correct this problem?

Hi,

have you refered below links?

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

http://support.microsoft.com/kb/914277/en-us

Hemantgiri S. Goswami

|||

Hi Hemantgiri,

Thank you for your reply.

I have reviewed the links that you recommended. I have completed most of the steps recommended. I am using a different firewall than Windows, and I will have to contact ZoneAlarm to receive more information about adding exceptions for SQL Server and SQL Server Browser. Usually, ZoneAlarm notify me to allow certain transactions to occur on my machine. I will ask the technical service people at ZoneAlarm why ZoneAlarm firewall was not informing me that it was blocking a remote connection to SQL Server from this machine. When I receive my requested information from ZoneAlarm and apply it to my firewall, I will let you know what happen next.

|||

Hi again,

I have taken the following steps to see if ZoneAlarm was presenting a problem. Please note that I have not heard from ZoneAlarm yet. I removed my wireless network card that I am using to conect to the internet. I disabled my ZoneAlarm and Windows firewall. I followed the steps in the article that was more focused on SQL Server Developer since I am not using SQL Express. I executed the command I mentioned earlier to see if I could connect to SQL Server remotely with out any firewall interference. I could not,and I received the same error. I did look at the other article that was more SQLExpress focused, but I am not sure how I would apply some commands in that article to SQL Server Developer. I have used the SQL Server Surface Configration to enable local and remote settings and using TCP/IP and Name Pipes. It shows that the radio buttons for both are selected, so I know that those choices are selected. As far as selecting a port, I am asking you what would be the SQLCMD command version for SQL Developer? The one for SQL Express is stated in the article, is there a similar one that I can use for SQL Developer? I tried to set the port using clientconfig.exe but that doesn't seem to work.

|||

Hi,

AFAIK their is no difference for the editions , you can perform the same steps.

Hemantgiri S. Goswami

|||

Hi everyone,

I am still looking into this situation. I do not know what to run the SQLCMD for SQL Developer. One article has it for SQL Express : SQLCMD -E -S YourServer\SQLEXPRESS,port #. My question is would I enter SQLCMD -E -S myserver\SQLDEVELOPER,port# or is there another way to state this?

|||

Hi everyone,

I have uninstalled the version of SQL Server 2005 and used an advanced version of SQL Express 2005. I have been successful in configuring remote connections and enabling Named Pipes and TCP/IP using this version. Even though I was not told by the previous version of SQL server 2005, I think that I did not correctly add myself to the Admin group to have the rights to change from local to local /remote connections and enable Named Pipes and TCP/IP. I will test my theory when I install my Standard edition of SQL Server 2005 during May or June.

I would like to thank everyone who replied to my post or who thought hard on a solution to my problem, but have not replied at this time.