linking two DASP databases

I have two SQL Server 2008 databases and am trying to create a link between the two.

If I try to create the link using Management Studio I get an error saying that I must be a member of the sysadmin role.

If I try to use sp_addlinkedserver I get a message saying that I do not have permission to perform the action

Any guidance would be much appreciated

Thanks

marc

 

Why not?

Sorry to revisit this, but is there a specific reason that DASP does not support linked databases on the server? I'd like to save a bit of money, which I can do if I can use a linked database.

Thanks

marc

 

I think you answered a big part of that question in your original post:

I'm not a DBA here (I will run this by our DBAs), but my guess is providing all the users of a shared database server access to sysadmin role would be less than ideal from a security/stability standpoint. There are no doubt other reasons as well that might not seem apparent from a user point of view.

There are several enterprise features of MS SQL that we can't offer, because they aren't meant for use on a shared server. MS SQL was designed as an enterprise (in-house) product from the outset, so using it in a shared environment has always meant that certain limitations are necessary.

I'll try to get a definitive answer for you, but generally speaking, most MS SQL features that we don't offer, we can't offer in our environment.

 

I don't think that it is necessary to give everyone sysadmin privileges; it can be done via a process under DASP control.

Right now it's frustrating because I have one database that I keep hitting the wall against, and another with significant space. Yes, I can change the application(s), but that takes some time and has an element of risk.