The problem with running SQL Server (even the Developer edition) on a
non-dedicated workstation is that SQL Server wants to buffer memory for it's
own use. This may leave insufficient physical memory when building a large
application with Visual Studio.NET, re-processing cubes in Analysis
Services, etc. and result in virtual memory paging to disk.
You can use Performance Monitor to determine what exactly is going on:
http://www.informit.com/guides/conte...seqNum=28&rl=1
Also, see if the following helps:
How to adjust memory usage by using configuration options in SQL Server
http://support.microsoft.com/default...;en-us;q321363
"Smithers" <> wrote in message
news:%...
>I have a development PC that has been working great for several years for
>SQL Server 2000 and .NET 1.1 development. It has a PIV 2.4G processor, 512
>RAM, 7200/8MB cache RPM IDE hard drive.
>
> I have seen people in the various NGs claim that one *must* have a
> significantly faster box with gobs of RAM when developing with VS 2005 and
> SQL Server 2005. Is this true? Or are many of you running fine on a box
> like the one I already have (as described above)?
>
> Yes I know more is better... just wondering if I really *must* develop
> with a more powerful box.
>
> Thanks.
>