Database

DECLARE @CheckQuantity INT;
SET @ParmDefinition N'@CheckQuantity INT OUTPUT';
SET @SQL  = N'SET @CheckQuantity= 12';
PRINT @SQL;

EXEC [dbo].sp_executesql @SQL, @ParmDefinition, @CheckQuantity = @CheckQuantity OUTPUT;
PRINT @CheckQuantity;

(Complete Time of the Period – (Addition of Failures Durations)) / (N° of Failures + 1)*

*for n failures, there n + 1 periods of functioning, and therefore:

For example for a month as January with 44 640 seconds for the complete period and errors as below:

•   From 1/1/14 09:17 to 1/1/14 17:20, (error 1 duration = 483 minutes)
•   From 14/1/14 17:20 to 15/1/14 07:40 (error 2 duration = 860 minutes)
•   From 21/1/14 07:40 to 21/1/14 11:12 (error 3 duration = 212 minutes)

The MTBF would be:

(44 640 - (483 + 860 + 212)) / 4 = 5 385 minutes 30s, MTBF is 89 hours 45mn 30s = 3 days 17 hours 45mn 30s.

DECLARE @value1 DECIMAL(18,2)
DECLARE @value2 DECIMAL(18,2)

SET @value1 = 2
SET @value2 = 500

SELECT (@value1 / @value2)*100
SELECT CAST((@value1 / @value2)*100 AS DECIMAL(18,2))

GuyThiebaut wrote:

partition tables

Agent_Spock wrote:

i am not sure that it can manage 100 million record

http://technet.microsoft.com/en-us/library/ms143432.aspx[^]

Rows per table: Limited by available storage
Database size: 524,272 terabytes

Agent_Spock wrote:

sql but i am not sure that it can manage 100 million record.