It will not list the user names of user inheriting permissions from dbo.  I do not know how to tweak it to get the results you are after.  Sorry....

Try this:

CREATE PROCEDURE sp_Permissions

AS

SET NOCOUNT ON

IF EXISTS (SELECT * FROM tempdb..sysobjects WHERE [name] LIKE '#perm%')

 DROP TABLE #perm

CREATE TABLE #perm (

 [qid] [int] IDENTITY (1,1) NOT NULL,

  [int] NOT NULL,

 [inherfrom]...

You are probably seeing a clustered index scan because you have a primery key on the unique identifier.  Will this ever be used in the generated query?  I would suggest...

This should work.  Your use of the temp table is not needed.  The update can also be written using inner joins.

update tarcustomer

set hold = 1

from tarcuststatus b

where tarcustomer.custkey = b.custkey

and...

Why are there parenthesis around the join columns?  I shouldn't make a difference in the execution plan.  Try stripping out the unneeded parenthesis and comparing the exectution plans and runtime...

1. I have not had to increase capacity on a Raid 10 array.  I hope someone else can answer this for you.

2. I would not put your tranlogs on your...

There are many, many posts througout SQL Server Central that touch on this topic.  I would recommend adding more drives.  I would add at least one more drive to your...

On the 'Select Source Tables and Views' screen in the wizard, select the Transform .... button.  Then go to the Transformations tab and select the 'Transform information as it is...

Here's a couple ways:

select * from tableA join TableB on TableA.IDColumn <> TableB.IDColumn

Select * from tableA where TableA.IDColumn not in (Select IDColumn from TableB)

I assume that you want to limit the number of user connections and not users?  I do not believe that this can be done.  Can you explain a little more...

Use the Data Transformation object in your DTS package and use an ActiveX script to first check for the existance of the row based on the unique key, if it...

You need to install a new instance from your SQL Server installation disks.  During the installation, you will have the option of naming your instance. 

Why not create a new instance with the same database names and use SQL Server or Windows security to control who can access the databases?

Are you saying that the databases in the named instances are continually messed up because they are in a named instance? 

You can have multiple installations of SQL Server on a machine if you use named instances.  Even in this case, a reference to 'local' would mean the local default instance. ...