Multiple instances of SQL Server - sql

If I install Multiple instances of SQl Server Express Edition (2005) on same DB server, will there be any licensing issue? DB is used by web sites.
Since SQL Server Express Edition is free, but I don't know if there is any limitation in describing the word "FREE"

No, there shouldn't be a problem. You still have the limits in place though.
Just be sure to set them up to run on different ports.

Related

SSRS and SQL Server database on different server

Is it possible to install SSRS and SQL Server database on separate servers, or should these two be installed on the same server?
Thanks
In order to have Reporting Services on your application server, you would have to use a SQL-Server license. You can install just the Reporting Services section of SQLServer, but it is still technically part of the SQL Server application and requires a license for use on that processor(s).
So yes, you can install it on another server.
Yes, you can install only the advanced services, but that still counts as full server., so it requires a full license.
Yes, you can install an Express Edition (with advanced services) on another server for free.
But... the express edition SSRS can't access a non-localhost database (technical limitations of express & web edition).
You can try to circumvent that with linked-servers, but you need to duplicate every used stored procedure, view, table etc., so it's an impractical mess.
The answer to your question is thus: Technically, yes - but actually NO, not without another license.
That extra-installation is gonna cost USD 1'000+ per month.
Yes, you can install SSRS and a SQL Server database on different servers. While the default installation tries to install both, you can select to install them separately.
MSDN links:
Considerations for Installing Reporting Services
Installing SQL Server Reporting Services
From MSDN article Considerations for Installing Reporting Services:
Select Database Engine Services in the Feature Selection page to host
the report server databases. Reporting Services requires a local or
remote instance of SQL Server 2005 or SQL Server 2008 Database Engine
to host the report server databases. If you install an instance of the
Database Engine concurrently with Reporting Services, you can
eliminate a post-Setup task by installing the default configuration,
which creates and configures the report server databases
automatically. In addition to hosting the report server databases, SQL
Server relational databases can also be a source of data for reports
and models.
You could install SSRS in a new server, but to do so you would need a new license for this other server.
From Microsoft SQL Server 2014 Licensing Guide:
"The software components of a single SQL Server 2014 license cannot be separated for use in more than one OSE. If these components are running on a server other than the main database server, then an additional license is required for each additional OSE in which they are installed. For example, if the SQL Server DB is deployed in one OSE and SQL Server RS is deployed in another, both OSEs must be fully licensed for SQL Server 2014 accordingly."
Link to download the guide:
http://go.microsoft.com/fwlink/?LinkId=230678

Can I develop in SQL Server Express for later deployment in a full SQL Server?

Very new to SQL Server. I am needing to develop a SQL Server database to run with an iPhone app I am developing. It will ultimately be running with our full-fledged SQL Server database, which is administered by our IT guy, but I'd like to have a local database for testing.
Two questions:
I assume I can use SQL Server Express 2012 for this purpose, since it is advertised as such; but would it be better/easier to use what appears to be the simplest form, LocalDB, in conjunction with VB2010? It will be running on my office PC to which a port is open for TCP communication from my app (which is working fine). Would LocalDB work for that, if the communication occurs in the VB app? Or will I need to get the SQL Server Express edition?
If a prototype database is developed in SQL Server Express, can it migrate to our full-fledged SQL Server when the app is taken "live"? (I am not sure right now what version our full-fledged SQL Server is, but I was planning on using SQL Server Express 2012.)
Yes, the Express editions ARE the full-fledged SQL Server version - no code difference, only some marketing-driven restrictions (on database size and so forth).
You can absolutely develop your system on a SQL Server Express, and then just detach your database from Express and re-attach it to a Standard or Enterprise edition server. No fuss, no migration, no conversion - nothing - it just works. Period.
And I would probably even argue having a server installation (of your Express) edition is the better choice than LocalDB. That way, you're already using the server-based approach as you will later on in production, and you won't fall into any "convenience" traps offered by LocalDB (or other approaches) that make dev life easier - but rollout to production can be a challenge. When you use SQL Server Express as a server-based installation from the get to - you have the "real deal" from day one.

Will SQL Server Express work with a database made in regular SQL Server?

