I did a google search on the error and several of the articles mentioned it being a security mapping issue.  Try mapping all users to a single 400 signon.

I'm just guessing now.  Do you have the latest client access and patches?  Have you tried deleting the datasource and recreating it.  Do you have the same datasource name on...

I'm assuming your using an ODBC datasource for your connection and the name of the datasource is LPUSA01.  If not the the syntax should be.

linkedserver.datasourcename.library.table

Try that.

Tom

Try:

select * from LPUSA01..EBSTSTNEW.BZRCRP

Tom

I never implied that you were not sufficiently protected against failures.  I think that your situation of dealing with a 500 gig database backup file to a unc share is...

I backup to unc shares on all of my production servers and haven't had a problem doing it for 4 years now.  I not only do it with my sql...

You'll also have to take the single tick off of hiday.  You've got the hiday default value commented out in the procedure definition.  I would also pass  values to the...

Are you having a performance problem with the database?

Sql databases do not need compacting like Access databases, because they are not flat file db's.  That being said, I'm assuming you're having a space issue with your database.  Either...

Try this.  It might be faster.

SELECT open_date,id

FROM AHDPROD.call_req

WHERE

(     priority in( 0,1,2)    

AND  active_flag = 1 AND type = 'I'    

AND ( assignee IS NOT NULL OR group_id...

It's the point at which the backup is finished.

Tom

One way to do it is to recreate the clustered index on the new file.  You should be able to go into manage indexes and change the location.  You could...

I would also suggest you increase the fillfactor on your clustered index build.  Assuming that as people sign up they are being added at the end of the index, based...

It has been a while, but I remember doing something similar and didn't set the space free up untill I re-indexed the tables that had datatype changes.  It ended up...

I would create an audit table and a trigger that writes out the row that's being changed along with the date.  That way you can do a quick search on...