Multiple instances

The Result:
Two people using the same computer running RS that connect to different
instances on the on the SQL computer, so that one person has no indication
that the other is present.
The Question:
How can I achieve the above result
The Plead:
All information regarding this problem is greatly appreciated.
The Closing:
Thank youIf they run only a report noone will ever see the other instance, or do you
want to decide at report level to which instacne the suer will connect to
during runtime ? Then you should use a stored procedure which evaluates the
destination while the user is quering the data and firing the appropiate
Query for this user.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"savvy95" <savvy95@.discussions.microsoft.com> schrieb im Newsbeitrag
news:BDCD5D89-595A-4D7B-917C-B6CF486A4E76@.microsoft.com...
> The Result:
> Two people using the same computer running RS that connect to different
> instances on the on the SQL computer, so that one person has no indication
> that the other is present.
> The Question:
> How can I achieve the above result
> The Plead:
> All information regarding this problem is greatly appreciated.
> The Closing:
> Thank you|||Yes -- I want to decide at report level to which instance the user will
connect to during runtime. My wish: To install RS 2 times on one server
using 2 SQL instances -- one RS1 "instance" uses SQL1 and RS2 uses SQL2, but
both SQL1 & SQL2 are on the same SQLBOX. Is THIS possible?
"Jens Sü�meyer" wrote:
> If they run only a report noone will ever see the other instance, or do you
> want to decide at report level to which instacne the suer will connect to
> during runtime ? Then you should use a stored procedure which evaluates the
> destination while the user is quering the data and firing the appropiate
> Query for this user.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
> "savvy95" <savvy95@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:BDCD5D89-595A-4D7B-917C-B6CF486A4E76@.microsoft.com...
> > The Result:
> > Two people using the same computer running RS that connect to different
> > instances on the on the SQL computer, so that one person has no indication
> > that the other is present.
> >
> > The Question:
> > How can I achieve the above result
> >
> > The Plead:
> > All information regarding this problem is greatly appreciated.
> >
> > The Closing:
> > Thank you
>
>|||I don't know about 2 instances of RS on the same box. You would have to
install to different URL's for each instance. And if you're going to have
different URL's, then you might as well use two different servers, or use
Virtual PC or VMware to get two virtual servers on the same physical box.
It sounds like all you really need is a report that sends UserId as a query
parameter, and a stored procedure that is smart enough to use the UserId to
query different data for different people. The "different data" in the query
could be separate SQL Server instances if you want.
HTH,
Ted
"savvy95" wrote:
> Yes -- I want to decide at report level to which instance the user will
> connect to during runtime. My wish: To install RS 2 times on one server
> using 2 SQL instances -- one RS1 "instance" uses SQL1 and RS2 uses SQL2, but
> both SQL1 & SQL2 are on the same SQLBOX. Is THIS possible?
> "Jens Sü�meyer" wrote:
> > If they run only a report noone will ever see the other instance, or do you
> > want to decide at report level to which instacne the suer will connect to
> > during runtime ? Then you should use a stored procedure which evaluates the
> > destination while the user is quering the data and firing the appropiate
> > Query for this user.
> >
> > HTH, Jens Suessmeyer.
> >
> > --
> > http://www.sqlserver2005.de
> > --
> >
> >
> > "savvy95" <savvy95@.discussions.microsoft.com> schrieb im Newsbeitrag
> > news:BDCD5D89-595A-4D7B-917C-B6CF486A4E76@.microsoft.com...
> > > The Result:
> > > Two people using the same computer running RS that connect to different
> > > instances on the on the SQL computer, so that one person has no indication
> > > that the other is present.
> > >
> > > The Question:
> > > How can I achieve the above result
> > >
> > > The Plead:
> > > All information regarding this problem is greatly appreciated.
> > >
> > > The Closing:
> > > Thank you
> >
> >
> >|||Thanks Ted K. and Jens Sü�meyer
I'm the IT guy, even though I know quite a bit about RS, the DBA will given
admin privileges (creating reports, users and setting permissions).
Presently there's another person in Business Intellegence who has the other
admin roll. That makes 2 Admin. My boss asked me to investigate the
possibility of not having to create another box with RS. Rather to find a
way to run 2 instances on the same box.
I will not be involved in installing RS and ensuring its operations. I told
my boss I didn't think there was a way to do what he wants, BUT I needed to
research it more. Your assistance has been greatly appreciated and has
confirmed my exploration into this matter as "not possible".
Mind you if I were the Admin, I would indeed take your advices and create
stored procedures.
Thanks again
"Ted K" wrote:
> I don't know about 2 instances of RS on the same box. You would have to
> install to different URL's for each instance. And if you're going to have
> different URL's, then you might as well use two different servers, or use
> Virtual PC or VMware to get two virtual servers on the same physical box.
> It sounds like all you really need is a report that sends UserId as a query
> parameter, and a stored procedure that is smart enough to use the UserId to
> query different data for different people. The "different data" in the query
> could be separate SQL Server instances if you want.
> HTH,
> Ted
> "savvy95" wrote:
> > Yes -- I want to decide at report level to which instance the user will
> > connect to during runtime. My wish: To install RS 2 times on one server
> > using 2 SQL instances -- one RS1 "instance" uses SQL1 and RS2 uses SQL2, but
> > both SQL1 & SQL2 are on the same SQLBOX. Is THIS possible?
> >
> > "Jens Sü�meyer" wrote:
> >
> > > If they run only a report noone will ever see the other instance, or do you
> > > want to decide at report level to which instacne the suer will connect to
> > > during runtime ? Then you should use a stored procedure which evaluates the
> > > destination while the user is quering the data and firing the appropiate
> > > Query for this user.
> > >
> > > HTH, Jens Suessmeyer.
> > >
> > > --
> > > http://www.sqlserver2005.de
> > > --
> > >
> > >
> > > "savvy95" <savvy95@.discussions.microsoft.com> schrieb im Newsbeitrag
> > > news:BDCD5D89-595A-4D7B-917C-B6CF486A4E76@.microsoft.com...
> > > > The Result:
> > > > Two people using the same computer running RS that connect to different
> > > > instances on the on the SQL computer, so that one person has no indication
> > > > that the other is present.
> > > >
> > > > The Question:
> > > > How can I achieve the above result
> > > >
> > > > The Plead:
> > > > All information regarding this problem is greatly appreciated.
> > > >
> > > > The Closing:
> > > > Thank you
> > >
> > >
> > >sql

