This started as an annoyance that has start to become a real problem. I am accessing a file that can be read with OLE DB that I am interrogating and inserting its records into a SQL Server database. The problem is that sometimes this will stop working, and requires a server reboot. The error that comes back is Microsoft.Jet... an error has occurred... Has anyone else had this similar problem, and how were you able to solve it?
After finished a unit test of an ASP.net program, I deleted the data from 3 tables to get ready for a system test. Then during the system test, the PK columns of 2 tables continued the integer number from the unit test. How can I let PKs restart from 1 for the system test and production test, respectively? TIA, Jeffrey
Before I re-install, anybody got a clue? I changed a few parameters in the Enterprise Manger config box, then restarted, but Sql Server did not come back up. REbooted, Sql Server would not come up. Tried to start from command line using "sqlservr -c -dc:mssqldatamaster.dat -f", and it TRIED to come up, but then I got error messages about login for SA. first message said login was successful, but the next message says "login failed" Whats up?
I am using windows Vista that comes with IIS 7. I am trying to figure out how to restart IIS, I went to services & tried to stop IIS Admin but was given a msg saying that you cannot stop this service.
Does anyone know how to successfully restart IIS 7?
Maybe a 'dumb' question, but I can't figure it out. I can't tell from the logs since they are periodically truncated, so how can I tell when the system was last restarted?
I would like to know the period of time that a dmv has been updating a particular view.
I have a package that uses checkpoint restart. It is resposible for truncatings many sets of tables and then loading them. There are several ExecuteSQL tasks to truncate the tables and several corresponding data flows to accomplish the loads.
If a load fails I want the corresponding truncate task to be part of the restart otherwise duplicate data may be loaded. Normally, SSIS will start at the failed task. I read something about containers that led me to think that if I put the truncate & matching load pair in a sequence container that the container would be the restart point, but either I read it wrong or it's not working that way.
Hey all.. I am wanting my SQL Server installation to restart its services at a time I define in the Scheduled Tasks feature of the server its on I need help with command line commands to:- Stop SQL Server Agent service- Stop and Start SQL Server service- Restart SQL Server Agent service Thanks in advance
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.
After the server is booted, our application flies.
After some days ( 1 to 3), the performance starts to degrade until it reaches an unbearable sluggishness. Teh degradation is not continuous, but it shows with time spans (which vary from 1 to 5 hours) during which everything is unacceptably slow. This time spans are usually longer each time they present themselves. There are no errors and if given the time (unacceptable) every workstation finishes its tasks properly.
If we stop the server and reboot it, everything comes back to the initial excellent performance and the cycle of degradation starts over again.
The hardware is excellent and we have checked almost everything that came into our minds, with no results.
Does anyone have any previous similar experiences ? Does anyone have any ideas on where we should focus our search ?
We are migrating the application into 7.0 but I am afraid that our nightmares might continue
I would appreciate all the advice you could give me. Thank you
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?
If the only way to truncate the tempdb fully is to stop SQLServer, how often should this be done? OK I know it depends on your system and the amount of up time, but...
Is there a better way of truncating the tempdb, without stopping SQLServer?
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 am stuck in a strange situation. I have successfully built my application setup through InstallSheild 12. Which first installs SQL Express user define instance as a pre-requisite and then install my application files. First time when i run my application (without restarting the pc), it connects successfully with user define instance. But as i restart my PC and try to open my application, it is not connecting with database. i am using the following command line to install SQL Express 2005 user define instance:
if i change Remote connection to "using both TCP/IP and named pipes" through "SQL Server Surface Area Configuration" and then restart my pc again. My application connects successfully with Database.
Please guide me where i am getting wrong in building setup. do i have to add something in my command line to not get this error
and every time i restart and put it back up ,,,,it rewinds the database
the only way i can prevent this is if i restart the server
wait a phew hours then put it back up ,,"which makes it the same way it was when i logged off"
i was told that sql database servers refresh every hour.
is there a way i can make it refresh before i restart it so then i can put the server straight back up
if i restart the server back up straight away it does a rewind for some reason.
tech ::
the server does a rewind because it wouldn't have saved the game so to speak - as in updated everyone's characters. So yes waiting is the only way as far as I know to save the game.
I would like to be able to automatically restart a package if it fails with a certain error. This is due to a job that fails every now and then due to a loss in connectivity to the database (when run again no issues).
I know how to catch the message, but is there i way that i can in a script task or some other task restart the whole package when moving into the OnError event for the whole package.
I know this isn't a great way to do it, but its just temporary until we can isolate the network issue that is causing the loss in connectivity.
Say I have a conversation established and the initiator server needs to reboot. Will the conversation automatically restart when the server comes back up? If not, can I get it to with some setting? If not, what is the best way to handle this?
I am having five data flow in our package . while executing the package , two data flow are executed sucessfully third data flow throw some error .after issue has been fixed manually(input having some problems , for example the user fixed the problem manually ) while we are try to execute the package by default the third dataflow have to be execute , how i achive this , please help.
I've 3 pc that have MS SQL 2000 database installed in it and connected to main server through merge replication. At first it run fine all the time. But now, it doesn't. It's happen when the pc have to restart every night. When i come to the office and check resplication status it return failed. I try to manually start synchronize but it failed too. I've to restart the pc all over again untill it ok. I hope some body out there can explain something to me and how to overcome the problem...
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 have a SQL 2005 server on a separate machine from my IIS machine, and anytime the SQL server restarts (like for last night's automatic updates) the connection pooling seems to break. Among the apps on this IIS box is Community Server 2.1, along with some other custom-built apps. The only way to resolve it is to stop and restart the IIS services. Previously all SQL-dependent apps on that IIS box broke when SQL was reset, but I seemed to have addressed it, at least on my custom-built apps, by forcing a TCP connection in the connection strings (instead of the default named pipes method). I did change the Community Server connection strings as well, but for some reason that didn't seem to work. Has anyone else experienced similar problems with interruptions in SQL connectivity bringing down apps that connect to that SQL server? I hate to turn off automatic updates just to make sure my ASP.NET apps are available. I apologize if this isn't clearly an ASP.NET question, but hopefully someone can help me out. Thanks,Josh
I set up SQL Agent to start up on a domain account with Administrator rights, and the auto-restart option is on. However, the agent does not restart automatically when restarting SQL Server. No problems restarting manually. The Event Viewer logs the following: "SQLServerAgent security context does not have server-autorestart privileges."
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.
