I've tested export of regestry keys "registered servers x"  and "MSSQLserver" (with subkeys), but that did not do the trick

That only gives me...

so after the delete operation, did you perform dbcc updateusage for that db ?

With such mass operations, statistics often get out of date.

If...

You could generate your queries as you desire and store them in a file and then use osql to execute from the saved file(s).

this message occurs when sqlserver gets a timeout when trying to extend a file. In this case it's the logfile.

The is no need...

IMHO memberlists should be documented in a separate entity containing at least listID and memberID.

This way your queries will be easy and straightforward.

With the kind of list you are using...

Don't drop/recreate the clustered indexes !

use dbcc dbreindex (check BOL)

DECLARE @TableName nvarchar(261)

DECLARE @SQLStatement nvarchar(4000)

DECLARE TableList CURSOR LOCAL FAST_FORWARD READ_ONLY  FOR

SELECT

    QUOTENAME(TABLE_SCHEMA) +

    N'.' +

    QUOTENAME(TABLE_NAME)

FROM

    INFORMATION_SCHEMA.TABLES

WHERE EXISTS

    (

    SELECT *

   ...

How about this :

set nocount on

declare @Employees table (EmployeeID integer not null, ManagerID integer null, EmployeeName varchar(128))

insert into @Employees values (1, 2, 'Jane')

insert into @Employees values (2, 3, 'Joe')

insert into...

how about using temporary objects to explode your relationships and then count the temporary objects (@table, #table or ##table).

declare @tmpRelations table (HiarchyLevel integer not null, EmployeeID integer not null, ReportsTo...

if that group already has access to your sqlserver, sqlserver will have stored the "old" windows-group-name in the system-tables. This will not be refreshed by default.

also take a look at KB 832674 (hotfix available !)

If you want to create proc SP_ADD_SCRAP_EXCEPTION_REVIEW2

      from within SP_ADD_SCRAP_EXCEPTION_REVIEW1,

     you'll have to use exec(@sql).

Else

     put a GO before the second create proc statement

end if

Found it !

Define your @sql variable varchar(500).

It is now defined to short !!

  Declare @sql varchar(100)

  Set @repIds = 'Z30'

  Set...

how about :

EXEC master..xp_logininfo @acctname = 'yourdomain\yourgroup',@option = 'members'    

cmd.Parameters.Append cmd.CreateParameter ("@TableName",adChar,adParamInput,3,"Z30")

vs

CREATE Proc LateResponses(@stableName char(3),@idCount int output,@idList varchar(500) output)

should give a unknown parameter.

Because you dynamicaly define the cursor, your users will have...

did you refresh all views that might have used the column with the datatype ?