Multiple FTP tasks that connect to same server at same time error

I have this job that download 4 files once a month from the same server. The files are sizable and I need to download them in less than 5 hours total. In 2000 I use an active x script to generate the ftp script then execute the script. all four files download at the same time in 4 different tasks with no issues.

I am rewrote the process in 2005 so that it uses the IS FTP function but when all 4 ftp tasks kick off they all fail... instantly. the initially shared the same FTP connection manager so I created different ones for each and still the same result

the error is one that relates to changing directories.... Now if I just run one of the tasks it runs fine it is just when more than one try to run at once. I ended up putting in 10 second delays between each ftp task kicking off and it works just fine...

Does this sound like a bug?

Also... I am on SQL 2005 Enterprise SP1 on Windows 2003 enterprise SP1.

I can also reproduce the problem when multiple FTP tasks share the same FTP connection manager. But everything works fine if I create individual FTP connection manager for each task. This does sound like a bug to me so I am going to log a bug issue. We will investigate the problem and address it ASAP. Thanks you|||Thanks...

Multiple connections in a CLR trigger

Hello

Is there nay way that it is possible to connect to another database within a trigger…

My scenario is that an update in a table in database X triggers several updates in a table in Database Y. The databases are on the same SQL Server

Thanks for any ideas, solutions or hints you can give me..!!!

Hi

I developed one solution like that Try Referencing server Y in server X wthi sp_addlinkedserver and then directly try to make the update like this

update servery.database.dbo.tabley set yfield=xfield

from serverx.database.dbo.tablex

|||

I tried the suggested function but i didn’t help and I still didn’t figure out how to make it work

Cheers

|||Did you try to just instatiate a new sqlconnection object using a normal connection string ? Make sure that you will need to grant a special trust level (external) to the assembly to make it work.

Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||

I did try to instantiate a new sqlconnection object. But I sadly I don't know about the trust level which you are talking about... Could you give me further information have I could grant the trust level to the assembly? It would be highly appreciated

Thanks

|||This would be a quick sample:

// Create Table Table1

//(

// SomeInt INT

//)

//INSERT INTO Table1 VALUES (1)

//EXEC sp_configure 'clr enabled' , '1'

//ALTER DATABASE Northwind SET TRUSTWORTHY ON

//RECONFIGURE

// Enter existing table or view for the target and uncomment the attribute line

[Microsoft.SqlServer.Server.SqlTrigger(Name = "Trigger1", Target = "Table1", Event = "FOR INSERT")]

public static void Trigger1()

{

SqlConnection conn = new SqlConnection("Data Source=.;Initial Catalog=master;Integrated Security=True");

SqlCommand cmd = new SqlCommand();

cmd.CommandType = CommandType.Text;

cmd.CommandText = "Select 1";

conn.Open();

cmd.ExecuteNonQuery();

}

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||Hi,
I think the “CLR Triggers for SQL Server 2005” article on
http://aspalliance.com/1273_CLR_Triggers_for_SQL_Server_2005.all
may be helpful in this discussion.

This popular white paper is written by a software engineer from our organization Mindfire Solutions (http://www.mindfiresolutions.com).

I hope you find it useful!

Cheers,
Byapti