I have a phone server running Window Server 2008. The server software is currently using Microsoft SQL Server 2012 Express Edition. I created an IVR application that has created a second database using the same SQL Server instance.
I found out post-development that the version of SQL Server installed on the server was Express and NOT Standard like I had thought. I checked the SQL Server Configuration manager and noticed that the instance is MSSQLSERVER, but it is running express. The phone system software I am using is proprietary and I cannot get in to change/modify connection strings.
My question is:
Is it reasonable to assume that upgrading from SQL Server 2012 Express to SQL Server 2012 Standard is safe? Does upgrading change the connection string, or instance name? Or is there anything I should be aware of during the upgrade? Or would it be better to just run Standard alongside Express?
Thanks!
I have read various articles saying that the connection string doesn't change, but I would like some input from someone who has actually upgraded from Express to Standard.
Related
Right now I have the express version and I need some automated work done and thus, I need the agent in my SSMS, my question is:
Which edition has the agent? On the website I've seen...
Enterprise,
standard - per core,
standard - server + CAL,
Developer,
Web,
Express
SQL Server Express doesn't support SQL Server Agent.
SQL Server Enterprise, standard, Developer, Web all support SQL Server Agent.
By the way, You can also see the SQL Server Agent Service of the SQL Server Express instance in the Sql Server Configuration Manager. But you can't start it. You will get the error message like the below picture.
I have been searching through SO and found a connection string that seems to be what I need.
However, it does not work.
I use SQL Server 2012 Express and I need my application to connect (with no credentials). I am using the following con.string:
Server=(localdb)\\SQLEXPRESS;Database=MyDB;Trusted_Connection=Yes;
However, the server does not respond.
You need to either use the proper SQL Server Express - then use this connection string:
server=(local)\\SQLEXPRESS;Database=MyDB;Integrated Security=SSPI;
(use just (local) - not (localdb))
or you use LocalDB (which is a "run-on-demand" version of SQL Server Express), in that case, use:
server=(localdb)\\v11.0;Database=MyDB;Integrated Security=SSPI;
The difference:
SQL Server Express proper is a server-based solution, which is installed and runs as a Windows service all the time
SQL Server Express LocalDB is a run-on-demand version of SQL Server Express, which only gets started up when you need it (e.g. in debugging inside Visual Studio 2012/2013)
I dont know much about sql server.
I have just re-installed windows 7 on my laptop. After that I installed Visual Studio 2012 Express Edition. I also Installed SQL Server Management Studio 2008 R2.
Now when I try to log in to sql server management studio by using server name as . or (local) or .\SQLEXPRESS or PC-Name\SQLEXPRESS and using Windows Authentication I get the error as below.
Please dont mark this question as negative as I have searched on google for last 4 hours but did not understand the problem.
Update:
There are many reasons that may cautioning the problem:
SQL Server is not running
SQL Server is not properly configured
You try to connect with a worng instance Name
You can try the following:
Go to Mycomputer->Rigt Click->Manage->Application and Services
And from there check that SQL Server Express is running
2.From there also, gCheck the Instance name of your SQL Express and be sure when you log on to Management Studio you Provide the same Instance name
Confirm that the service is installed and running. Under Computer Management, drill-down into Services and Applications -> Services.
There should be a service named "SQL Server (SQLEXPRESS)". Try a restart or start of the service.
If any other instance of SQL Server is installed it will be listed - try connecting to LOCALHOST(whatever the instance is listed as) to verify the installation is functional.
UPDATED following further information from comments:
You may have only installed the client tools (management studio), and have not installed the database service. Ensure you have the correct installer which includes the database services engine.
First check that the SQL Server parameters are set accordingly.
Go to Start -
All Programs — Microsoft SQL Server 2008 R2 — Configuration tools —
SQL Server Configuration Manager
Under SQL Server Services, make sure that the instance is running :
SQL Server ()
SQL Server Browser
Under SQL Server Network Configuration - Protocols for (), these are enabled:
TCP/IP
Named Pipes
Do the same under SQL Native Client 10.0 under Client Protocols
I need to deploy a WCF service with a database on client machines. I am confused about SQL Server Express. I need to verify all of the following.
When attaching database files in the App_Data folder, do I still need to install SQL Server Express engine (Windows service) on client machines?
There is a flavor called SQL Server Express LocalDb. That one does not need an engine (Windows service)? But I think it need a prerequisite installation of LocalDb.
Localdb is introduced with SQL Server 2012. There is NO localdb for SQL Server 2008. Correct? I could not find 2008 version on MS site.
Do I still need to install SQL Server Express engine (A win Service)
on client machines?
Yes, they need it installed for your application to query the database. Can't really get around it.
There is a flavor called SQL Express localDb. That one does not need
an engine (win service)? but I think it need a perquisite installation
of localdb.
Yes, you'd still need to install LocalDB on the client machine. It's pretty hassle-free to do, but I think it's overkill unless you really need the full features of a SQL Server instance for your webservice.
Instead of LocalDB I'd strongly recommend using SQL Server Compact Edition - it performs the role you're thinking of (your WCF Service can simply connect directly to the database file on your client machines without installing SQL Server, and is lightweight), but doesn't need to be installed (it's simply included as a DLL with your WCF application):
Unlike other editions of Microsoft SQL Server, SQL CE runs
in-process with the application which is hosting it.
In Microsoft's own words on the differences between LocalDB and SQLCE:
LocalDB and SQL Server Compact?
Small and simple database, lightweight installation, connecting to a
database file -- this will sound familiar to any developer using SQL
Server Compact. The similarities are not accidental, as our goal for
LocalDB was to be as easy to use as SQL Server Compact (while being as
powerful and compatible with full SQL Server as SQL Express).
There are significant differences between LocalDB and SQL Server
Compact:
Execution mode: SQL Server Compact is an in-proc DLL, while LocalDB runs as a separate process.
SQL Server CE is kind of like an updated version of MS Access, the file goes with the application which can "just connect" to the database file without involving any database server installation, and its syntax/features are very close to SQL Server standard.
Is there a compatibility problem that would prevent a program running under Windows XP from accessing a SQL Server 2012 Standard instance running on a Windows 2008 server on the same domain?
This might be a stupid question; I know that it is not possible to install SQL Server 2012 on XP, but I cannot think of a reason why it would not allow access by a program.
So this is merely a stab in the dark. For the moment I only wish to know whether there are any problems in principle; if there are none I will try to come up with a minimal error case for my particular setup and ask a separate question.
I just confirmed that an application written in VB6 using ADO with the "Microsoft OLEDB provider for SQL Server" can connect to a SQL Server 2012 database. The connection string looks like this:
Provider=SQLOLEDB.1;
Password=PasswordHere;
Persist Security Info=False;
User ID=SomeUserName;
Initial Catalog=SomeDatabase;
Data Source=SQL2012Instance
The operating system is Microsoft Windows XP Service Pack 3.
The operating system hosting the SQL database is Win-7.
The database engine is Microsoft SQL Server 2012 - 11.0.2100.60 (x64)