I am looking to add replication to an existing instance of SQL Server 20212. I am running it as admin. When I select add new features and point it to the cd it says I must restart the server. Can I bypass the restart? The server is my production 24/7 machine. Can I add replication without restarting my server?
Related
I have a website that runs on Microsoft server (I have a remote desktop connection) with the SQL database. I want to enable remote access to the SQL database, without restarting the service. Is that possible?
I had SQL Server 2012 Express installed on my PC at work, but we received a file from a client the was created in SQL Server 2014. Please keep in mind, I am newbie, and I only made this mistake about 7 months ago
I tried to install SQL Server 2014 Express as another instance on my PC along with SQL Server 2012. After noticing that my new SQL Server instance did not work and my old SQL Server did not work, I looked online and found that what I did was a step up from what an ape would do. Always read before attempting an install.
After un-installing SQL Server 2014 I tried to relaunch SQL Server 2012, but it would not connect to my instance that I was able to just before.
I now get this error:
Cannot connect to STID02\SQLEXPRESS.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (.Net SqlClient Data Provider)
I have also read this thread Can't connect to SQL Server 2014 Express and found that the SQL Server service is stopped and I cannot start it, and the SQL Server Agent Service is stopped and won't start either.
I have not been effected by this until recently, I need to do some testing with DB's but I need my local instance to do the testing. I would appreciate any advice, as I am still new to SQL Server and most computer related things I would be very thankful to those how can dumb it down extremely low.
Thank you -Anthony
In short, uninstall everything, then reinstall the version you want to use.
Some configuration files must have been overwritten by SQL Server 2014. Don't worry, it can be fixed.
First: do you need any of your existing databases? I assume not as you haven't been using SQL Server for the last 7 months. If you do need some of the databases you'll find the .mdf, .ldf files in you SQL Server installation folder somewhere in the DATA folder.
Then: Uninstall SQL Server 2012 - note that since you've corrupted your current installation it might happen that some registry entries will be bad and/or services or libraries won't be removed. In that case fix the registry entries using some tool, like CCleaner, and try again to remove those programs/services.
Last step: reinstall whichever version you want. If you needed your previous databases overwriting the new mdf/ldf files should do the trick (of course while the server is not running). You can check the server's state from the SQL Server Configuration Manager or from Services.
Trying to install Sitecore 7.1 on local machine but getting an error while attempting to connect to SQL Server. If I browse for a Database Server nothing comes up in the list. I have SQL Server 2012 installed and several databases that were created from Visual Studio. What am I missing to make the connection?
For some it may be a case of the SQL Server Service has stopped running. To turn it back on:
Open up Sql Server Configuration Manager.
Select SQL Server Services in the tree view on the left
In the Context Window on the right check to see if your SQL server service is turned off.
If it is right click and click start.
I've installed SQL Server 2012 Express advanced edition on a clean (just OS without any third-party soft) w7x64 residing on VirtualBox 4.1.18. I’ve chosen every needed option to install, but after installation there is no SQL Server Express service running on guest OS on virtual machine. Also I have the same edition of SQL Server installed on my host OS which is also w7x64. Please give me any clues to what may be the cause of this issue.
Steps to diagnose:
Check in Control Panel -> Services that the SQL service is running
Try to connect from the local machine, type osql -E -S localhost\sqlexpress in a command prompt.
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.