|
|
Posted by Neil on 12/07/07 20:31
"Greg D. Moore (Strider)" <mooregr_deleteth1s@greenms.com> wrote in message
news:13lj8p2grq8eab@corp.supernews.com...
> "Neil" <nospam@nospam.net> wrote in message
> news:s2f6j.23284$4V6.14684@newssvr14.news.prodigy.net...
>>
>>
>>
>> Just as a general practice with Windows apps, that memory gets lost or
>> corrupted over time. Perhaps not with SQL Server. But there are other
>> apps running on it. PC Anywhere is installed as a host on that machine.
>
> Unless there's a specific need for PCAnywhere, I'd get rid of it and
> administer the machine via remote desktop.
>
> Works much better.
>
>
>> I don't know how much memory degradation, if any, occurs from that app.
>> Occasionally the machine is used to test the front end app (though it's
>> not the primary machine for that purpose).
>
> Well in that csae you've got other issues with the machine.
>
> Which if it's a purely dev machine or one where shutdowns don't impact the
> business, you may be ok.
>
> The prod environments I work in tend to be 24/7 so shutdowns are very
> infrequent.
>
> Also if you're doing a soft-reboot, that's a bit "nicer" to the hardware
> than a hard-reboot which can shorten the lifespan of components.
>
>
>>
>>
>
>
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com
> http://www.greenms.com/sqlserver.html
>
>
One problem with remote desktop is that you can't transfer files or transfer
the clipboard contents (or can you?). I use those two functions all the
time.
Navigation:
[Reply to this message]
|