the drive sizes are ok as long as they are big enough to factor in growth, so you dont want to put in a db now which will grow to...

what is the backing behind changing the collation? is it just to have the same collation throughout or is there other factors at play here?

there is no issue in that its the capacity splits that you need to worry about, but only you can decide this as you should know roughly how the database...

might want to take a look at this url http://www.codeproject.com/Articles/5986/Passing-a-Comma-Delimited-Parameter-to-a-Stored-Pr

replace the , for a + to concatinate the strings at the end of the first case

are you wanting the users to be able to use the data picker, as I have just created a test report allowing multiple values for a date time parameter and...

does the stored procedure handle multiple dates being passed in with the startdate parameter?

you need to split the disks out as you see fit ensuring that they are big enough for db growth and that you can easily add more disk space should...

your login will have a language of english which is US so dates are in the format MDY, if you change it to british english it changes it to dmy,...

try set dateformat dmy at the top of the script

you need an end after the first case

CONVERT(CHAR(4), YEAR(EffectiveDate))+

CASE

WHEN LEN(MONTH(EffectiveDate)) = 1

THEN '0'+CONVERT(CHAR(1),MONTH(EffectiveDate))

ELSE CONVERT(CHAR(2),MONTH(EffectiveDate))

...

yep that would work, one thing I would try though is doing the count in the data set in one report and doing the runningtotal in another and see if...

SELECT

CONVERT(CHAR(4), YEAR(GetDate()))+

CASE WHEN LEN(MONTH(GetDate())) = 1

THEN '0'+CONVERT(CHAR(1),MONTH(GetDate()))

ELSE CONVERT(CHAR(2),MONTH(GetDate()))

END

the bottom part of the script which marcus provided does the memory utilisation checking