I am unable to login to the sql server as I would like to reboot the server, please let me know how I can do the following remotely in such a scenario:
1. Reboot the sql server
2. Restart the mssqlserver and sqlserveragent services
Thanks.
I've been dealing with a few problems with SQL Server 2005.
We don't want to give our DBA's local administrator access to the servers so we had a problem with SSIS which I managed to resolve by adding their global group into the local DCOm group and modifying the security properties of MsDtsServer.
Another problem I've come across is when you log into Management Studio as an account that has local administrator access to the server you have the Green symbol next to the registered server, you can then right click and Stop, Restart services etc.
If I log into Management Studio with an account that has full SQL sysadmin rights but not local administrator rights to the server then the Green symbol doesn't appear and the Stop, restart options are all greyed out - all other functionality appears okay, they just seem to lose the ability to remotely stop and start services.
All of the above is with Windows Firewall turned off, if the user has local administrator rights but the SQL Server has the Windows Firewall switched on they are unable to remotely stop and restart services.
Port 1433 is open on the firewall and program execptions are there for sqlbrowse.exe
Anyone come across this particular problem before?
I have an SQL Server 2012 with SSIS installed on Windows Server 2008 R2 Core. I'd like to connect remotley to SSIS but I receive the following error. 'The RPC server is unavailable.'
We manage some SSIS servers, which has only SSIS and SSIS tools installed on them and not the sql server DB.
SSIS packages and configuration files are deployed on a NAS. We run the SSIS packages through DTEXEC by logging in to the server.
We want to allow developers to run their packages on their own on the server, but at the same time we dont want to give them physical access on the server i.e we do not want to add them into RDP users list on server properties. We want them to allow running their packages remotely on the server.
One way We could think of is by using powershell remoting and we are working on that. But is there any other way or any tool already present for the same.
we run std 2008 r2. I'll be putting together a pkg whose last step needs to execute a program that resides on a remote (not same as where pkg runs) computer and that program must run on the remote computer. Return code(s) would be important to the pkg. I see talk about running over http which may or may not be possible with that remote ws 2003 sp2 server.
The pkg will be running on a ws 2008 r2 std sp1 machine.Does the community have any recommendations for running a remote program from ssis?
As I think about it, i'm not a big fan of making a pkg wait for another process synchronously. So I may just want to trigger the remote program and let something I would set up on the remote server tell me daily if the program succeeded. Interestingly this is a rewrite of a pentaho job that does wait for the remote program execution. I suppose installing ssis on that remote server is an option but I think i'd get a lot of resistance going that route. I'll probably be triggering a sql agent to ssis job after that remote program finishes.
Has anyone ever experienced the SQL Server unexpectedly rebooting?
Yesterday my SQL Server 7 installation rebooted itself and the error log seemed fine as did the restart. The only evidence I can find was a message in the event viewer's application log stating the the MSSQLServer service terminated unexpectedly. Any ideas are appreciated.
I've a SQL server that intermittently restarts itself mostly during. Its a SQL Server 6.5 SP4 running NT 4.0 SP6. It really has no rhyme or reason to it happening. The are no indications in either the SQL or the Nt events logs. Has anyone heard of this?
I have a linked server set up to a proprietarty temporal DB through an OLEDB provider. From time to time and for various reasons the OLEDB provider crashes with "Error 7302 Could not create an instance of OLE DB Provider 'IhOLEDBProvider.iHistorian.1'. OLE DB Trace [Non Interface Error: CoCreate of DSO for IhOLEDBProvider.iHistorian.1 returned 0x80070008"
Up till now, to re-initilize the connection we have just restarted the SQL Server service. However, some automated processes are now feeding data into this server and more users and have started coming online so restarting for this issue has become a big deal.
Getting the OLEDB provider sorted out isn't an option at present so my question is:
Is there a way to re-initalise a failed linked server other that restarting the SQL Service?
I have SQL server running on windows Adv Server 2000. Since last couple days whole computer restart every one hours. Only thing I remember doing was to shrink database db size is 200+GB.
I've got a table with a column that contains the status of available licenses to the user, i.e. they are either in use or are available. If the server goes down, then when it is restarted I need to make sure all the rows in this column describe each license as being available.
So the question is how can I ensure data in a table is, if you like, initialized, each time the server is restarted? Is there a system defined stored proc or trigger than is executed when a server is restarted?
i hv a database (sql server 2000) where i got locking on many tables and my application was down.
I restarted the sql server and the application was fine but after five minutes the same locking issue started happening. I did a index rebuild the next time on all indexes and everything was fine.But i cannot relate how locking occured and why it was not after index rebuild.Can anyone shed some light on this or anyone had similar experience... cos i cannot figure out a way on this.
I setup Sql agent for autostart with sql server and autorestart if stoped but after rebooting NT or after stoping SQL server it never starts ,I have to start it manualy
I have an old application to maintain that uses CDatabase to connect to SQL Server. If SQL Server is stopped and restarted, such as in a cluster failover (i.e. move group), then the CDatabase connection needs to reconnect. It seems that it's not capable of doing this on it's own so I need to check the state some how. Various methods, such as IsOpen, seem to be useless as far as determining if I have a "good" connection.
@@servername sometimes returns NULL depending on how you have been messing around with replication and various other settings.
The simple solution offered to fix this is to delete the entries in the system tables and sp_addserver 'servername','local' and then restart the SQL service.
This is fine but what do you do in the situation where the SQL server is a 24/7 production box ? Does anyone know of a method / hack to fix this without stopping the service ?
We were trying to restore our production server db backup in test server over LAN (due to space shortage on test server) . Test server hanged and did not respond for abt more than 15 hours (backup file 40 GB ) . The we restarted the server (resetting the power button) . Now it's showing the status 'Restoring' . According to me it's not doing anything (as seen in task manager workload ) . So how can I go ahead with checking the db .
Due to 'restoring' status I get following error ------------------------------------ Msg 927, Level 14, State 2, Line 1 Database 'envdb' cannot be opened. It is in the middle of a restore. ----------------------------------
Our inhouse app used to run on a SQL2000, but we've recently moved it to 2005. The move was done by way of backup and restore (it was on a whole new server).
After the move, an odd problem showed up: once in a while, the server seems incapable of finding/using its indexes: everything starts working slowly, until I run a maintenance plan that rebuilds its indexes etc. In the database/server all relevant options seem to be ok (auto update statictiscs etc.), and my conclusion that it doesn't use its indexes comes from the fact that: * it gives the results from certain select statements in a totally different order (although the set of rows is the same), * performance is (all of a sudden) very slow (seconds turning to minutes!!)
This happens: * at least after a reboot of the server * sometimes just in the middle of the day
The only way I've found to solve the matter, is by running the maintenance plan to rebuild the indexes, but sometimes this only seems to work the second time.
Does anybody share this experience, or know what to do about it?
I've installed an SSL certificate via IIS. I stopped sql server and agent but cannot restart them. I'm getting the following message in the error log:
2007-10-31 21:24:53.63 Server Error: 17182, Severity: 16, State: 1. 2007-10-31 21:24:53.63 Server TDSSNIClient initialization failed with error 0x2, status code 0x38. 2007-10-31 21:24:53.63 Server Error: 17182, Severity: 16, State: 1. 2007-10-31 21:24:53.63 Server TDSSNIClient initialization failed with error 0x2, status code 0x1. 2007-10-31 21:24:53.63 spid9s Starting up database 'model'. 2007-10-31 21:24:53.63 Server Error: 17826, Severity: 18, State: 3. 2007-10-31 21:24:53.63 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log. 2007-10-31 21:24:53.63 Server Error: 17120, Severity: 16, State: 1. 2007-10-31 21:24:53.63 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
I've tried removing the SSL certificate but with no success.
Help! I'm starting to think that the only solution is to uninstall sql server 2005 and reinstall.
We have been having a problem with on of our servers, applications connecting to it are experiencing poor performance, even though the server is only running at a peak of 50%.
The odd thing is that after a sql service restart we couldnt connect at all on the SQL port. We were only able to re-connect after rebooting the actuall box. Is there anything that can be done about this? Its strting to look like a network related problem instead of SQL
I have got the error “a network related or instance specific error occurred sql server 2012 “.I have enabled tcp/ip, restarted the services. The sql server service is getting stopped even after the manual restart. I have checked in event viewer and I noticed a error. Here is the error...The log scan number (43:456:1) passed to log scan in database ‘model’ is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication.
Is there a way to find the max number of sessions that were on a sql server since its last restart? I know how to get how many total connections there were since last restart, and the current number of sessions, but not the max number of sessions that were running since last restart. Also, opinion on the optinum number of allowable sessions, or a good way to figure out the balance?
I have a service that depends on SQL Server service. Basically we make sure that our service only starts after SQL server service started. Unfortunately this dependency does not ensure that database is available.
Basically I observed in Application log that SQL server reports that it started to listen on a port. And then I see that recovery process started. As I understand SQL server is not available while database is in the recovery state.
Note: I might have not used a correct terminology to describe SQL server recovery process as I don't have access to Application log with the exact message at the moment. I can verify the message if necessary.
Because SQL server service is started our service starts and attempts to connect to the database. Service fails to connect to database, because of the restoration process. Once restoration is done service connects successfully.
I observed that restoration process starts every time machine is rebooted. It only takes a few minutes to run, but it is enough to generate a number of error messages in event log about failed SQL connections.
My first question is: Is it normal for database to enter into recovery state every time machine is rebooted?
My second question is: If it is a normal operation, is there any way to detect that SQL server is truly available, so our code does not have to try retry establishing connection many times
I've combed through SQL Help to find the answer to my question but I think it's telling me it can't be done. I work both from an office with my servers and from home. When I'm at home I would like to access my SQL server remotely using a tool such as MS SQL Server Management Studio. But it appears there is no way to access my SQL Server for management purposes using Management Studio over a remote internet connection. I can access the server using Management Studio while I'm on the internal office network but not from home. Has anyone been able to do this or might recommend a third party tool as robust as Management Studio? Thanks
I just reinstalled SQL Server and after reattaching my databases, I can't connect remotely. If I use "localhost" in my connection string it works fine, but I can't register my remote Enterprise Manager this way.
Can someone tell me if it is possible to register and connect to a SQL server that is not on my local network? I want to be able to use the Enterprise Manager to make updates to the SQL servers in my office from home. I am using SQL 7.0
I have heard a lot of people saying that they administe the SQL Server remotely , I mean sitting in one city , they work on the SQL Server in another city.
How is this actually achieved . Is it that the SQL Box is given a real Ip & then they connect it though the internet, but then this would not be safe , as the SQL box would be on the real Ip.
Could some one please let me knw the ways (solutions) to access & adminster a SQL Server remotely. (Not on ones LAN ) ...
I have a sql server 2005 remotely, need to connect from client using sql management studio. I am unable to connect from one of the client machine and able to connect from different machine.
The tcp/ip, named pipes and sql browser is enabled in server and windows firewall is off in client.
I am getting (provider: sql network interfaces, error 26 - error locating server/instance specified)