Our organisation is planning to create a database for the existing spreadsheets. I have a seen a lot of articles on installation of SQL Server Express. But I couldn't find any information about the prerequisites for the installation (like installing the database engine on a windows server so that the database can be accessed from multiple computers etc).
I want to configure the database such that multiple users and can access it through SSMS.
Please check following MSDN page for SQL Server 2014 hardware and software requirements
https://msdn.microsoft.com/en-us/library/ms143506%28v=sql.120%29.aspx
Then you can switch to any SQL Server version on this page using Other Versions drop down
Search for Express for SQL Server Express Edition requirements on the page
For SQL 2016, here is a list of all operating systems that support SQL Express. More specifically, it does not require Windows Server, however, it does require Windows 8 or higher. SQL 2014, requires Windows 7 or higher.
Also be aware of some of its limitation (though In your case, I don't believe this will be an issue).
Related
I'm trying to publish my ASP.NET Core app to Linux for production. My question is, is Microsoft SQL Server Express available for production in Linux? Or do I have to use the paid version?
SQL Server Express can be used in production (beware of the limitations, like the 10GB cap), but according to this link Express is available for Linux.
SQL Server Express is available for Linux
As discussed in Install Microsoft SQL Server 2017 on Fedora 29/CentOS 7, just install the mssql-server package and choose "3) Express (free)" in the configuration step.
SQL Server Express is available to use in Production. It's just restricted by the DB size (10GB) and doesn't come with some other features, like SQL Agent, High availability, transparent data encryption, etc...
I am poorly experienced in SQL Server installations. I have already installed 2008r2 on Microsoft Windows 8.
Now I want to install MS SQL Server 2005, but I need both MS SQL Server 2008r2 and MS SQL Server 2005.
How can I install this?
You can install both versions on same computer..
From MSDN:
SQL Server supports multiple instances of the Database Engine, Analysis Services, and Reporting Services on the same computer. You can also upgrade earlier versions of SQL Server, or install SQL Server on a computer where earlier SQL Server versions are already installed.
There's a couple of problems here; firstly SQL 2005 isn't even compatible with Windows 8. Windows 7 you can just about get away with it with some patching. Next you need to install the instances and tools in version order. So SQL 2005, then SQL 2008.
You could try uninstalling SQL2008, but you'll probably find too many updates and bits have occurred to get back to a state that might allow you to try doing SQL2005.
My recommendation would be; format the host machine. Install Windows 8. Setup HyperV virtual machines for each version of SQL Server in an operating system that's more inline with the SQL product. Eg. Win2003 for SQL2005. Win2008 for SQL 2008.
He's a block post of doing this to create a manageable developer workstation running every version of SQL Server: http://www.purplefrogsystems.com/paul/2016/05/using-hyper-v-and-powershell-to-create-the-perfect-developer-workstation/
I have a database in SQL server which is created on xp and to be opened on vista
When i try opening it on Vista.
Would this be possible
Thanks
Sun
SQL Server creates files that SQL Server can read. The file formats are independent of Windows versions.
What you should be aware of/considering are SQL Server versions and editions.
For instance, if you create a DB using SQL Server 2008 R2, you will not be able to attach/restore such a database using SQL Server 2005 or 2008, no matter what OS you're working on.
Similarly, if you've applied a particular service pack to the installation where the .mdf originates, you need to be working at the same or later service pack on the system where you want to read the file.
Similarly, if you create a database that uses features that are only available in higher level editions of SQL Server - i.e. something only available in Enterprise/Developer edition - you may have issues using the same database on a Standard Edition installation.
You don't open a sql server database with "xp" or "vista". You open the database in Sql Server. That's all that matters here: does the machine have the correct version of Sql Server available? Note that no version of Windows ships with Sql Server installed by default.
Also, unless you're talking about Sql Server Compact Edition you might want to re-think this. Full editions of Sql Server belong on the server editions of Windows. If you're building a database for an app that will live on individual user's desktop and the database will only serve the instance of the app on the machine, do not use sql server for that database. Instead, use something like Sql Server Compact Edition (it uses a different engine than full sql server that is more desktop-friendly), SQLite, or even Access.
Yes, there is no reason why this should not work.
As #Demian said, you can not open database created in SQL Server 2008 R2 in SQL Server 2008. But alternatively if you are sure that your database is not using any features specific to R2, you can script out whole database and then create similar database by running those scripts into SQL Server 2008 (ofcourse with some changes in script). And then just write some insert scripts to import data from 2008R2 to 2008 (Or you can use SSIS to dump data from one location to another location)
I think the question itself is pretty unclear. No explaination of environment of both XP and Vista machines (e.g. DBMS versions including SPs) or how you are trying to open/access database (using attach or by restoring backup). Without proper information I don't think there is any EXACT solution.
Since SQL Server Express is free to use, If I install two instances of the same version on a single CPU machine, will there be any licensing issue even though it is free?
None.
I currently have a VM that has:
SQL Server 2005 Express
SQL Server 2008 Express
MySQL 5.1.49 Community
Oracle Express (10g)
I don't recommend having them all run on start up, unless you actually need to access them.
I need to create a linked server to a DB2 database on a mainframe. Has anyone done this successfully on a 64-bit version of SQL Server 2005? If so, which provider and settings were used?
It's important that the linked server work whether we are using a Windows authenticated account to login to SQL Server or a SQL Server login. It's also important that both the 4-part name and OPENQUERY query methods are functional. We have one set up on a SQL Server 2000 machine that works well, but it uses a provider that's not available for 64-bit SS 2005.
We had this same issue with a production system late last year (sept 2007) and the official word from our Microsoft contact was that they had a 64 bit oledb driver to connect to ASI/DB2 but it was in BETA at the time.
Not sure when it will be out of beta but that was the news as of last year.
We decided to move the production server onto a 32 bit machine since we were not comfortable using beta drivers on production systems.
I know this doesn't answer your question but it hopefully gives you some insight
What provider are you using for Sql 2000? I'm pretty sure MS has an x64 OLEDB driver for DB2 (part of Host Integration Server, but available as a separate download). IBM has x64 for .NET and ODBC, and possible OLEDB as well (though it's a PITA to find).
Once you get the linked server setup, I'm pretty sure all of your other requirements would be automatic....
From the Sql 2005 February 2007 Feature Pack:
The Microsoft OLE DB Provider for DB2 is a COM component for integrating vital data stored in IBM DB2 databases with new solutions based on Microsoft SQL Server 2005 Enterprise Edition and Developer Edition. SQL Server developers and administrators can use the provider with Integration Services, Analysis Services, Replication, Reporting Services, and Distributed Query Processor. Run the self-extracting download package to create an installation folder. The single setup program will install the provider and tools on x86, x64, and IA64 computers.