I have installed ASP .NET 2.0 MVC3, SQL server express 2005 and SQL server Management studio express 2005 and IIS 7 in my system. If I am opening the install_btnet file, and providing the SQL server details also it is not getting connect. It is giving error as Service unavailable. Any one suggest me how to install Bug tracker .NET tool in my system with examples.
Thank you.
First thing to check it that your SQL 2005 express instance is running and allowing remote connections. Open the Administrative Tools >> Services and look for the service called "MSSQLSERVER$SQLEXPRESS" and ensure it is started.
Next, open the SqlServer Configuration Utility (on the server or PC where SQL 2005 Express is Installed) Look for the Client Configuration Option and Select "Client Protocols".
Set TCP/IP to "Enabled" and you should now be able to connect to your SQL server.
Note that even if your BugTracker.NET install is on the same machine, it may still be using the network to connect to your SQL Instance.
Hope this helps,
Dave
Related
Suppose that I've created a project using MS SQL Server.
Now if somebody asks me to run my application on their brand new PC, should I install the entire SQL Server management studio on their computer? Or are there any other choices?
Please note that I just want to run my app (.exe template) not to debug it or anything else.
If your application is intended for standalone use on a PC, you can include the redistributable version of SQL Server Express in your installer. It's a limited but functional version of SQL server intended to be included with application programs like yours free of charge.
https://www.microsoft.com/en-us/sql-server/sql-server-editions-express
If your application program is designed for either shared or standalone use, and you have time to polish up your installer, you can ask your users whether they want to use a shared SQL Server instance. That will let you skip the installation of SQL Server Express when it's not necessary.
No they don't need SQL server or management studio , however they a database driver to access the server. ADO, ODBC and JDBC are the types of drivers you would look at. This depends on the language you wrote your application in and the connection string.
You clients would use the server's address and connect to it using the driver which is specified in a connection string. See the examples below:
.Net Framework Data Provider For SQL Server:
Server=myServerAddress;Database=myDataBase;User Id=myUsername;
Password=myPassword;
SQL Server Native Client 11.0 OLE DB Provider:
Provider=SQLNCLI11;Server=myServerAddress;Database=myDataBase;Uid=myUsername;
Pwd=myPassword;
If you application only connect to the database that you have a two-tier client server architecture. For the server to be reachable it needs to be on a network or network endpoint that the clients(people running your software) can see. The server needs to be on as well(your comments).
I've installed SQL Server 2016 (Standard Edition) on a Windows Server 2016, selecting Integration Services to be installed too. I've also installed SSMS and SSDT from the same installation media.
I am running SSMS as administrator and can connect to the local Database engine.
My user is a Windows and SQL Server admin.
However I cannot connect (explicitly using the server name) or even browse to the local Integration Services?
Receiving the following error.
SSIS not browsable and can't connect
Having already searched for an answer to this problem, many suggest checking that the service is running etc. which can be seen in the Services and SQL Configuration Manager.
Services shown as running
I've also tried turning off the Windows Firewall to establish if that is the cause of the problem but it had no effect.
Anyone got any ideas what might be preventing it from being accessible?
I've had this problem last month. In my case I had to install the 32-bit version of access database engine (on my 64 bit windows).
Sql data tools works with 32-bit
https://www.microsoft.com/en-us/download/details.aspx?id=54920
The later SSMS versions (16.x and 17.x) will only connect to their respective versions SQL 2016 and SQL 2017. Microsoft is planning to retire the older method in favor of the SSISDB, which is more secure.
Link to the official statement from Microsoft (in the note box).
I have had the same problem and the solution was to install the old interface on top of the existing one (SQL Server Management Studio 2016). Here's link to the installation file. After having installed this, I can now connect to the integration services. You will have to set it up of course and give yourself Rights
I have downloaded and installed SQL Server 2014 Express
(from this site: http://www.microsoft.com/en-us/server-cloud/products/sql-server-editions/sql-server-express.aspx#Installation_Options).
The problem is that I can't connect/find my local DB server, and I can't develop DB on my local PC. How can I reach my local server?
My system consists of Windows 8.1 (no Pro or Enterprise editions) 64 bits
Checking the configuration of SQL Server with SQL Server 2014 Configuration Manager tool, I see an empty list selecting "SQL Server Services" from the tree at the left. Below you can find a screenshot.
In the Windows Services list, there is just only one service: "SQL Server VSS Writer"
EDIT
My installation window of SQL Server 2014 is the following:
Most probably, you didn't install any SQL Server Engine service. If no SQL Server engine is installed, no service will appear in the SQL Server Configuration Manager tool. Consider that the packages SQLManagementStudio_Architecture_Language.exe and SQLEXPR_Architecture_Language.exe, available in the Microsoft site contain, respectively only the Management Studio GUI Tools and the SQL Server engine.
If you want to have a full featured SQL Server installation, with the database engine and Management Studio, download the installer file of SQL Server with Advanced Services.
Moreover, to have a sample database in order to perform some local tests, use the Adventure Works database.
Considering the package of SQL Server with Advanced Services, at the beginning at the installation you should see something like this (the screenshot below is about SQL Server 2008 Express, but the feature selection is very similar). The checkbox next to "Database Engine Services" must be checked. In the next steps, you will be able to configure the instance settings and other options.
Execute again the installation process and select the database engine services in the feature selection step. At the end of the installation, you should be able to see the SQL Server services in the SQL Server Configuration Manager.
I downloaded a different installer "SQL Server 2014 Express with Advanced Services" and found Instance Features in it. Thanks for Alberto Solano's answer, it was really helpful.
My first installer was "SQL Server 2014 Express". It installed only SQL Management Studio and tools without Instance features. After installation "SQL Server 2014 Express with Advanced Services" my LocalDB is now alive!!!
I have noticed that after installation of SQL server 2012 express on Windows 10 you must install ENU\x64\SqlLocalDB.MSI from official Microsoft download site. After that, you could run SqlLocalDB.exe.
Just download and install LocalDB 64BIT\SqlLocalDB.msi can also solve this problem. You don't really need to uninstall and reinstall SQL Server 2014 Express with Advanced Services.
Also, if you just installed localDB, you won't see the instance in the configuration manager. You would need to initiate it first, and then connect to it using server name (localdb)\mssqllocaldb.
Source
I faced the same issue. Just download and install the SQL Server suite from the following link :http://www.microsoft.com/en-US/download/details.aspx?id=42299
restart your SSMS and you should be able to "Register Local Servers" via right-click on "Local Servers Groups", select "tasks", click "register local servers"
I want to deploy an MVC 4 web application to a Windows Web Server 2008 based dedicated hosting. I am using SQL Server 2008 R2 Express as my back-end database. What steps will I need to take regarding the following:
Installing SQL Server 2008 R2 Express on the web server and deploying my database.
Managing SQL Express database remotely using SSMS.
Configuring database path in my EF5 generated model
Deploying my application
Managing changes to my application.
Can someone provide me a detailed answer/some good links?
Installing SQL Server 2008 R2 Express on the web server and deploying my database.
This depends on your provider. Most providers, if not all, allow you to install your own licensed SQL Server. If you will be using an Express edition then it is, and should be, 100% allowable by your provider. The only step you need here is to go to download page of SQL Server 2008 R2 and download the appropriate file you need. The files you need on that page are the ones with "ADV" in its name. Choose x64 if you will install a 64-bit OS or choose x86 if you will install a 32-bit OS.
Managing SQL Express database remotely using SSMS.
This depends on the firewall set by your provider. But basically this is how you will allow remote access to your SQL Server:
For Windows 2008 R2
Login to your dedicated server using Remote Desktop. If you don't know how to do this, it's best that you consult with your provider.
Go to Start > All Programs > Microsoft SQL Server 2008 R2 > Configuration Tools -> SQL Server Configuration Manager
On the window that open in step #2, expand SQL Server Configuration Manager (Local) -> SQL Server Network Configuration -> Protocols for SQLExpress
On the right pane, right-click TCP/IP and select Properties.
Select the IP Addresses tab and then scroll to the IP All section.
Set/change the TCP Port value to/from 1433 to 14333 (or any other port) and then click OK.
Right-click TCP/IP again and Enable it
Restart your SQL Server by going to Start -> All Programs -> Administrative Tools -> Services -> SQL Server (SQLEXPRESS) -> Restart. The Restart is on the left pane.
Configuring database path in my EF5 generated model
Unfortunately, I cannot answer this one as I believe you are using the EF designer in creating your model. I never worked with EF that way, but only by code-first. I have to skip this part and let you Google this.
Deploying my application
There is already a good documentation written here so I will not dupliate it here. Basically what you need to do is enable FTP on your dedicated server. Then once that is setup you can go on with bin-deploying your application.
Managing changes to my application.
I assume what you are asking here is that if you have changes to your application, how would you re-deploy it. A bin-deployment will not hurt. Deploying only the files in which you have changes is a good approach. Knowing which files changed can vary depending on the tools you use. In addition, if you don't have any fancy setup that will tell your users you are deploying changes to your site, you might want to take a look at this post. It tells you to put a App_Offline.htm file in your root web directory. That should still work with MVC, after all MVC is still ASP.Net.
I've just built a new dev machine and I can't get SQL Server Agent working. What I've done so far:
Install VS 2010 (I think this installed an express version of SQL Server)
Install SQL Server 2008 R2 Developer edition.
I'm not sure if I did something wrong in step 2. All I want is a fully working version of SQL Server with SQL Server Agent running and no limitation on the amount of data I can store (I will need more than 10GB).
Currently, in SSMS I have the following instance: ./SQLEXPRESS. I thought that during step 2, this would have been upgraded, but it doesn't seem so.
Can anyone help?
Note: I ended up resolving this by uninstalling everything that had "SQL Server" in it in Control Panel > Programs and Features. I then reinstalled from scratch.
Note: I ended up resolving this by uninstalling everything that had "SQL Server" in it in Control Panel > Programs and Features. I then reinstalled from scratch.
The agent account is disabled. If you aren't able to enable it through configuration manager, try enabling it through services. After its enabled, try starting the serivce. If you still have issues starting the agent, try changing the account the service is running under. There may also be an issue with the account that the SQL Server service is running under. Trying changing the SQL Server service account and restarting it. The agent should then start up successfully.
You have two installations, with two named instances. The Express named SQLEXPRESS and the developer edition named MSSQLSERVER (unless you changed this during install). connect to .\MSSQLSERVER and see, it should be there available to be started.
SQL Server Express does not ship with the SQL Server Agent.