Trystan

Please will you provide some sample date and expected results.  Do either of the two queries produce the desired output?  If so, why do you not want to use them...

If you can't change the stored procedure then I think your only option is to have the client side manipulate the result sets for you.

John

If you change your stored procedure as below, it should work.

John

-- Creating test procedure

CREATE

PROCEDURE sp_test

AS

It sounds like either disk E failed or was unavailable, or the path to the error log was incorrect, and so the SQL Server resources failed over to the other...

This means that SQL Server was stopped "gracefully" - either manually or by some process (scheduled job, maybe, or application of a service pack) that stops the service.  If the...

Jay

It doesn't use VB, but here's how I'd do it:

(1) Find the job under SQL Server Agent that starts your replication agent.

(2) Create a new job that does exactly the...

If you've got enough disk space, then you're better off dumping your database to disk and backing up the dump file to tape.  If you have to use the Arcserver...

Vidas

A few things here:

(1) It is OK to start and stop SQL Server 2000 using Enterprise Manager or SQL Server Service Manager, even on a cluster.  The Microsoft documentation verifies...

Kedar

Run this script, after inserting your logical file name in both places (the logical file name is what you see under File Name in the Data Files tab of the...

Vidas

If you can find the answer to question 1, it may lead you to the answer to question 2.  But I'm afraid you're going to have to do some work...

Mahesh

Try this.  But beware: if you have procedures of the same name owned by different owners then this will need a bit of refinement.

John

select o.name, user_name(p.grantee) from syspermissions...

I think you're safe using the SQL Server Service Manager to stop and start the services - it's the Services applet in Control Panel that you shouldn't use.  Having said...

Depending on what commands you are trying to execute against the databases in your list, something like this might be what you're looking for:

declare @db sysname

declare @sqlstring nvarchar(100)

set...

Perhaps the users who couldn't connect are all on the same part of the network, and connectivity between that part of the network and the SQL Server was lost.  Then,...