Weird Installation Message
-
I used to have an HP laptop that had Windows 7 on it. I had very successfully and easily installed my copy of SQL Server 2008 Developer Edition on it. I had to install every service pack on it, as well, but no hitches.
My HP laptop died and I bought a Sony VAIO "E" series with an I5 in it. 6GB of RAM and a 750GB hard-disk in it. Operating system is Windows 7 Home Premium.
The bloody thing won't let me install SQL Server 2008 Developer's Edition (I have a REAL disk of it). Even when I get past the following popup, it tries to install and then asks me for my key. The Dev Edition doesn't come with one. Any ideas on how I can't get around all of this before I do a deep dive on Google????
Thanks, folks.
--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) -
You didn't say whether the OS is 32 bit or 64 bit, but the message says you can install SP1 after installing SQL 2008 to avoid the compatibility issues.
This link may help: http://sqlblog.com/blogs/john_paul_cook/archive/2009/08/10/sql-server-2008-on-windows-7.aspx
Thank the deities that it wasn't your old Core2Duo (or was it a Pentium 4) machine that died! What would we do if you couldn't do performance testing on that dinosaur?
My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St -
dwain.c (8/27/2012)
You didn't say whether the OS is 32 bit or 64 bit, but the message says you can install SP1 after installing SQL 2008 to avoid the compatibility issues.This link may help: http://sqlblog.com/blogs/john_paul_cook/archive/2009/08/10/sql-server-2008-on-windows-7.aspx
Thank the deities that it wasn't your old Core2Duo (or was it a Pentium 4) machine that died! What would we do if you couldn't do performance testing on that dinosaur?
I'm not even sure they make 32 bit laptops anymore. It's a 64 bit machine (I5 processor).
I'll take a look at the link. Thanks, Dwain.
And I think my old dinosaur is going to (hopefully) live forever. 😛
--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) -
Jeff Moden (8/27/2012)
I'm not even sure they make 32 bit laptops anymore. It's a 64 bit machine (I5 processor).That's true enough and if the OS came pre-installed it is also probably 64 bit (although you do have a choice). You can also install a 32-bit OS on a 64-bit machine though.
I know because I've done it to install TOAD (no 64 bit version available to me).
My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St -
Ugh!!! Scratch that... I found the product key. I'd feel stupid about it except that the PK label had fallen off into the bottom of the plastic container it all comes in. I'd have also sworn that it filled in the product key automatically the last time I did the install. Maybe it was 2k5 that did that.
Anyway, thanks for coming to the rescue. The show stopper was the missing PK label and a really bad memory.
--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) -
At least you didn't say your dog ate it. Then it would have sounded like a homework problem. 😛
You're most welcome but all I did was try.
My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St -
BWAAA-HAAAA!!!! In the truest sense, it is, in fact, homework. It's a privately owned laptop for home use that I'm setting up. Thought I'd warm it up with 2k8 before I download 2k12 from my MSDN account.
I REALLY appreciate the "try", Dwain. The day's coffee is starting to wear off and I guess just talking with a friend on SSC snapped me out of my stupor. Thanks, again.
As a side bar, I remember having to talk with an operator to get a hold of someone local on the phone. Now, I'm getting help from someone halfway across the world faster than I can dial a phone and it's almost free. I'm a fortunate soul to have seen all of this happen.
--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) -
Jeff Moden (8/27/2012)
BWAAA-HAAAA!!!! In the truest sense, it is, in fact, homework. It's a privately owned laptop for home use that I'm setting up. Thought I'd warm it up with 2k8 before I download 2k12 from my MSDN account.I REALLY appreciate the "try", Dwain. The day's coffee is starting to wear off and I guess just talking with a friend on SSC snapped me out of my stupor. Thanks, again.
As a side bar, I remember having to talk with an operator to get a hold of someone local on the phone. Now, I'm getting help from someone halfway across the world faster than I can dial a phone and it's almost free. I'm a fortunate soul to have seen all of this happen.
For global connectivity, you should try Skype.
I have to turn it off when I'm at the office, otherwise I'd be responding to chats all day. 🙂
My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply