Post reply

30-day demo period

  • February 13, 2012 at 2:35 pm

    #251546

    Hi there. I'm wondering if there are any good ways to quickly time-lock an application that has been built at the database level. The scenario is:

    1. We want to deliver our software to a potential customer. Giving them 30 days to use it.

    2. After 30 days we've asked them to remove the application.

    However they may not... in which case I want a "back-door" time lock. I'm thinking of doing the following:

    We're looking for a specific logon user i.e. "Mickey"

    I would write a generic .NET CLM and compile it. It would store a hard coded date and the username.

    A logon trigger (we persist our sessions) would then validate against the CLM and either allow access or close the session (is that possible??)

    I'm wondering if anyone has had to do this quickly. It doesn't need to be 100% but the analogy would be "if they want to steal the car, lets at least not leave the keys in it".

    Thanks.

  • February 13, 2012 at 3:14 pm

    #1446552

    You might want to read this about logon triggers ...

    I think somewheres in that article you will find a logon trigger that will do just what you want.

    http://www.simple-talk.com/sql/t-sql-programming/logon-triggers/

    If everything seems to be going well, you have obviously overlooked something.

    Ron

    Please help us, help you -before posting a question please read[/url]
    Before posting a performance problem please read[/url]

  • February 13, 2012 at 3:50 pm

    #1446567

    wow. thank you very much, that's exactly what i want. implemented and wrapped. nice job -thank you.

  • February 13, 2012 at 7:19 pm

    #1446599

    Stevie T (2/13/2012)

    wow. thank you very much, that's exactly what i want. implemented and wrapped. nice job -thank you.

    Will the customer have any logins with "SA" privs. If so, then it's all a fairly useless exercise.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • February 24, 2012 at 12:03 am

    #1451189

    Gald you found the answer but I am thinking your customers are connecting using sql logins to the database (assuming they are accessing the database from different domains).

    I am not sure if the login at the server level is where you should control this behavior of application users.

    It would be better to control user roles assignment via some enterprise login database.

    Consider an example where some users have 30 days while others have 180 days

    Of where some users have access to 2 features and others 8.

    Jayanth Kurup[/url]

  • March 2, 2012 at 2:06 am

    #1454062

    Hi, thank you for sharing

    cong ty dich thuat - tu van du hoc -thiet ke web[/url] - cong ty seo - vietnam software outsourcing

  • March 8, 2012 at 6:03 pm

    #1456904

    phung.quang (3/2/2012)

    Hi, thank you for sharing

    SPAM reported.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply