about writes/sec SQL server

Hi Guys,
Do you know how many writes/sec SQL server is capable of performing
generally? Trying to work out what % of a DB we would be consuming. ThanksProbably many more than you will even need. But it is usually not SQL
Server that is the bottle neck. It is mostly the hardware that will
determine how many writes per second you can do.
--
Andrew J. Kelly SQL MVP
"Iter" <Iter@.discussions.microsoft.com> wrote in message
news:33DBA316-4AE8-49D0-A7EE-D49F8ECD9E7D@.microsoft.com...
> Hi Guys,
> Do you know how many writes/sec SQL server is capable of performing
> generally? Trying to work out what % of a DB we would be consuming. Thanks
>|||How many transactions the sql server can handle for a minutes. Thanks.
"Andrew J. Kelly" wrote:
> Probably many more than you will even need. But it is usually not SQL
> Server that is the bottle neck. It is mostly the hardware that will
> determine how many writes per second you can do.
> --
> Andrew J. Kelly SQL MVP
> "Iter" <Iter@.discussions.microsoft.com> wrote in message
> news:33DBA316-4AE8-49D0-A7EE-D49F8ECD9E7D@.microsoft.com...
> > Hi Guys,
> > Do you know how many writes/sec SQL server is capable of performing
> > generally? Trying to work out what % of a DB we would be consuming. Thanks
> >
> >
>
>|||try to navigate to www.tpc.org: you'll find a lot of different answers.
The number of transactions/min depends on a lot of factrors:
- Hardware
- Infrastructure
- OS
- physical and logical design of the DB
- logical design and implementation of the transaction
- etc.
Usualy any RDBMS is implemented to give the most efficiency, but...
Gilberto
"Iter" wrote:
> How many transactions the sql server can handle for a minutes. Thanks.
>
> "Andrew J. Kelly" wrote:
> > Probably many more than you will even need. But it is usually not SQL
> > Server that is the bottle neck. It is mostly the hardware that will
> > determine how many writes per second you can do.
> >
> > --
> > Andrew J. Kelly SQL MVP
> >
> > "Iter" <Iter@.discussions.microsoft.com> wrote in message
> > news:33DBA316-4AE8-49D0-A7EE-D49F8ECD9E7D@.microsoft.com...
> > > Hi Guys,
> > > Do you know how many writes/sec SQL server is capable of performing
> > > generally? Trying to work out what % of a DB we would be consuming. Thanks
> > >
> > >
> >
> >
> >|||Like I said it is mainly up to the hardware and how the application and
schema were developed. I have worked on SQL Servers that do over 60K
transactions per second. The TPC link that was given would be a good
resource but that does nothing to show how much your system will do.
--
Andrew J. Kelly SQL MVP
"Iter" <Iter@.discussions.microsoft.com> wrote in message
news:098E0931-DD8C-403F-8837-5091D21AE42A@.microsoft.com...
> How many transactions the sql server can handle for a minutes. Thanks.
>
> "Andrew J. Kelly" wrote:
>> Probably many more than you will even need. But it is usually not SQL
>> Server that is the bottle neck. It is mostly the hardware that will
>> determine how many writes per second you can do.
>> --
>> Andrew J. Kelly SQL MVP
>> "Iter" <Iter@.discussions.microsoft.com> wrote in message
>> news:33DBA316-4AE8-49D0-A7EE-D49F8ECD9E7D@.microsoft.com...
>> > Hi Guys,
>> > Do you know how many writes/sec SQL server is capable of performing
>> > generally? Trying to work out what % of a DB we would be consuming.
>> > Thanks
>> >
>> >
>>|||"Iter" <Iter@.discussions.microsoft.com> wrote in message
news:098E0931-DD8C-403F-8837-5091D21AE42A@.microsoft.com...
> How many transactions the sql server can handle for a minutes. Thanks.
How big are your transactions?
Are you committing 5 bytes or 5 gigabytes?
How many disks do you have?
How fast are they?
Quite seriously, your question is really a bit open ended.
Note, even with the TPC benchmarks that Andrew pointed you towards, that's
really a matter of "how much money you want to spend."
With more money, MS could probably post even better numbers. But until
someone betters them enough, they won't bother.
>
> "Andrew J. Kelly" wrote:
>> Probably many more than you will even need. But it is usually not SQL
>> Server that is the bottle neck. It is mostly the hardware that will
>> determine how many writes per second you can do.
>> --
>> Andrew J. Kelly SQL MVP
>> "Iter" <Iter@.discussions.microsoft.com> wrote in message
>> news:33DBA316-4AE8-49D0-A7EE-D49F8ECD9E7D@.microsoft.com...
>> > Hi Guys,
>> > Do you know how many writes/sec SQL server is capable of performing
>> > generally? Trying to work out what % of a DB we would be consuming.
>> > Thanks
>> >
>> >
>>
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Simple answer: enough for your needs - given sufficient hardware. :-) And
it doesn't take a kajillion dollars worth of hardware to get REALLY good
performance either!
--
TheSQLGuru
President
Indicium Resources, Inc.
"Iter" <Iter@.discussions.microsoft.com> wrote in message
news:098E0931-DD8C-403F-8837-5091D21AE42A@.microsoft.com...
> How many transactions the sql server can handle for a minutes. Thanks.
>
> "Andrew J. Kelly" wrote:
>> Probably many more than you will even need. But it is usually not SQL
>> Server that is the bottle neck. It is mostly the hardware that will
>> determine how many writes per second you can do.
>> --
>> Andrew J. Kelly SQL MVP
>> "Iter" <Iter@.discussions.microsoft.com> wrote in message
>> news:33DBA316-4AE8-49D0-A7EE-D49F8ECD9E7D@.microsoft.com...
>> > Hi Guys,
>> > Do you know how many writes/sec SQL server is capable of performing
>> > generally? Trying to work out what % of a DB we would be consuming.
>> > Thanks
>> >
>> >
>>