|
|
Posted by Neil on 10/03/07 05:30
Well, we certainly don't have anywhere near 14 million transactions a day
(most of the activity is reads, and, even that is not a huge amount). But
with only 2 GB RAM, what would be left for SQL, 1 GB? That doesn't seem like
a lot.
"Greg D. Moore (Strider)" <mooregr_deleteth1s@greenms.com> wrote in message
news:13g65tfdj2ldm20@corp.supernews.com...
> "Neil" <nospam@nospam.net> wrote in message
> news:cTxMi.54176$Um6.5889@newssvr12.news.prodigy.net...
>> Well, we kind of don't have a DBA. :-(
>>
>> We have the system admin, who sets up the boxes, installs the client and
>> network software, etc., but knows next to nothing about SQL Server.
>>
>> Then we have me, the developer, using SQL Server as the back end to our
>> database (Access), and proficient in developing in SQL Server, but
>> somewhat weak when it comes to administrating it.
>>
>> So that's the reality of the situation.......
>>
>> As for users, we have about 30 users connected over a LAN; about another
>> 10-15 connected through a WAN; and are going to have a new location
>> opening with another, I'd guess, 5-10 users at most over the WAN. So
>> total users is about 50.
>>
>> Thanks for your assistance!
>>
>> Neil
>>
>
> At my previous employeer we had a system with 4 gig of RAM (so only 2 gig
> available to SQL Server) that served easily 14 million transaction a day.
> And that was on now 8 year old hardware.
>
> So, "it depends".
>
>
>
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com
> http://www.greenms.com/sqlserver.html
>
>
Navigation:
[Reply to this message]
|