Emad,

Let try to get a better error message to see what is happenning.

Log on the the server and open a command window and run this...

osql -S. -E -Q"select sj.name ,...

It is in the registery.

USE master

EXEC xp_regread 'HKEY_LOCAL_MACHINE',

'SOFTWARE\Microsoft\Microsoft SQL

...

It depends. How big is the DB and how fast the network.

In the past I built a replication architecture that had 800 miles between the sql servers with a 512KB...

Since you are active/active, it needs to be done on each node.

What you describe applies to an active/passive configuration.

Look at your installation, do you not have two different sql server...

Your developers encrypted the stored procedures.

CREATE PROCEDURE prc1 WITH ENCRYTION

Stored procedure code is stored in the table syscomments and is viewable by anyone. Encrypting the procedure removes this ability. Plus...

Thomas,

Look at the documentation for sp_OACreate stored procedure and all the sp_OA... procedures in the BOL. I think the DLLs will need to be installed on the SQL Server. There...

Scott,

How about this...

CREATE PROCEDURE dbo.getPrice @PRODUCT_CODE VARCHAR(8)

...

non-clustered PK on which table and why would this solve the problem?

sp_executesql should take a VARCHAR(8000) variable

or if that is not enough

Use EXEC( ) instead of sp_executesql.

DECLARE @SQL1 VARCHAR(8000)

, @SQL2 VARCHAR(8000)

...

EXEC( @SQL1 + @SQL2 )...

The SQL command should be exec master.dbo.xp_cmdshell 'CScript C:\schd.vbs'

Norman

Here is a script that uses the IsMember method to find database owners.

// ----------------------------------------------------------------------------

//

// Name: SAReport

//

// Description:

// Generates a report of all the users in the SA Role, as well...

Any way to make this work across NON-trusted domains? Other than installing it in every domain. Centralized collection would be nice.

I successfully used Hit software's OLEDB driver for several years when I needed to interface with the AS400. AS far as I know it is still in use at that...

No

Norman

Execute the following stored procedure just as you would any other.

EXECUTE msdb..sp_start_job @job_name = 'your job'

You must be a sysadmin to start a job that you do not own.

Norman