Our database server is a SQL 2008 server.
My colleagues all have XP service 2 installed with Sql 2008 Management studio and they have absolutely no performance issues.
I however am running Vista x64 (Ultimate) and when I open the 2008 Management studio it's impossibly slow. It takes almost 25 seconds to just connect to the database, so when I run certain portions of our code against the database I more often than not get timeouts.
Everything else on this machine is running like a dream! Is there an issue with SQL2008 on Vista x64 communicating with SQL2008 on a Windows 2003 Server?
Thanks
Nevermind, I have my problem while asking the questions.
Vista has a TCP/IP auto tuning feature. By following this tutorial: http://www.vistax64.com/tutorials/72308-auto-tuning-tcp-ip-receive-level.html I disabled it and now everything runs like a dream!
Related
I'm working on a Sql Server Reporting Services solution that queries across both a Sql Server data source and an Oracle 10g data source. My dev box is Windows 7 64bit with Sql Server 2008R2 and I'm hosting IIS7 and SSRS on that system for development; using VS.NET for designing the reports.
I have been having errors when running the report where SSRS complains about loading the 32 bit Oracle client in a 64bit process. There a number of threads out there about how to solve that. The thing is, they all come down to making sure you have the 64bit Oracle, client which I do. The weird chain of events I have goes like this:
Create initial Oracle datasource and wire up report (it works)
Edit Oracle datasource connection (it stops working with BadImageFormatException 32bit/64bit error message)
uninstall and reinstall Oracle client (it works)
Edit Oracle connection again (it stops working with BadImageFormatException 32bit/64bit error message)
So short of reinstalling the client every time I change the connection string I am at a complete loss. Has anybody seen this sort of behavior? And if so what the heck am I doing wrong?
Originally answered here: SSRS report with 32-bit Oracle Client Not working in 64-Bit Environment
This is the second time I configure a similar server, and the second time I spend hours figuring this one out. If for nobody else, I am writing this for the future me. This is for a Windows Server 2012 R2 64bit, 8GB RAM, 300+GB HDD, Intel Xeon CPU E5620 # 2.40GHz, that is running Microsoft SQL Server Reporting Services 2012 64bit and IIS 7.0 with web applications that use the Oracle Client 32bit connection System.Data.OracleClient
Install the 64bit client
Change the name of the Oracle inventory directory # "C:\Program Files\Oracle" to "C:\Program Files\Oracle64"
Restart computer and test for connection from SSRS to Oracle
Install the 32bit client and specify a different location for its home directory
Restart computer and test connection from SSRS to Oracle and from Web Applications to Oracle
I hope this helps my future self and others :)
You need to install 64 bit Oracle Client. Beware, i had bad experience on having both oracle 32 bit and 64 bit client. I ended up uninstalling 64 bit oracle client and trying to figure out installing SSRS in 32 bit mode on 64bit win7.
I recently switched to a MacBook Pro for my development machine (for many reasons). I want to setup a Virtual Machine for ASP.NET, IIS, and Visual Studio 2010 development. I also have need to do some development work with SharePoint 2010.
What I am wondering is if I should use Windows 7 (64 bit) or Windows Server 2008 (64 bit) as the OS for my development virtual machine. I don't really need most of the services running in Server 2008 so I felt that Windows 7 would probably run faster in the VM environment however I am fairly new to SharePoint 2010 so I am not sure if Windows 7 (64 bit) can be used as a development environment for it.
Thanks for any input.
much easier is to install SharePoint 2010 on Win Server than on Windows 7 - on Windows 7 you need to install SharePoint manually (extract installation files, install prerequisites, install additional patches etc). Here is a link how to do it: http://bit.ly/aDCzvS
Services will not make a difference. Look at all the stuff you need for Sharepoint - this is not a low capacity environment. So, 00mb will not make a difference. Between SQL Server, Sharepoint server and Visual Studio I would say you ASK for about 6-8gb anyway ;)
I do not think it makes a difference now. Sharepoint 2010 was explicitly optimized for being installable on Win 7 - and this is a fully supported development model (contrary to 2007 where you basically were at the end of a bad line as developer). Win 7 should be good. That said, you can tune Windows server to be as good as Win 7 UI wise (for development work and playing music in the background).
I would go with Windows 7 for the time being - and possibly install Sharepoint on a separate Win 2008 when needed. THe main problem here is that Sharepoint is heavy in mem useage, and I woud hate carrying it around all the other time.
A MacBook Pro may be a bad choice for that - make sure you have at least 8gb memory for real sharepoint development work.
I work with people that use SharePoint in a VM on a Mac and their life is much harder. Among other things copying and pasting code between the guest and host machine doesn't work, and they're forced to dedicate one monitor to the VM. You should really consider Boot Camp and Windows 7.
Boot Camp + Windows 7 should get you:
Ability to use multiple monitors (Visual Studio's multi-monitor support is really wonderful)
Ability to hibernate (which you wouldn't necessarily get in Boot Camp + Server 2008 R2)
Use of all of your memory (SharePoint 2010 is a memory hog, running in a VM won't help the situation)
Fewer inconveniences like copy and paste problems
If for whatever reason Boot Camp isn't an option I'd go with Windows 7 in a VM. One of the big pros over Server 2008 is it has all of the features that you need already enabled. It ends up being a lot of work to debug why something isn't working in Server 2008 R2 only to find some obscure feature or service wasn't installed or activated out of the box.
I have a Windows 2008 R2 server running on a VM machine.
My .NET service is running on this server periodically querying WMI, for example:
SELECT ProcessId FROM Win32_Service WHERE ...
After a day or two WMIprvse takes up to 500M memory and WMI queries start getting out of memory exceptions.
This article seems to be talking about this issue:
"http://support.microsoft.com/kb/958124"
I've seen other articles saying that Microsoft is aware of the problem and not going to issue a fix until the next major release.
http://social.msdn.microsoft.com/Forums/en/netfxbcl/thread/256eb40c-d050-4278-a3d8-863e30db02a0
I'd appreciate any suggestions and insights on this.
Check out both the following KB articles,
KB981314 - The "Win32_Service" WMI class leaks memory in Windows
Server 2008 R2 and in Windows 7 -
http://support.microsoft.com/kb/981314/en-us?p=1
KB977357 - A memory leak issue occurs in the Windows Management
Instrumentation service on a computer that is running Windows Server
2008 R2 or Windows 7 - http://support.microsoft.com/kb/977357
...but also worth noting we are on Windows 2008 R2 with SP1 (file versions higher than those provided by both hotfixes) and we are still seeing some slow memory leak issues possibly from either WMIAPSRV.exe and/or TRUSTEDINSTALLER.exe.
We are going to open a support call, if we find anything relevant will post the answer.
There is a hotfix available, but you have to request it by clicking on the link to request the hotfix at the top of the page.
Hotfix
Here is a question not directly related to programming.
Being fed up with Microsoft Windows XP Professional, and the lots of eye-candy, I want to try Microsoft Windows Server 2003 as the main OS on my development PC. (The other reason is a better version of IIS than 5.1). And knowing that Win2K3 was originally designed as a Server OS, I think that I should make it somehow more "workstation friendly".
My question is: How do I transform Win2K3 (Standard Edition most probably) into a Workstation OS? Any articles or links are highly appreciated.
PS: My development PC must run mainly MS Visual Studio 2008, MS SQL Server 2008, MS Expression Studio 2, different Oracle software (10gR2, ExpressEdition, 11g) and other little utilities (a testing framework, a subversion tool - TFS, a web browser, a bittorrent client, etc). All of this are compatible with Win2K3, as I previously checked.
Tnks
I only server OS as my workstation, I had Server 2003 before I switched to Server 2008. There's a guide you can find here http://www.msfn.org/win2k3/.
You shouldn't run into any problems. Most of windows xp drivers will work on server 2003, however, some apps won't. Especially those that check for the OS version before installing. But you shouldn't have any problems with VS2008, Expression and anything you posted.
For me the only thing that was troublesome was running iTunes on server 2003, it doesn't look as good.
And if you like the eye candy you can turn it on by starting the Theme service and changing a few settings.
You shouldn't run into any issues running those applications on Server 2003.
The last time I personally ran 2003 on a workstation the only real big change was changing the security settings of internet explorer.
If you run one of the free anti-virus software packages you may find that they will not install on a Server OS.
edit: As another poster has suggested I would also go straight to server 2008 if it is an options. Server 2008 runs very well as a workstation OS and if you're hardware supports it the virtual server works very well.
Here's links for turning 2003 into workstation:
http://www.google.com/search?hl=en&q=windows+server+2003+workstation+converter
If you'd like use Windows Server 2008 as a workstation, runs much better (faster) than a regular Vista install:
http://www.google.com/search?hl=en&q=windows+server+2008+workstation+converter&aq=1&oq=windows+server+2008+work
or try getting your hands on Windows 7 RC1 which runs quite well.
None of the software types you've listed has any workstation-biased dependencies that I'm aware of. Expression Blend may suffer a bit depending on your hardware and drivers, as WPF is a little more demanding of visual goo than most other development tools for Windows forms.
I am updating my rig and I need to make a decision between staying with XP x64 or going to Vista x64. I do very little development, really just building products from my developers. The other 90% of my work is done with Google Apps, Skype, Office, etc...
I want to upgrade to Vista not only because I will have 3x monitors running on DirectX10, but mostly because iTunes isnt' supported on XP x64!
So, my question...
With all the horror stories about Vista, will Vista Ultimate x64 with 8GB RAM be good for my development machine?
If I can't develop on Vista, I can always fire open a VPC to do the development in. No?
EDIT
I am using all Microsoft development tools...
VS.NET 2005
VS.NET 2008
VB6
SQL Server 2005/2008
ASP.NET
(.NET 2.0 & .NET 3.0)
I'm sure the software will run, I suppose I am not so sure that the OS will be speedy enough, or stable enough.
I am fine with Vista 64 bits for .net and php.
A lot of conversation about it are already on SO. Here is some important point your might take in consideration for .Net:
Unit Testing with NUnit
UAC with developpement
VS and Vista
A lot more...
You can develop for X86 on your new X64 machine without problem.
For PHP XAMPP work fine, Eclipse work fine too.
I run Vista x64 with 4GB of memory and haven't run into any major problems. Before this I was using Vista x86 and I definitely like x64 better as it seems more stable.
In case you're curious, with only (hehe, only!? amazing to say) 4GB of memory I can easily run:
3 instances of Visual Studio 2008 with Resharper
a couple Sql Management Studio instances
Outlook with 3 mail stores totaling # 2GB
Firefox with # 20 tabs
a bunch of Windows Explorer windows
Windows Media Player
iTunes (which is slow as a dog)
# 5 Excel and Word documents
plus some assorted services (eg, Sql Service 2005 and 2008) and status-area apps
Even with all this I still have roughly 750 MB free and no performance issues when using the applications.
I run Vista Business x64 SP 1 (8 GB RAM) for one month now. No problems so far. I'm using following software:
Visual Studio 2005 SP 1
Visual Studio 2008 SP 1
TortoiseSVN / VisualSVN
Visual SourceSafe (older projects)
SQL Server Client Tools
Firefox 3.01 + Firebug
IE 7 + Fiddler
Chrome
Red Gate SQL Compare / Data Compare
Virtual PC 2007 SP 1
Notepad ++
SyncBack
RoyalTS (RemoteDesktop Manager)
Skype
Office 2007
I used it for a long time before switching to Windows Server 2008 (x64) - was very good though,
Personally, I found Server 2008 to be a much better dev OS though. Check out this article on converting Windows Server 2008 to smell a little more like Vista.
I personally use Vista Ultimate x64 with 8GB RAM for my development machine. I don't quite have 3 monitors, but my machine is pretty well set up for development.
Vista x64 is great for .NET and Java. Started with 4GB RAM and that wasn't enough (hit 100% sometimes and the machine would slow to a crawl). 6GB is just barely enough. Hitting 95% memory usage sometimes and it slows down a little, but the machine doesn't go into a paging frenzy anymore.
I run Vista x64 Ultimate as my primary dev machine and it's just fine. Support for x64 has come a long way and for the most part you won't notice a difference except for program files location and much, much more RAM.
Vista will be plenty fast and stable. I'm using Vista x64 Ultimate for development #work right now, and have been for some time. I have nothing but good to say about it.
I'd say it depends on what you're developing. The first priority should be to make sure that all of your development and testing tools work properly under Vista x64. If they don't, there's no reason to suffer the pain of doing all your actual work in a virtual machine.
So I'd say the best thing to do is to take the plunge, see how it works, and keep the XP discs around. And should everything work as expected, it would still be prudent to have a copy of XP running in a VPC just for compatibility testing.
You will have to go XP-based Virtual Machine for any development in IE6. It is near-impossible to run that browser in Vista, let alone Ultimate.
Since a lot of government and legacy code base is against IE6, this happens a lot.
I've used Vista x64 as a development machine and have had only a few minor issues mostly related to using third party APIs in Visual Studio 2008. Just remember that if your getting a really unexplainable error within your Visual Studio project while utilizing a third party API - try compiling your app using the x86 CPU flag in your project settings. This has solved a few headaches for me here and there.