I am trying to install SQL Server Data Tools - Business Intelligence for Visual Studio 2012 on my currently installed SQL server.
I get the following error during installation : same architecture installation
The error message does not make sense, these are my specifications
I am using the following exe to install Business Intelligence tools
I had the same error.
In this case, in Installation Type section, you need to choose
Perform a new instance of SQL Server
instead of the
Add features to an existing instance of SQL Server
Otherwise, the installation fails with "Same architecture installation".
In all likely hood you have a 64-bit SQL Server application installed on your box. You can check the CPU architecture type of your SQL Server installation by firing following query:
select ##VERSION
On my machine which has a SQL Server 2008 installation returns below string:
Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64) Jun 28 2012 08:36:30 Copyright (c) Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
Here the initial part of the query output Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64) suggests that my SQL Server installation is a 64 bit application. To make an upgrade or adding new feature I'll always have to run 64-bit installer.
You are trying to run x86 (aka 32-bit) CPU architecture installer to add new features.
Though you are not at fault. This link details the trail of events as to why Microsoft never released x64 CPU architecture installer for this specific case of SQL Server Data tool - Business Intelligence for Visual Studio 2012. The available setup is only 32-bit as Visual Studio 2012 (Shell) is 32-bit only.
Quoting from the link I've mentioned above:
Make sure you choose the "New Instance" option (strange as that might
seem). Otherwise, you'll get an error that says the following: Rule
"Same architecture installation" failed.
This will effectively create a new 32-bit named instance on your computer and install all the desired features and data tools on top of it.
Update: I've faced the same issue even while installing SQL Server Management Studio 2014 on top of an existing SQL Server 2014 (x64) Instance. In fact, in this case I faced the issue even when I was running 64-bit installer of SSMS 2014. Solution remains same to go past the error.
Related
I'm trying to move to a new hosting provider and I'm having real difficulty getting my web site to run. It uses Hangfire on application startup to run some background jobs, whilst also serving web pages on the main thread.
The website seems to work for the very first page load and then subsequent accesses fail to run a reasonably complex Entity Framework search query.
Here's the server's configuration on the existing machine, via SQL Server's select ##version command:
Microsoft SQL Server 2017 (RTM-GDR) (KB4583456) - 14.0.2037.2 (X64) Nov 2 2020 19:19:59 Copyright (C) 2017 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: )
Shared operating system (not sure what this is)
SQL Server 2017 - Standard Edition
.NET Framework 4.8
Hangfire using SQL Server storage, with table's using the Hangfire schema
Other application tables, with tables using the dbo schema
Here's the server's configuration on the new machine, via SQL Server's select ##version command:
Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64) Sep 24 2019 13:48:23 Copyright (C) 2019 Microsoft Corporation Express Edition (64-bit) on Windows Server 2019 Standard 10.0 <X64> (Build 17763: ) (Hypervisor)
Windows Server 2019
SQL Server 2019 - Express edition
.NET Framework 4.7,. (according to Plesk, although I've installed 4.8)
On the new server I have full RDP access, so can install whatever software I like on this machine. However, SQL Server Standard edition is extremely expensive for a little website like mine.
Is there something that is preventing the Entity Framework query running on the new Windows Server 2019 machine, with SQL Server Express? Does that combination not allow multiple schemas for the database, or is there some other restriction from this combination that I might not be aware of?
Running the website with SQL Server Express on my local Windows 10 machine runs fine.
I'd really appreciate any help with this, as I'm pulling what little hair I have left out of my head!
Thanks for trying to help, but in the end the problem was a lot simpler than I'd anticipated. I thought this was a permissions issue, but actually it's just a simple performance issue.
Running SQL Express on the new server failed because the machine didn't have enough RAM. It only had 4GB of RAM, and with Plesk and other software installed by the hosting provider, the free RAM was down to just a few hundred MBs.
Some simple queries that would take milliseconds to return on the old server could take over 2 minutes to return on the RAM limited new server.
Increasing the RAM to 8GBs fixed most of the issue, although using SQL Express is still significantly slower than the SQL Standard edition on the old server, and SQL Standard is alarmingly expensive to run just for this one website (the old server has a shared SQL Standard edition installation).
When trying to install SQL Server 2016 Express in Windows 7 Professional x64 SP1 in VMware I get the following message.
What can I do to solve this?
Here is a workaround for users that need SQL 2016 on a Windows 7 development PC. This will allow the developer to develop and manage them by using using MDFs in LocalDB:
If you don't have Visual Studio 2015 then get it or the 2015 Community Edition
Download and install SQL Server Data Tools. SSDT
Note:
When I initially installed Visual Studio 2015 I chose custom install and selected all options. I was assisting someone else troubleshoot their installation so I installed Visual Studio 2015 Community Edition on another Win 7 Computer. I chose custom Install and under Windows and Web Development options I chose Microsoft SQL Server Data Tools. It stated 2012 SQL Server, but after install and restarting I had both the 2014 and 2016 SqlLocalDB (under 120 and 130 folders respectively). SQL Server Data Tools install may not be needed unless you need SSIS, SSAS or SSRS which I do need.
After all of this you will need SQL Server Management Studio 2016 or higher to connect to the local db and access the 2016 functionality.
After you have installed this there should be a SQL Local DB command Line tool installed. My install location was D:\Programfiles\130\Tools\Binn\SqlLocalDB.exe
The default install location as pointed out by Discosultan may be:
D:\Program Files\Microsoft SQL Server\130\Tools\Binn\SqlLocalDB.exe
My install path was different, but that may be due to the several versions and related components of SQL server that I have installed on the PC and the manner of my installs. Once you have done the install you can search for SqlLocalDB.exe if you have multiple versions and navigate to the 2016 version, (product version 13 in the 130 subfolder).
You can find the install folder path in the registry for SQL 2016 by reviewing the following Registry Entry in HKEY_LOCAL_MACHINE (Abbreviated to HKLM below):
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server Local DB\Installed Versions\13.0
You can run the command line from there or add the directory to the path statement. I have multiple versions so I just go to the directory. Then you create a localDB instance and start it:
SqlLocalDB create "LocalDBExample2016" -s
SqlLocalDB Utility Command Line Reference
From that point if you prefer the GUI you can open SQL server Management Studio 2016 or through Visual Studio and connect to server:
(localdb)\LocalDBExample2016
From there you can add databases, etc.
The mdf and log files will default to C:\Users\[UserName], but they can be moved when creating the databases or copied elsewhere and given to the DBAs, etc. Some of the features won't be available like in memory OLTP tables. Here are the edition comparisons: Editions and Supported Features for SQL Server 2016
As the error message states SQL Server 2016 is not supported in Windows 7. You will have to upgrade to Windows 8 or higher or switch to a Windows Server operating system. Here is a list of all the operating systems (and other hardware and software requirements) in which SQL Server 2016 can be installed.
Late to the party, but while you can't install SQL 2017 Express or 2016 Express on Windows 7, you can install SQL 2014 Express. This may not work for compatibility purposes if you're dealing with a newer version of SQL (although I've been able to install the non-express version of SQL 2016 and 2017 to Windows 7) but if you're supporting something that uses an older version of SQL Express (which, frankly, is likely if you don't have access to a newer OS) this should work well enough.
I am a new SQL Server programmer and this is my first question on stackoverflow.
Anticipating your help...
I have these installed in my PC: Windows 7 ultimate SP1 + SQL Server 2012 Enterprise + Visual Studio 2010 (SSDT which came with my SQL Server 2012). What I want to do is create a database from SSDT.
In server explorer, I right clicked the data connection -> create new SQL Server database. After I input my server name and choose "Use Windows authentication" (which is the case with my SQL Server 2012), I got this warning:
This server version is not supported. Only servers up to Microsoft SQL Server 2008 are supported.
What shall I do? Shall I upgrade to Visual studio 2013 or I have other options?
Much appreciated if anyone can help.
Visual Studio isn't really the issue here. And you didn't say why you installed VS 2010 (are you actually developing apps with it?). If you're not actually developing in VS, I would remove it and just install the latest SSDT. This will install a VS shell, containing enough functionality to fully run SSDT. Then you should be able to create SQL Server 2012 databases, which I assume is what you want to do.
I am having trouble finding the 64 bit version of Microsoft SQL Server Data Tools.
Does any one know where i can download the 64 bit version of Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2013 and SQL Server 2014.
I have only been able to find the following 32 bit version http://www.microsoft.com/en-us/download/details.aspx?id=42313 but i need the 64 bit version.
As the others have said, there is only a 32 bit version.
The important thing is, if you’re running an x64-based SQL instance (64-bit), make sure to select “New Instance” on the Installation Type page, and NOT “Add features to an existing instance”. Not doing so will cause it to error out.
Only 32 bit version of SQL Server Data Tools published by Microsoft.
SQL Server comes in x32 and x64 but Visual Studio comes in only x32.
So if you have x64 SQL Server 2014, you can only install SQL Server Data Tools x32 in a new instance configuration. This will install Visual Studio 2013 x32.
However if you have SQL Server 2012, SQL Server Data Tools are available in the installation media (unlike SQL 2014 where it has to be manually downloaded & installed).
I am using 64bit Windows 8 rtm.
Where can I get Sql server 2008 mgmt. studio for it?I tried installing sql server 2008 express sp1 and SQL Server 2008 R2 Express SP1, but it wont install.(ref: http://blogs.msdn.com/b/sqlexpress/archive/2012/03/02/sql-server-express-and-windows-8.aspx)
Can you provide me a link from where I can download a working setup and give step by step installation instructions?
Well for a start the OS requires the appropriate version of MS SQL to be installed. You may have difficulty in installing just the management studio because express is primarily designed to run on a stand alone machine. There is some configueration work to do to get ports open and protocols enabled. I suggest you install SQL 2008 R2 express with tools: http://www.microsoft.com/en-gb/download/details.aspx?id=26729
You want the WT (with tools versions)
however you may want to install sql 2012 express as this will connect to all earlier versions of MS SQL