SQLKnowItAll (4/4/2012)

---

Geoff A (4/4/2012)

---

RAID 0+1 is still the best choice, regardless of anything else.

You would need 20 years of finacial data for 10,000 customers before you even got close to...

Lynn Pettis (4/4/2012)

---

I think I would go with RAID 10 (or is it 1 + 0). I'd rather mirror the drives first then strip across that. More resilient...

RAID 0+1 is still the best choice, regardless of anything else.

You would need 20 years of finacial data for 10,000 customers before you even got close to using half of...

RAID 0+1 will yield a 900 GB disk and offer the greatest performance. (if the PERC700 supports it)

RAISERROR is not being removed!!!

the only functionallity that has changed it you cannot pass RAISERROR less the ()

you use to be able to send RAISERROR 50000 'this is a test'...

interviews. blah...

having been on both sides of the table i can also add 1 thing.

whenever you think you did bad, there will more than likely be 10 people behind you...

well, whatever it is, apparently it is not enough.

to the original question though, you cannot see history that is not there.

the SQL Agent job history either gets wiped out...

then check the Agent properties.

the defaults for history are 1000 rows or 100 per job.

do you have a "Clean Up History" task that runs in a Maintenance Plan?

open the Parameters box in BIDS.

it could be a parameter OR it could be in your stored procedure or SQL text.

you can fix / look for problems by using SQL Server Business Inteligence Develpment Studio...

you will need to fix the RDL that generate the report and fix a missing CONVERT issue.

actually, Microsoft has not stated that RAISERROR is deprecated at all. It is still a valid command.

what is ACTUALLY not possible in SQL 2012 is using RAISERROR like this;

RAISERROR 50001...

get the last backup file name like this;

declare @filenametbl1 varchar(60)

set @filenametbl1 = (

select top 1 rtrim(ltrim(REVERSE(SUBSTRING(REVERSE(T2.physical_device_name),0,(charindex('\',REVERSE(T2.physical_device_name))))))) [filename]

from [YOUR_SERVERNAME_HERE].msdb.dbo.backupset T1 JOIN [YOUR_SERVERNAME_HERE].msdb.dbo.backupmediafamily T2 ON

T1.media_set_id = T2.media_set_id

where T1.[type] = 'D' and T1.database_name...

in order to returns zeros from your COUNT on transactions, you will have to use a CROSS JOIN i think.