In my office there is one machine running Windows 7 32BIT Professional and SQL Server Express 2008 along with others software are installed. But the problem is in certain course of time Windows gets automatically deactivated and SQL server gets uninstalled, while other microsoft products are performing well. I have already reactivated the windows and installed SQL server on that machine atleast 3 - 4 times, but problem still persist. Please help in this regard.
regards,
Snehashis Ghosh
Related
In our company we have to support a large legacy system built on Microsoft Access 2010 as frontend and SQL Server 2008 R2 as backend. The backend SQL server runs on Windows Server 2008 R2. Currently our users works on Terminal Server sessions on a Windows Server 2008 R2. A couple of days ago we started to test Windows Server 2019 and Notebooks with the latest version of Windows 10. We recognized a big performance difference while executing the same Access databases on the different environments.
For instance the creation of a report takes 27 seconds (new environment) instead of 7 seconds (old environment). The database.accdb is identical, the backend is identical (still Windows 2008 R2 Server with SQL Server 2008 R2 and SP2), only the execution environment (Windows) changed.
Does anyone of you have an idea how to explain this?
In Access 2010 the SQL server tables are linked using System-DSN data sources. On the old environment ODBC is used (Driver: SQL Server, Version: 6.01.7601.17514).
On the new environment I tested the following drivers:
ODBC Driver 11 for SQL Server (2014.120.5543.11)
ODBC Driver 17 for SQL Server (2017.173.01.01)
SQL Server (10.00.17763.01)
SQL Server Native Client 10.0 (2009.100.4000.00)
SQL Server Native Client 11.0 (2011.110.5058.00)
I created a new System-DSN using the different drivers and updated the linked tables in Access. But in any case the performance is still bad. I also tested the latest version of Access which comes with Office 2019, but again it is slow.
Sounds like your terminal sessions are getting throttled. Despite the fact that you have a SQL Server back end, Access is still doing a fair bit of thunking with the result sets, so any resource throttling differences between your Server 2008 and Server 2019 policies could be choking Access in the new server.
I think your answer is going to be found in Windows System Resource Manager. The page says it's not being maintained, but following the "Recommended Version" link leads to a generic Server 2019 page. Here's another article about how WSRM might be throttling sessions: Using WSRM to control RDS Dynamic Fair Share Scheduling.
Compare the Weighted_Remote_Sessions policy in 2008 and 2019 servers. There's either been a change to the default settings or behavior or the 2008 server policy was modified in the past to get to the current performance level.
Ok, a number of things to check.
First thing to check:
Launch the ODBC manager and check if SQL log tracing is on. I don’t know why, but I see sql logging turned on.
You NEED to be 100% sure it is turned off.
You MUST launch the ODBC manager from the command line or start menu, since the one in the control panel is for the x64 bit version, and you are using Access x32 (I assume).
So launch this version:
c:\Windows\SysWOW64\odbcad32.exe
So VERY important to launch the x32. It is assumed you are using a FILE dsn. So check these two settings:
(Make sure they are un-checked).
Next up?
Link access using the IP address of the sql server.
So, place of say:
myServer\SQLEXPRESS
Use:
10.50.10.101\SQLEXPRESS
(Of course use the IP address of sql server, not the above “example” IP).
The above things are quite easy to check.
Still no performance fix?
Then disable the fire wall on your new Terminal server (I seen this REALLY cause havoc).
And, disable windows defender on the new TS server if running.
The above tips should fix your issues.
If above don’t work, then next would be to check the priority settings for the TS server (GUI over server).
However, I am betting the above checks should restore your performance.
I have Windows 7 running on my machine (I know it's old) and when I try to install SQL Server 2017 using the setup utility, I get this error:
The operating system on this computer does not meet the min requirements for SQL Server 2017. To determine the min required OS supported for this SQL server release, see the hardware and software requirements.
This is the link provided: Hardware and Software Requirements for Installing SQL Server
I don't see anything there that stands out that my machine does not have. I know people have installed SQL Server 2017 on Windows 7 boxes, so that can't be the issue.
I tried changing the compatibility mode by right clicking the setup file and properties too, to Windows 7 but I still can't get passed that error message.
I think at the link you provided Windows 7 is actually not in the list of OS supported? Here it's also mentioned SQl Server 2017 can only be installed on Windows 8 or Windows Server 2012 and later versions.
I tried Installing Microsoft SQL Server 2008 at first, Its installation was going smoothly until I closed my computer to attend to an occasion. Before I tried installing it for a second time, I compressed my C drive(C:) so as to create more storage space. On Installing it again, It couldn't install as a dialog box displayed showing that my attributes doesn't match.
I uncompressed my C: drive and tried installing it again yet it couldn't install. Finally I tried for the last time just to see the image below.
What do I do? My computer is a 32bit OS. and window 7 Ultimate.
You should take a look at the Hardware and Software Requirements for Installing SQL Server 2008, some conditions are:
SQL Server Setup will block installations on read-only or compressed drives.
For minimum version requirements to install SQL Server 2008 on Windows Server 2012 or Windows 8, see Installing SQL Server on Windows Server 2012 or Windows 8 (http://support.microsoft.com/kb/2681562).
So please read it carefully, you can found it in the MSDN here
I have SQL server 2000 dev edition. But it isn't compatible with my new win7 pro 64 bit computer. Is there a free version of 2000 that I can install on my 64 bit pc for development?
As I understand it, I can restore a 2000 database to sql server 2008. But I wont be able to restore the database back to the 2000 server after making any changes in 2008.
The free version of sql server 2000 is called "MSDE". I haven't tried it, but I don't think it works with windows 7. If it does work with Windows 7, you'll have to make sure you run the installer as administrator, and remember that being logged in to the administrator account isn't enough to ensure that happens anymore.
Otherwise, you'll have to update to at least sql server 2005. Both sql server 2005 and sql server 2008 have express editions with licenses that do permit production use if that's any help. If that doesn't work you'll need to install sql server 2000 on a separate machine (even a vm would do) and use newer sql server management studio software to connect to it.
You could use a virtual pc or equivalent with an older OS image on it. I use Virtualbox, it's free and I am very happy with it. I always keep on my home server a compressed Virtualbox image of XP with Sql Server for emergencies.
step1
1-Enter gpedit.msc into the start menu and hit Enter.
2-Now navigate to User Configuration\Administrative Templates\Windows Components\Application Compatibility. Then on the left side under Setting double click on Turn off Compatibility Assistant.
3-Now click on Enabled then click on Apply and OK then close out of Local Group Policy Editor.
step2
go to services and disable Program Compatibility Assistant Service
step3
restart the pc
step4
go to SQL installation folder and choose edition .
Then run setup.bat
step5
please install sql 2000 sp4 when the installation is done.
NB do not run autorun.exe bc you will get error.
IT WILL WORK BC IT IS WORKING ON MY W7 MACHINE
Talley
Raleigh,NC
talleyouro#hotmail.com
"The light will always dominate the darkness"
I always seem to battle with this so on my new Windows 7 dev PC build, I thought I'd try and get it right!
Do you install VS 2008 first and then SQL Server 2005 developer or the other way around? And for either way, are there any special options/settings that have to be enabled/disabled?
I've just take an Acronis image of my PC, configured IIS for use with SQL Server 2005 (see below) and proceed to install SQL Server 2005 developer. It's warned about SQL Server 2005 needing SP3 (no problem) but it's also warned about VS 2005 not been compatible. Can I ignore this and go ahead and install VS 2008?
Cheers, Rob.
PS. The page to configure IIS features for use with SQL Server 2005 is http://support.microsoft.com/default.aspx/kb/920201
I always install in the following order
IIS
Windows Installer
Sql Server
VS any version
whenever i tried to go the other way, i always faced a problem approx thrice i faced this problem. Usually some components becomes missing in other way