I was wondering if we could backup the database that we currently host on regular SQL Server, and put it onto our clients computer when we setup SQL Server Express for them.
Is this possible?
Thanks,
Matt
Yes, it's possible to restore a database backup from the Standard edition to the Express edition. It's not possible to restore a SQL Server 2008 to a SQL Server 2005 version, though.
However, there a some minor differences between versions. I've noticed an issue in SQL Server Express 2005 when calling .NET SQL CLR functions across databases, so your mileage may vary. I haven't been able to find a good overview of the exact differences between the various SQL Server editions.
It's always best to keep the development platform as close as possible to the release platform. I can only recommend that you use the Express edition of SQL Server for development as well; and re-test your application.

SQL Azure database using SQL Server Management Studio

I've been trying to work out whether it's possible to manage (i.e. add tables, modify them, create stored procedures) a SQL Azure database using some kind of GUI like SSMS and I keep coming up against different answers.
I found a post from the end of 2009 saying that it would be supported in SSMS but I'm not sure if that includes the Express version? Does anybody know what the most recent update of the express version is and whether it supports it?
I think I'm right in saying that it can't be done in Visual Web Developer 2010 (and I can't afford the full fat VS2010).
I'm prepared to consider alternatives though if anybody knows any full features GUI tools that work with SQL azure and I don't mind paying for a commercial license if it's not too expensive.
Thanks.
Yes, SQL Server 2008 R2's Management Studio does support working with SQL Azure databases.
See:
Getting Started with SQL Azure Development
There are a couple of options
1) You can use SSMS (get the free version by downloading SQL Express v2008 or greater) with advanced services. This will give you SSMS. You can then connect to SQL Azure using SSMS. However - there is a limited set of functionality available via this tool.
2) You can use SSDT (stand-alone for free) or from within VS2010 SP1 or greater. Again, you can connect to SQL Azure, but there are some restrictions on what you can do.
I am using the SQL Express on AWS RDS (free usage tier) myself lately (and connecting via SSMS or SSDT). I prefer their implementation of SQL Server in the cloud to Microsoft's implementation of SQL Azure.

Do I have both SQL Server 2005 and SQL Server 2008 installed?

When in 'SQL Server Configuration Manager' I see, under 'SQL Server Services', 2 items that look like SQL Server's:
SQL Server (sqlexpress)
SQL Server (mssqlserver)
Does that mean I have 2 versions installed at the same time? The 'SQL Server (mssqlserver) is currently stopped).
You have two instances. They might or might not be the same version (meaning 2005/2008).
Express is just an SKU / edition from the myriad of different editions.
You can have the same version or multiple versions/SKUs installed as different instances on the same machine.
So unless someone wittingly set up a new instance with the name "sqlexpress", you probably have two kinds of products installed (both can be 2008 or both can be 2005 or they can be different - it is just that one of them is presumably the Express SKU while the other is say Standard.)
You can get more information on the instances by using ##VERSION.
It looks like you got SQL Server Express installed with Visual Studio and then later installed SQL Server 2008. I've done this before and the best solution I found was to completely uninstall SQL Server Express and SQL Server 2008. Remove all the files in the Microsoft SQL Server directory in Program Files, then reinstall SQL Server 2008. If you still have problems getting the 2008 instance to be the default, you may also need to uninstall Visual Studio.
In the future, if you're going to install the development (or other) version of SQL Server locally, I suggest making sure you install it before Visual Studio. The VS install won't install SQL Server Express if it detects an existing SQL Server instance on the system.
BTW, you can verify if this is true by using the Add/Remove Programs Control Panel item.
SQLExpress is the light/free edition, usually used for developers or very lightweight applications.
MSSQLServer is the full blown SQL install.
So yes you have 2 "SQL Server" installs, but they are different products, I can't say which versions based on your provided data.
You have two SqlServer instances installed on your system. One is SqlServer Express Edition and the other one a Sql Server. I can't say which version or edition.
Maybe you can find some more information in the registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft).
I'd vote against removing either one--SQL server does fine with multiple instances and they are good for different things. For example, lots of open source projects presume a local copy of sql express at .\SQLEXPRESS for development use. Whereas you can't write analysis service stuff with SQL Express.
Or, its not a problem. Those aren't the droids your looking for. Move along.