This should get you what you need for that particular age range.

SELECT

BIRTHDAY,

NAME,

SURNAME

FROM

TABLE

WHERE

BIRTHDAY >= DATEADD(YEAR,-25,GETDATE())

AND

BIRTHDAY <= DATEADD(YEAR,-20,GETDATE())

IIRC ClusterAdmin needs only public access to be able to in a fashion do a connection to the master database to check its online to either initiate a fall over...

the best place to start would be here http://technet.microsoft.com/en-us/library/ms151198.aspx and then pic the replication type which is best suited for what you need to do.

Hi welcome to SSC, please could you take a moment to read the second link in my signature on how to post code as it will help us, help you...

Hi, welcome to SSC, please could you take a few minutes to read through the second link in my signature block in relation to posting code so that we can...

Yes you are correct that if your password expires then the data source will fail to work.

Personally I would go for the second option, and set it as a user...

If you change the data source to use your credentials, then each user which runs any reports which use that data source will impersonate your credentials.

If you dont want this...

what error, severity, state numbers do you have for this?

something like error 18456, severity 14, state 11?

also if you use a proxy account you will find it in the run as box of the job step, if it says SQL Server Agent Account, then this should...

riya_dave, I have been looking at a few of the threads started by yourself and a number of the people here are getting frustrated due to you not answering...

yes, it will be the execute as drop down box of the job step

check the execution account of the maintenance plan? is it running as the agent account or do you have it running under a proxy. from there you should...

does the user exist as a server principle already? if not it will need to be added as a login first before it can be added as a DB...

declare a parameter or a variable within the report, set it to an expression of the GETDATE() equivilent in SSRS, then use that instead of System.DateTime

thats due to you using the system date time and that is always changing due to it being the system clock. you would need to use a static starting...