Sql Server 2008 Enterprise Evaluation Edition Expired!!

  • hi

    i had used Sql Server 2008 Enterprise Evaluation Edition on my machine. now i am getting the error, i.e it was expired.i have backups of every thing.

    can i uninstall and reinstall again the Sql Server 2008 Enterprise Evaluation Edition on my machine. is it possible to do it again or it is not possible,

    please guide me

    thanks and regards

    ROCK..

  • Do an purchase the developer edition of SQL Server. It's $50 US, you can use it for anything as long as it isn't a production server.

  • I'd agree with Denny. Go for the dev edition.

    You could uninstall, but I think you'd need to delete things (not dbs), but files, and clean the reg to get it to reinstall and work.

  • I have a related issue. I downloaded and installed sql server 2008 Enterprise Trial recently in a hurry

    as my version of sql server 2005 developer edition would not connect on vista ultimate to the aquadata

    studio 3.5 client or (more critically) register a dsn in coldfusion administrator for last minute testing of

    application going live.

    I have 2008 and the application (and sql client) talking and my boxed version of developer 2008 has arrived

    but I do not know whether 2008 enterprise declines into a developer edition after the trial period expires

    (unlikely I guess given MS change for dev edition (kinda dumb in itself - you want ot encourage sqlserver dev or not Steve?)).

    I would like to install the dev licence but MS does not seem to document whether this can be done and I doubt trying

    to install dev side by side with ent trial will be grief free and I dont want more days lost fighting ms undocumented connections

    complexities.

    Anyone offer any guidance on the best path to dev edition from ent trial - hopefully not involving reinstalls and reconfig (agghhh)?

    Dan

  • Gave up. You cant go from SQL Svr 2008 Ent trial to a lower version - frustrating most trialists I imagine.

    So uninstalled Ent trial completely and rebooted (it doesnt ask you but the unremoved values block you from reinstalling - so do reboot)

    Installed dev edition - even though installation routine asked for my connection profile and I chose windows and sql server authentication -

    it only enabled windows authentication so I had to reset that again manually.

    Another sloppy MS gotcha was they turned IP connections off again so I had to use config manager and restart server to connect from

    sql client or application.

    Question MS - how many people are not going to connect to sql server over tcp/ip ?

    Another frustrating experience from Gates & Co...

  • compass2k (6/25/2009)


    Another sloppy MS gotcha was they turned IP connections off again so I had to use config manager and restart server to connect from

    sql client or application.

    Question MS - how many people are not going to connect to sql server over tcp/ip ?

    Another frustrating experience from Gates & Co...

    It's not a sloppy gotcha, it's an intentional lockdown of the freshly installed instance. SQL 2005 onwards installs with absolutely no connectivity options enabled and most options disabled. It's for a smaller attack area. It's pretty well documented as well.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • compass2k (6/25/2009)


    Gave up. You cant go from SQL Svr 2008 Ent trial to a lower version - frustrating most trialists I imagine.

    ...

    I was looking for a query that might show me the remaining days left of the trial. In the end I settled for the timestamp on the installation logs. Anyway, my point.

    This post scared the pants off me, as we have an Enterprise Evaluation Edition hosting our new, ready to go production SQL Server 2000 migrated databases. As far as I was aware, you could "upgrade" ( bit of a misnomer when you're coming from a different edition of 2008 anyway ) to Standard so with our licence keys still not arrived and the switch due to take place any day now, I had visions of the new production server turning itself off or having to delay while we wait for the keys :-O

    After digging around the MS site, I find this page http://msdn.microsoft.com/en-us/library/ms143393.aspx that details the version/editions that you can upgrade from/to and my panic is unwarranted...hopefully. Could anyone confirm, from the real world, if they have successfully completed a 2008 Ent. Eval Ed. x64 to 2008 Std x64 "upgrade" and any post upgrade issues that you faced?

    Just thought I'd add this post in case anyone else was in the same boat...save them a few grey hairs.

    UPDATE: I have successfully upgraded to Standard, using our pucka (genuine) SQL Server 2008 Standard DVD. Everything seems unchanged so far, save from the output of @@VERSION of course.

    Thanks in advance,

    Michael

  • There will be a couple of features which are different, such as online index rebuilds won't work any more, and some of the really high end table partitioning features. But if you aren't using them, then you won't really notice the difference.

  • Michael - We have the same situation and need to get from SQL Eval 2008 to SQL Std. We have volume licensing so do I simply use the DVD and run through the upgrade - do all databases stay intact and did you need to enter a product key (we do not have one with our open license) or was this embedded on your DVD? Thanks. Brett

  • Not to worry you too much..

    But i had to give up after trying hard for a few days to downgrade from ent. eval to developer edition.

    i eventually got the database engine running, but SSIS and the even the management studio was never up and running again (and i tried all sorts of tricks including registry changes).

    This COULD however be because i let the eval. edition expire before downgrading, so be sure not to let that happen.

  • bcaruso (7/9/2009)


    Michael - We have the same situation and need to get from SQL Eval 2008 to SQL Std. We have volume licensing so do I simply use the DVD and run through the upgrade - do all databases stay intact and did you need to enter a product key (we do not have one with our open license) or was this embedded on your DVD? Thanks. Brett

    Sorry bcaruso, I must have missed the notification of your post.

    Use the DVD and once the "SQL Server Installation Center" dialog has opened, choose "Maintenance". On that screen is the handy option "Edition Upgrade". When I got to the section that required the Product Key, it was already populated. It was as simple as that. Everything appears to be working normally, as far as testing can show.

    Again, sorry for the shoddy response time.

    Michael

  • Not to hijack this thread...but to make a long story short we found a production server with an evaluation copy that expired...

    I would simply like to extend the end date to then backup then detach the databases for a move.

    According to MS support there is no way to trick the 180 day evaluation and I find that to be a lot of 'BS'....

    Anyone able to 'trick' the system to get the evaluation working past the 180 or extend the 180 limit?

  • Nope, and there's no need to. Simply copy the mdf and ldf files to the other server and attach them.

    Done.

  • Great..one last question...

    if the sql server stops by expiration does go through the process of detaching user databases?

    I ask this because if I attach on the other server will I have to resync to avoid orphan users?

    Thanks

  • Yes you will need to sync the logins to users. You have to do this if the service is stopped or if the database is detached.

Viewing 15 posts - 1 through 15 (of 36 total)

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