Running SQLSERVER2005 with SQLSERVER2000

Hi,
Is it possible to run SQL2000 on the same machine as 2005? Will there be any
major problems? Can it be done at all? Will they simply be treated as
seperate applications?
Thanks for your help on this.
AntHi,
You can run both in parellel, but make the memory static (FIX) for both
instances. As you said both will be running as seperate applications
(Thread) .
Thanks
Hari
"Ant" <Ant@.discussions.microsoft.com> wrote in message
news:C8C2BEE3-7F22-418F-B954-DEDEDCFFAE74@.microsoft.com...
> Hi,
> Is it possible to run SQL2000 on the same machine as 2005? Will there be
> any
> major problems? Can it be done at all? Will they simply be treated as
> seperate applications?
> Thanks for your help on this.
> Ant|||Ant wrote:
> Hi,
> Is it possible to run SQL2000 on the same machine as 2005? Will there be a
ny
> major problems? Can it be done at all? Will they simply be treated as
> seperate applications?
> Thanks for your help on this.
> Ant
Hi
As Hari has pointed out, there are no problems in running both versions
on a server. You just have to keep in mind that only one of them can be
a default instance - the other will have to be a named instance.
Regards
Steen Schlüter Persson
Database Administrator / System Administratorsql

Running SQLSERVER2005 with SQLSERVER2000

Hi,
Is it possible to run SQL2000 on the same machine as 2005? Will there be any
major problems? Can it be done at all? Will they simply be treated as
seperate applications?
Thanks for your help on this.
Ant
Hi,
You can run both in parellel, but make the memory static (FIX) for both
instances. As you said both will be running as seperate applications
(Thread) .
Thanks
Hari
"Ant" <Ant@.discussions.microsoft.com> wrote in message
news:C8C2BEE3-7F22-418F-B954-DEDEDCFFAE74@.microsoft.com...
> Hi,
> Is it possible to run SQL2000 on the same machine as 2005? Will there be
> any
> major problems? Can it be done at all? Will they simply be treated as
> seperate applications?
> Thanks for your help on this.
> Ant

Running SQLSERVER2005 with SQLSERVER2000

Hi,
Is it possible to run SQL2000 on the same machine as 2005? Will there be any
major problems? Can it be done at all? Will they simply be treated as
seperate applications?
Thanks for your help on this.
AntHi,
You can run both in parellel, but make the memory static (FIX) for both
instances. As you said both will be running as seperate applications
(Thread) .
Thanks
Hari
"Ant" <Ant@.discussions.microsoft.com> wrote in message
news:C8C2BEE3-7F22-418F-B954-DEDEDCFFAE74@.microsoft.com...
> Hi,
> Is it possible to run SQL2000 on the same machine as 2005? Will there be
> any
> major problems? Can it be done at all? Will they simply be treated as
> seperate applications?
> Thanks for your help on this.
> Ant|||Ant wrote:
> Hi,
> Is it possible to run SQL2000 on the same machine as 2005? Will there be any
> major problems? Can it be done at all? Will they simply be treated as
> seperate applications?
> Thanks for your help on this.
> Ant
Hi
As Hari has pointed out, there are no problems in running both versions
on a server. You just have to keep in mind that only one of them can be
a default instance - the other will have to be a named instance.
Regards
Steen Schlüter Persson
Database Administrator / System Administrator

Running SP with a different user

We are using SQL2000. User insert table in one database DB1 and trigger insert the record into another database DB2. In this scenario, is it possible have a trigger in DB1 to execute a stored procedure in DB2 with a different user?

try define trigger with execute as clause

CREATE TRIGGER YourNAme ON Yourtable
WITH EXECUTE AS 'CompanyDomain\SqlUser1'

AFTER INSERT, UPDATE AS.......

--call your procedure here

GO

Running SP with a different user

We are using SQL2000. User insert table in one database DB1 and trigger insert the record into another database DB2. In this scenario, is it possible have a trigger in DB1 to execute a stored procedure in DB2 with a different user?

I think you may use openrowset in the trigger to update the other database. it is not the best practice but it is the only solution I know

OPENROWSET('SQLOLEDB','ServerName';'user';'Password',

'SELECT * FROM pubs.dbo.authors ORDER BY au_lname, au_fname')|||

hello,

if you will be doing this most of the times

you might as well use the sp_addlinkserver options "useself" set to false to create a

linked server

Syntax
sp_addlinkedsrvlogin [ @.rmtsrvname = ] 'rmtsrvname'
[ , [ @.useself = ] 'useself' ]
[ , [ @.locallogin = ] 'locallogin' ]
[ , [ @.rmtuser = ] 'rmtuser' ]
[ , [ @.rmtpassword = ] 'rmtpassword' ]

by setting useself to false you can enter the desired username and password

regards

|||

USE DB1

Go

EXEC sp_

Trigger ON INSERT

USE DB2

Go

EXEC sp_

Adamus

|||i wish the new sp for 200 would allow "execute as" feature in 2k5|||

If this is in the trigger, is there any way I can run stored procedure with OpenRowSet and make trigger code invisible to the user who is inserting record since the password is there.
Thanks,