September 1, 2015 at 4:52 am
Win 10 Upgrade.
Win 7 laptop upgraded on second try, no issues yet but I haven't tested it beyond it starting.
Other two devices both upgraded from 8.1 to 10 no problems.
SQL Sat Olso;
Was a great success, and I finally got to meet Gianluca in person, cool guy.
Amazing weather as well. Fantastic food.
I took something in the region of 1200 photos, which I will start working through tonight, and continue to do so for a few days yet!
Cheers,
Rodders...
September 1, 2015 at 5:58 am
GilaMonster (9/1/2015)
Thanks everyoneI'm leaning towards getting a 256 GB SSD for the OS and then 2 (or 3) 1TB drives for all the large stuff (databases, graphics resources for my 3D stuff, games, documents, videos, etc). The current desktop has 2 1TB drives in it and one very old 320GB (which still works fine surprisingly), and I've got a 1TB in the drawer that I bought intending to replace the 320 and never did.
The motherboard that Glenn recommended I get has *10* SATA 3 ports on it, so running out of ports won't be an issue, and the case has space for 8 3.5" drives.
Now, affording it all is another matter, as is finding the time to do all the rebuilding.
Gail, if you can swing the price, look at getting a board that will support a PCIe M.2 drive. I've got one, with a 256GB M.2, for my desktop machine and holy carp the boot time is silly fast. I used to have a 256GB SSD, it blows that out of the water. You give up a PCIe slot and possibly one other device (in my case the chipset-based USB3 and the lowest PCIe slot on the board)
When I first loaded the system, the longest part of the boot-up was the BIOS screen. Now it's probably a tie between the BIOS and the OS. I'd say less than a minute between hitting the power button and being able to log in (Win8.1 Pro)
September 1, 2015 at 7:34 am
jasona.work (8/31/2015)
Jeff Moden (8/31/2015)
Steve Jones - SSC Editor (8/31/2015)
I'm not sure this is as big a deal as some people have written. Hard to decide if this is journalism run amok for the sake of hits: http://www.zdnet.com/article/no-microsoft-is-not-spying-on-you-with-windows-10/Heh... I trust them as far as I can throw them on such things. They added a Windows 10 Upgrade icon to my tray on my laptop. If they can do that, what else can they do? Of course, it's not likely that Windows 10 will be any less secure than my current Windows 7 OS but there's also no guarantee of that. So, I'll wait for a while longer.
The icon gets added via a Windows Update that was sent out as a "Recommended" update. So, if you were like most people (including me) on your machine you just check the boxes (or let the install on their own.)
If you want to get rid of the icon, just uninstall KB3035583 and don't re-install it...
Jason
Thanks for this information Jason. Yanking it off right now.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
September 1, 2015 at 7:38 am
jasona.work (9/1/2015)
GilaMonster (9/1/2015)
Thanks everyoneI'm leaning towards getting a 256 GB SSD for the OS and then 2 (or 3) 1TB drives for all the large stuff (databases, graphics resources for my 3D stuff, games, documents, videos, etc). The current desktop has 2 1TB drives in it and one very old 320GB (which still works fine surprisingly), and I've got a 1TB in the drawer that I bought intending to replace the 320 and never did.
The motherboard that Glenn recommended I get has *10* SATA 3 ports on it, so running out of ports won't be an issue, and the case has space for 8 3.5" drives.
Now, affording it all is another matter, as is finding the time to do all the rebuilding.
Gail, if you can swing the price, look at getting a board that will support a PCIe M.2 drive. I've got one, with a 256GB M.2, for my desktop machine and holy carp the boot time is silly fast. I used to have a 256GB SSD, it blows that out of the water. You give up a PCIe slot and possibly one other device (in my case the chipset-based USB3 and the lowest PCIe slot on the board)
When I first loaded the system, the longest part of the boot-up was the BIOS screen. Now it's probably a tie between the BIOS and the OS. I'd say less than a minute between hitting the power button and being able to log in (Win8.1 Pro)
I remember when my wife had me pick out a computer for her at work.
The 1tb drive became a backup to the SSD I installed.
The IT guy started by making a comment implying it was cheap as it was a brand he hadn't heard of.
When they booted it up, and were up and running in less than 15 seconds, his tune changed.
Started asking questions like where can I find one of these and what does it have in it.
A couple years later, it hasn't slowed down.
Usually by this time, she's complaining it's time for a new machine and how slow the machine is.
Drawback is no cup of coffee after hitting the power button in the morning.
You wonder how many leave their machines on overnight just to avoid the boot up wait in the morning?
Between productivity and power savings, a good machine can pay for itself.
Sometimes this is lost in the corporate world.
September 1, 2015 at 8:07 am
Last week my computer kept crashing and after a few crashes it couldn't load Windows. Problem was caused by a bad OSD (200 GB SATA III SSD). I replaced the drive with a spinning 160 GB SATA II drive I had handy, reinstalled Windows and computer is running fine, but is so slow in booting up!
I ordered a new 250 GB SATA III SSD. It should be delivered today. Can't wait to see how much faster booting will be. 🙂
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
September 1, 2015 at 9:26 am
Sean Lange (8/31/2015)
Matt Miller (#4) (8/31/2015)
Sean Lange (8/31/2015)
Grant Fritchey (8/31/2015)
For the upgrade to 10, I think I'd suggest holding off a while. I'm seeing occasional errors: faulty_hardware_corrupted_page. From the Microsoft forums, quite a few others are as well. Seems to cut across the hardware spectrum, Asus, Dell, Toshiba, so it's probably not a proprietary driver. It seems to be something in the OS. One or two more updates before I'd suggest installing it.I did the inplace upgrade on a desktop at home. Generally it works quite well. I have noticed one thing that is really strange. If the computer goes to sleep about half of the time when it wakes up again it will have hundreds of instances of Windows Explorer running each consuming around 4MB of memory. It will use up around 6-8GB total with these threads running. I tried a couple time to kill them but they are like tribbles. There seems to be no end without a reboot.
Another thing that is strange is that it sometimes won't wake up. I can lights on the mouse and keyboard but no amount of movement or key mashing seems to wake Win10 from its deep slumber. I have to do a hard reboot.
I've seen the same, or a close alternate where the screen activates and parks me on the "please wait" spinning icon forever. I've changed my desktop power setting to just kill the monitor, but not put the disk drives to sleep as a result.
Does that "fix" the problem? I am not sure I want to consume that much power and this is my home machine and sometimes it sits 2-3 days without touching it. Maybe I just need to get in the habit of shutting it down when I leave it.
It does for me. Of course - I already don't keep the machine on when I leave, so that part isn't a big imposition. I will say 10 does start up a whole lot faster, so it doesn't slow me down.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
September 1, 2015 at 10:52 am
Silver spoon, you are in the wrong business.
Let's comment out the COMMIT and ROLLBACK statements in code during testing because I don't want to have to restore the database between tests during testing.
Oh, let's have tempdb on its own disk and then try to shrink it because the disk is running out of space. Wait, it tempdb is the only thing on the disk, doesn't it make sense that the problem is that tempdb is trying to grow larger than the disk there by causing the out of space problem? How is shrinking tempdb supposed to solve this problem when it may occur again because of bad code or other processes?
September 1, 2015 at 10:58 am
Lynn Pettis (9/1/2015)
Silver spoon, you are in the wrong business.Let's comment out the COMMIT and ROLLBACK statements in code during testing because I don't want to have to restore the database between tests during testing.
Oh, let's have tempdb on its own disk and then try to shrink it because the disk is running out of space. Wait, it tempdb is the only thing on the disk, doesn't it make sense that the problem is that tempdb is trying to grow larger than the disk there by causing the out of space problem? How is shrinking tempdb supposed to solve this problem when it may occur again because of bad code or other processes?
Yeah, it WILL occur again because I don't think he understands that he has to find the culprit and actually FIX IT.
September 1, 2015 at 11:17 am
Ed Wagner (9/1/2015)
Lynn Pettis (9/1/2015)
Silver spoon, you are in the wrong business.Let's comment out the COMMIT and ROLLBACK statements in code during testing because I don't want to have to restore the database between tests during testing.
Oh, let's have tempdb on its own disk and then try to shrink it because the disk is running out of space. Wait, it tempdb is the only thing on the disk, doesn't it make sense that the problem is that tempdb is trying to grow larger than the disk there by causing the out of space problem? How is shrinking tempdb supposed to solve this problem when it may occur again because of bad code or other processes?
Yeah, it WILL occur again because I don't think he understands that he has to find the culprit and actually FIX IT.
No kidding:
Silver Spoon (9/1/2015)
Unfortunately that is not a quick fix.They are running a lot of SP's that use Temp tables. Hundreds...
September 1, 2015 at 11:23 am
Lynn Pettis (9/1/2015)
Silver spoon, you are in the wrong business.Let's comment out the COMMIT and ROLLBACK statements in code during testing because I don't want to have to restore the database between tests during testing.
Oh, let's have tempdb on its own disk and then try to shrink it because the disk is running out of space. Wait, it tempdb is the only thing on the disk, doesn't it make sense that the problem is that tempdb is trying to grow larger than the disk there by causing the out of space problem? How is shrinking tempdb supposed to solve this problem when it may occur again because of bad code or other processes?
It doesn't matter how many times I remeasure and make another cut. It's still too short! What am I doing wrong? 😉
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
September 1, 2015 at 11:23 am
Matt Miller (#4) (9/1/2015)
Sean Lange (8/31/2015)
Matt Miller (#4) (8/31/2015)
Sean Lange (8/31/2015)
Grant Fritchey (8/31/2015)
For the upgrade to 10, I think I'd suggest holding off a while. I'm seeing occasional errors: faulty_hardware_corrupted_page. From the Microsoft forums, quite a few others are as well. Seems to cut across the hardware spectrum, Asus, Dell, Toshiba, so it's probably not a proprietary driver. It seems to be something in the OS. One or two more updates before I'd suggest installing it.I did the inplace upgrade on a desktop at home. Generally it works quite well. I have noticed one thing that is really strange. If the computer goes to sleep about half of the time when it wakes up again it will have hundreds of instances of Windows Explorer running each consuming around 4MB of memory. It will use up around 6-8GB total with these threads running. I tried a couple time to kill them but they are like tribbles. There seems to be no end without a reboot.
Another thing that is strange is that it sometimes won't wake up. I can lights on the mouse and keyboard but no amount of movement or key mashing seems to wake Win10 from its deep slumber. I have to do a hard reboot.
I've seen the same, or a close alternate where the screen activates and parks me on the "please wait" spinning icon forever. I've changed my desktop power setting to just kill the monitor, but not put the disk drives to sleep as a result.
Does that "fix" the problem? I am not sure I want to consume that much power and this is my home machine and sometimes it sits 2-3 days without touching it. Maybe I just need to get in the habit of shutting it down when I leave it.
It does for me. Of course - I already don't keep the machine on when I leave, so that part isn't a big imposition. I will say 10 does start up a whole lot faster, so it doesn't slow me down.
I have noticed that it seems to boot up a lot faster than any previous version I can remember.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
September 1, 2015 at 11:30 am
Alvin Ramard (9/1/2015)
Lynn Pettis (9/1/2015)
Silver spoon, you are in the wrong business.Let's comment out the COMMIT and ROLLBACK statements in code during testing because I don't want to have to restore the database between tests during testing.
Oh, let's have tempdb on its own disk and then try to shrink it because the disk is running out of space. Wait, it tempdb is the only thing on the disk, doesn't it make sense that the problem is that tempdb is trying to grow larger than the disk there by causing the out of space problem? How is shrinking tempdb supposed to solve this problem when it may occur again because of bad code or other processes?
It doesn't matter how many times I remeasure and make another cut. It's still too short! What am I doing wrong? 😉
Clearly, you forgot to run the saw in reverse. That's how you put wood back on, right? 😀
September 1, 2015 at 11:35 am
Ed Wagner (9/1/2015)
Alvin Ramard (9/1/2015)
Lynn Pettis (9/1/2015)
Silver spoon, you are in the wrong business.Let's comment out the COMMIT and ROLLBACK statements in code during testing because I don't want to have to restore the database between tests during testing.
Oh, let's have tempdb on its own disk and then try to shrink it because the disk is running out of space. Wait, it tempdb is the only thing on the disk, doesn't it make sense that the problem is that tempdb is trying to grow larger than the disk there by causing the out of space problem? How is shrinking tempdb supposed to solve this problem when it may occur again because of bad code or other processes?
It doesn't matter how many times I remeasure and make another cut. It's still too short! What am I doing wrong? 😉
Clearly, you forgot to run the saw in reverse. That's how you put wood back on, right? 😀
No you use DBCC Timewarp 'Woodwork REVERSE'
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
September 1, 2015 at 11:42 am
Sean Lange (9/1/2015)
Ed Wagner (9/1/2015)
Alvin Ramard (9/1/2015)
Lynn Pettis (9/1/2015)
Silver spoon, you are in the wrong business.Let's comment out the COMMIT and ROLLBACK statements in code during testing because I don't want to have to restore the database between tests during testing.
Oh, let's have tempdb on its own disk and then try to shrink it because the disk is running out of space. Wait, it tempdb is the only thing on the disk, doesn't it make sense that the problem is that tempdb is trying to grow larger than the disk there by causing the out of space problem? How is shrinking tempdb supposed to solve this problem when it may occur again because of bad code or other processes?
It doesn't matter how many times I remeasure and make another cut. It's still too short! What am I doing wrong? 😉
Clearly, you forgot to run the saw in reverse. That's how you put wood back on, right? 😀
No you use DBCC Timewarp 'Woodwork REVERSE'
Just be careful which parameter you use to specify your value.
Wait...have you tried a different saw? Or, better yet, a different saw running in reverse?
September 1, 2015 at 11:56 am
Viewing 15 posts - 50,416 through 50,430 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply