I would hope it would fail. 🙂

staggerlee011 (3/31/2012)

Hello George.

Sorry what do you...

restricted mode means only members of the db_owner role or the actual owner of the database (in this case the person who restored it) can access the database, so not...

and to achieve that say you want to overwrite the database if using the gui, or use the 'replace' clause if using TSQL.

piotr, for future reference. you will get a better, more focused responses if you start your own new thread.

A shrink of a data file will always fragment that file, so...

the extra memory will help with SSIS and should alleviate the error if its enough extra memory

how much memory did you have before?

As its 32bit SQL engine wont be able to take more than 2GB and will probably top out around the 1.7GB mark, so no...

If your server is in a stable state of equilibrium you may not need to worry. Do you have 'optimize for adhoc workloads' option enabled? If not, you may be...

these are my results on a consolidated SQL server supporting about 10 apps with 13GB out of 16GB assigned to SQL (64bit SQL2008 windows 2008 enterprise)

CacheType ...

enable /3gb you will get another gb for sql - buffer cache only though, wont affect proc cache though I dont think your problem is there anyway

total and target memory the same = a good thing.

is this a 32 or 64 bit system?

thanks for posting back

thanks opc, Thats better, now we have proof.

Just to complete the picture:

what does task manager say SQL is using ?

whats the value for perfmon - sql server memory...

sorry opc.three I am still not convinced on this use of AWE with 4Gb or less of physical memory and 32 bit, I have not seen any evidence yet of...

yes it is, I have done this more than once.. If these are just user databases, merely offlining the databases would be enough rather than stopping services.

back them up first...