It has to be a trusted domain for Windows Authentication to work. Both computers must be able to authenticate logins at the same place. This also means that both computers...

@ identifies a variable, so SQL Server is confused when you are using at the beginning of a string.

The single quotes should work, but try this instead:

[@psuedo program]

-SQLBill

What does the UPDATE command look like?

What are the table fields/columns set as? Do the columns allow NULLs?

-SQLBill

You can use SQL Server's Profiler to run a trace.

You could create a trace that tracks the commands being run on the database, but be aware that this can...

For SQL Server to use Windows Authentication, it has to be with a trusted network. With the error you are getting, I would guess that the system you are on...

And once you get this issue solved and are back up and running...you need to decide if you need the transaction logs for recovery. If so, you need to back...

Only Enterprise Edition is Cluster-aware.  Check Microsoft's SQL Server website, for the description of the versions. Only Enterprise Edition says that it can be clustered.

-SQLBill

Yes, you can create a job to do this. But if you want it done regularly and don't care when it's done, set the database to AUTO SHRINK. (Enterprise Manager,...

 Please post in an appropriate forum. This forum (QOD or Question Of The Day) is strictly for discussing the Question of the Day. The QOD is a daily 'test'...

Do regular log backups.

-SQLBill

Maybe something like this:

CREATE PROCEDURE usp_runproc

   @procparam  INT

AS

   IF @procparam = 1

     BEGIN

       EXEC usp_procedure1

     END

   ELSE

   IF @procparam = 2

     BEGIN

       EXEC usp_procedure2

     END

   ELSE

   IF @procparam = 3

<Rest of...

Does it always happen after running the same amount of time? If so, it might be a timeout issue (I think timeout is the term).

I don't know where to find...

Are any of your inputs being CASTed longer than 30 characters? Default length for a VARCHAR when CAST is used is 30 characters.

-SQLBill

There's an even easier way to move database files. But you should still have them backed up first.

Detach the database(s). (You can use either Enterprise Manger - easiest or TSQL...

First: Data file size will NOT be the same as Database size. Data file is just that - the data itself. Database size is the size of the data file(s),...