You are right but this method I had mostly used to add columns

Sorry I was too vage.

1. you create table with same structure + new altered columns (target)

2. a second table with just one column (PK)  [slider]

3.  Create a view that is...

http://www.nigelrivett.net/SQLTsql/CheckIfFileExists.html

and remember that if you plan to access shares you must use unc path instead

hth

If your shop is 24/7 you are going to have to implement the sliding window view method. If not wait for low activity and do a recommended above.

hth

>>If you have > 16 GB of memory you can toggle the /3GB switch. Problem is, the OS won't see beyond 16 GB.<<

Which again, proofs my point

Yelena,

Table Dependency is achievable from the current metadata tables. Triggers and Table dependency are easy also but OBJECT dependency when it is in regards to procedure and functions is difficult...

I think the only thing that approaches that, are the  perl scripts written by Linchi Shea

Real World SQL Server Administration with Perl

Other than that, you...

Are you saying that

FROM BOL:   (Managing AWE Memory)

...

In order to allow AWE to use the memory range above 16 GB, be sure the /3gb parameter is not in the...

Ah, You are talking about other things. I was carried away with subject of the post !

you could do that even with the previous one too! But What I am trying to get at is that yours and previously posted code are only changing sysdatabases table...

aren't just a bunch of stored procedures?

http://www.rac4sql.net/Help/Introduction/howorks.htm  

I would'n use it for things this simple

I don't know where you got that data from but I can asure you that it is impossible to use /3GB when the OS has to manage more than 16GB AWE

Yep,

Copy and Paste effect

Thanks Remi

rmazzol,  here is the corrected statement

-- Make them read write...

-- Make them read only

exec sp_MSforeachdb 'if (''?'' like ''tg/_%'' escape ''/'' and ''?'' not like ''%training%'' ) begin  exec(''ALTER DATABASE [?] SET READ_ONLY'') end'

-- Make them read write

Frank,

By no means I was offended, and may be my words came out a little bit too strong for what I was trying to get accross (non-native speaker weakness). I appologize...