none
64 bit windows 7 and sql server management studio express

    Question

  • I have just upgraded to a 64 bit widows 7 machine from a windows xp machine. I need to have ms sql server management studio express to manage a sql 2000 db as well as a sql 2005 db; I used to have this on my xp machine. My tech rep pointed me to: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=76ea83da-4797-4f11-a834-456ee9dc3764 soI went there and downloaded and installed the: ENU\x64\SQLServer2005_SSMSEE.msi.

    the install went fine, I ran some queries and and all seemed fine. I'm not quite sure just when thigs started to go wrong but I think it was when I tried to modify and run a view; my query returned no recordsand then some things took a very long time to run. then I got an error that said that there wasn't enough space to run the query that I was trying to run and eventually the circle just kept spinning. So, I shut it down and restarted. I was able to modify a view and run the query and it ran fine but when I tried to open a file and run the next query, the spinning circle happened again and was spining for about ten minutes and then it shut down.

    I started it again and run one query fine but the next one, it said retrieving data but just sat for a long time. I clicked back on the query, got the spinning circle again and then it just shut itself down again. All of this works well and quickly on my xp machine.

    I have to confess :( that I didn't install the  .NET Framework 2.0, but as it said, if you have already installed SQL Server 2005 or Visual Studio 2005, you already have Microsoft .NET Framework 2.0. and I also didn't install the latest Microsoft Core XML Services (MSXML) 6.0 version mostly because I didn't read the full page because the file download was at the begining so I didn't go any further - dim-witted I know.

    So, I went back and installed the  .NET Framework 2.0 which was actually 4.0; and I tried to install the latest Microsoft Core XML Services (MSXML) 6.0 version but I didn't know whether to install msxml6-KB954459-enu-amd64.exe or msxml6-KB954459-enu-ia64.exe

    I googled what is the differnce between msxml6-KB954459-enu-amd64.exe and msxml6-KB954459-enu-ia64.exe but got only two results in English, one of which was  an article entitled Description of the security update for XML Core Services 6.0: November 11, 2008 it said "This article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you."' but I didn't know to which version it was referring, and a second one entitled Security Update for Microsoft XML Core Services 6.0 (KB954459) which included downloads for both version.

    I am, due to lack of knowledge, daunted by the descriptions and caveats for installing and upgrading and updates, so I appeal to you. I've gone on at length but am trying to give you as much information as possible - and then some.

    I tried again after restarting my system and after one query and a view update, I got a system.outofmemory error thrown.

    I know that Kate will have her challenges but she will never have to figure out stuff like this!

    I doubt that I've even selected the right forum.

    Any help would be appreciated.

    Thanks

    Thursday, March 31, 2011 3:59 PM

Answers

  • Hi,

    The file "msxml6-KB954459-enu-amd64.exe" is used  for 64-bit operating systems, and the file "msxml6-KB954459-enu-ia64.exe" is used for 64-bit operating system running on Intel Itanium CPU. Besides, since you are running Windows 7, which ships MS XML 6.0 SP2 by default, so that you have no need to manually install it. More information about processor types, see: X86 (http://en.wikipedia.org/wiki/X86), X64 (http://en.wikipedia.org/wiki/X64), Itanium (http://en.wikipedia.org/wiki/IA64).

    From the error message, "there wasn't enough space to run the query". It sounds like there is not enough free space on the current database where your query is running on, or you don't have enough free space on the tempdb (some operations will use tempdb, such as sorting, temporary tables, etc.). Please double check that, if this is the case, you may need to manually increase the database or set autogrowth on so that size will be increased automatically if required. Also, make sure you have enough free space on file system where you database files live. More information about how to increase database size, please refer to http://msdn.microsoft.com/en-us/library/ms175890.aspx.

    Another error from your description is that "system out of memory", it sounds that you don't have enough available physical memory for this instance of SQL Server to complete the query. Since you have two SQL Server instances, SQL Server 2000 and 2005 on the same box and/or some other applications as well, you may require enough physical memory on the OS and configure Min and Max Server Memory options for each server instances appropriately and make sure you have enough memory left for some other applications if any. More information about SQL Server server memory, please refer to: http://msdn.microsoft.com/en-us/library/ms178067.aspx.

    You may check your operating system event logs and SQL Server Error Log as well for further investigation about these errors.

    Hope this helps.


    Best Regards,
    Chunsong Feng

    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the threa
    Tuesday, April 05, 2011 3:34 AM
    Moderator

All replies

  • >>that there wasn't enough space to run the query that I was trying to run and eventually the circle just kept spinning.

    The out of memory error you are receiving is not from SQL database engine  but from .net runtime in a client application (in your case SQL Server management studio) which is mostly written in .net (C#)

     

    I would suggest you do not use Management studio to open a large table or view etc.  (this behavior is changed in SSMS 2008 and later it only let you select first 1000 rows etc.)

    Instead you should use **Query Editor** and issue a T-SQL statement to read, write and manage your database.

     

    Thursday, March 31, 2011 4:09 PM
  • Hi,

    The file "msxml6-KB954459-enu-amd64.exe" is used  for 64-bit operating systems, and the file "msxml6-KB954459-enu-ia64.exe" is used for 64-bit operating system running on Intel Itanium CPU. Besides, since you are running Windows 7, which ships MS XML 6.0 SP2 by default, so that you have no need to manually install it. More information about processor types, see: X86 (http://en.wikipedia.org/wiki/X86), X64 (http://en.wikipedia.org/wiki/X64), Itanium (http://en.wikipedia.org/wiki/IA64).

    From the error message, "there wasn't enough space to run the query". It sounds like there is not enough free space on the current database where your query is running on, or you don't have enough free space on the tempdb (some operations will use tempdb, such as sorting, temporary tables, etc.). Please double check that, if this is the case, you may need to manually increase the database or set autogrowth on so that size will be increased automatically if required. Also, make sure you have enough free space on file system where you database files live. More information about how to increase database size, please refer to http://msdn.microsoft.com/en-us/library/ms175890.aspx.

    Another error from your description is that "system out of memory", it sounds that you don't have enough available physical memory for this instance of SQL Server to complete the query. Since you have two SQL Server instances, SQL Server 2000 and 2005 on the same box and/or some other applications as well, you may require enough physical memory on the OS and configure Min and Max Server Memory options for each server instances appropriately and make sure you have enough memory left for some other applications if any. More information about SQL Server server memory, please refer to: http://msdn.microsoft.com/en-us/library/ms178067.aspx.

    You may check your operating system event logs and SQL Server Error Log as well for further investigation about these errors.

    Hope this helps.


    Best Regards,
    Chunsong Feng

    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the threa
    Tuesday, April 05, 2011 3:34 AM
    Moderator