I have a Windows Mobile application that uses SQL Server CE 3.5. When a handheld requests a System Update, it receives an .SDF file that’s generated on a Windows Server. This system has been running on a Win 2003 server for several years without any problems.
I’m migrating the server processes from the Win 2003 server to a Win 2008 R2 server and have run into a problem. After receiving the .SDF file from the new 64 bit server, the handheld takes more than 20 seconds to open a connection to it. Opening a connection to the .SDF built on the 32bit Win 2003 server is virtually instantaneous. My experimenting has shown that the problem occurs whenever the .SDF is built on a 64bit machine but does not occur if the .SDF is built on a 32 bit machine.
By the way, only the first connection opening is slow. Subsequent openings are instantaneous. Does anyone know what I can do to fix this?
The indexes in the database are different on a device and a PC (32- or 64-bit). On first open, the device detects that the indexes are invalid for the current platform, so it must delete and recreate them. This takes time. The only "solution" is to reindex them on a device on your end, then deploy the database that came from the device and not the one from the server.
Related
Can I install Visual Studio Code on Windows server 2008 ?
I am a developer but I sent the information to my administrators and they told me that the setup file crashes after launched
I get seput file from hee https://code.visualstudio.com/download
procesor: Intel(R) Xeon(R) Gold 6142 CPU # 2.60Ghz - 2.59 GHz
RAM: 8 GB
64-bit
virtual machine
1 CPU - 2 cores
Windows Server 2008
First time answering here so bare with my vintage reply formatting. (also pardon that i couldn't capture screen due to server is on a intranet that not accessible on this device causing a long reply)
Being a unfortunate fellow that need to work on legacy Systems and Application frequently, i happen to have a fresh 2008R2 server recently setup by my team's Server Admin with following specs:
processor: Intel(R) Xeon(R) Gold 5220 CPU # 2.20Ghz - 2.19 GHz ,
OS: Windows Server 2008R2 x64 ,
RAM: 8GB
The versions that is able to install was 1.70.3,which is the same version that is the last supporting versions for Windows 7 as well,if you happen to need to work on devices using that OS version.
although i'm uncertain whether it is a VM or not, i'd like to point out a few more things that your question did not cover but need to consider:
The installer version (System setup vs User Setup)
aside from the x64 |x86 | ARM installer differences, as you've not mentioned which versions of the build and which exact setup installer you sent to your admin, i've first replied which build version successfully installed on 2008R2, which as of writing the latest build was 1.73.0 and on run,it pop up a error message as follow regardless of System/User Setup:
This Program does not support the version of windows your computer is running.
in our current case that we want specific previous versions installer, VScode FAQ on previous versions have a URL lists that enables you to download a specific build version of your preferred setup. For my case (and also refer below to exactly why this one), i've go for System setup, and i know the aprox. supporting version was ~1.70.0, so i used the link as below and replace the {version} to start:
https://update.code.visualstudio.com/{version}/win32-x64/stable
Active Domain, Multiple user sessions etc.
Per VSCode requirements page stated,
VS Code does not support multiple simultaneous users using the software on the same machine, including shared virtual desktop
infrastructure machines or a pooled Windows/Linux Virtual Desktop host
pool.
as im not sure do you work solo or do have fellow colleagues to code on the server at the same time, you might need to reconsider to install using user or System setup.
if your intentions are to use exclusively on a specific AD account, then user setup should probably be good enough.
however, if the intentions was to setup say a shared Remote desktop connections on the VM that allows multiple RDC sessions simultaneously for coding,programming etc., so you intend to install a system setup to allow all users on said server to be able to use VScode, then you might run into the problem the VScode requirements stated it does not support.
in addition, as i was remote connected as administrator , when using a 1.70.2 user setup ,a different warning message as follow was thrown:
This user Installer is not meant to be run as Administrator. If you would like to install VS Code for all users in this system, download the system Installer instead.Are you sure you want to continue?
as the installer itself also checks with the operator on this matter, your admin may have skipped on the exact reasons why the install failed and just told you the installer crashed.
if you absolutely need VScode to run on the server but can't install for reasons, the last resort (aside from going for alternatives like notepad++) is to Setup a Portable Mode builds on your own workstation/devices first, then upload the package to the server and use it from there.
i wouldn't go into too much detail in that as this reply already span for a starwars trilogy length but keep in mind, version limitations still apply, and whatever add-ons you need, you need to download them first before bundle it into the package to upload and run on your server.
Anyone that is a System admin or infrastructure architects , do correct me on my novice understanding on Server settings etc. as although i'm primarily a programmer, i did end up touching a lot more things that i'm not specialized into over the few years of vendor career work so there bound to be incorrect/inaccurate concepts i spilled. cheers.
I have an apache-tomcat (8.5.35) that runs a web app. It runs on different computers (Windows 10, Mac OS X) without a problem but won't work on a specific computer (also Windows 10). I am not really sure why and have spent hours trying to find out why it won't work. The log files display
org.apache.catalina.loader.WebappClassLoaderBase.clearReferenceJdbc The web application [web-app] registered the JDBC driver [org.postgresql.Driver] but failed to unregister it whenthe web application was stopped. To prevent a memory leak, the JDBC has been forcibly unregistered.
Any idea why it won't work with this specific computer? I have postgresql 10 (x86) installed in this computer. I thought Kaspersky would have been an issue so I disabled it and uninstalled both the Small Office Security and Secure Connection but the problem seems to be linked into Windows or something.
I also tried different versions of tomcat, postgresql, and jdbc drivers (postgresql jar files).
I'm trying to get a legacy Powerbuilder 8 application to work in a Windows 10 environment. The application has not been installed from any installation package, I simply open it from a network share containing all the necessary files. It works this way in Windows 7 systems. In Windows 10 the app opens fine, but connecting to database fails with error message:
999: DBMS MSS is not supported in your current installation.
Neither Windows 7 nor Windows 10 workstations have any specific database access drivers installed.
My development environment has Windows 10 and there connection to the database works ok. The database server is installed locally in the dev environment, though.
We had a problem with Powerbuilder 8.4 and 0racle 10 and 11. With Windows 10 patch 1803. When we copied files to local drive it worked. We were getting strange data base error. It had to do with smb version 1. June 30 2018 Windows 10 solved the problems. If your still having problem this may be worth a shot.
I have Windows 7 64bit. I had Sql Server 2008 R2 Express installed. I unistalled it and then I tried to install Sql Server 2008 R2 Web. Unfortunatelly on the Setup Support Rules page for 'Consistency validation for SQL Server registry keys' I got 'Failed'. I spent half of a day trying to solve it, but then I assumed that there must be realy something wrong with registry keys and it will be faster just to reinstall Windows.
After formatting the disk and reinstalling Windows 7, rebooting dozen of times I installed all Windows upadtes as well. I also did install some programs like Skype, Thundirbird etc. which has no influence on Sql Server setup.
And then I tried again to install Sql Server 2008 R2 Web. And again an error. A bit different one. Now when the setup is on the Setup Support Rules page I get an error message box with the title "FixSqlRegistryKey_x86 - Application Error" and content: The application was unable to start correctly (0xc000007b). Click OK to close the application. 'Consistency validation for SQL Server registry keys' gets 'Failed' status as well.
My team mate has exactly the same machine as mine. He had no problem with installation (he didnt even need to reinstall Windows).
I run the setup as administrator, from a local folder. I even tried to use the setup files copied from my team mate, for a case if my copy is corrupted. In the setup options I have chosen the 'x64' version.
Any ideas what can be the reason of the problem?
Problem solved.
Someone suggested to me that Web edition should not be installed on Win 7 (just on Windows Server). So perhaps installing a different version would work. My team mate perhaps succeeded acidentially - due to having sql server installed already in express edition... but it is just a guess.
Before I tried to install another edition of SqlServer, I downloaded 2008 Express version and I started the install. From the temporary folder created by the express edition I copied FixSqlRegistryKey_x86.exe file and I had overwritten the problematic file in the Web setup with this file.
I started the setup again. It passed the verification this time. But has crashed on a later point - setup unpacks the installation files to C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2 and runs from it. So I needed to again overwrite the problematic file in this location. Now the installation succeeded.
I have basically succumbed to the fact that if you are a hardcore computer user, you will have to reimage your computer every few months because something bad happened. Because of this, I bought imaging software and then really got into imaging. I am now ready to move my development environment completely into a virtual machine so that I can test sites on IIS as though I am on a dev network (and backup these images easily).
The question is, what is the best virtual development platform for a 4 gb laptop? A virtual Vista Business with 3 gb of ram, windows XP sp3 with 3 gb of ram, or Windows Server 2003 with 3 gb of usable ram.
Tools I will need to install:
*sql server 2005 dev edition
*vs 2008 sp1
*tools for silverlight
*and multiple other smaller testing tools
I have tried the following combinations:
Windows XP SP3 on Virtual Server
2005 R2
Windows Vista Business
x64 on Virtual Server 2005 R2
Windows XP on Virtual PC 2007
Windows 2003 on Virtual Server 2005
R2
Windows XP on VMWare Fusion
and the Virtual Server installations where either local or hosted on a server and they all ran fine and about the same speed.
The VMWare Fusion Virtual Machine running under OS X is (seat of the pants) significantly faster than the others. I haven't tested VMWare on Windows to see if it is VMWare or the Hardware making the difference, but it's something worth looking into.
Server 2008, converted to a workstation.
Nothing compares IMO, I've loaded 3 Different OS's in the last 3 months, and I'm set on Server 2008.
I think the biggest question (from my standpoint) is whether or not you'll be doing development (like SharePoint) that requires a server platform. If you anticipate a lot of SharePoint development (or perhaps Exchange, or BizTalk, or another product that requires development be done on a server platform), then go with Windows Server 2003. If not, then I'd probably choose XP, though Vista isn't a bad development platform.
I personally prefer developing on a server platform - however, that opinion might shift if I was developing any sort of WinForms applications, since it would more correctly represent the OS family for the target audience.
I did notice a slight performance decrease going from Server 2003 to Server 2008 that I was not expecting, but that might be more from doing an in-place upgrade instead of starting clean.
From the options you gave, I would personally go with W2k3. You can really trim a server OS down to run lightning-fast, especially when you don't have or get rid of the MS "eye candy".