DB Engine :: Reboot / Restart Service After Setting Max Server Memory
Apr 29, 2015After I have set the maximum sql server memory in sql server 2014 using sp_configure, do I need to reboot whole server or restart sql service?
View 4 RepliesAfter I have set the maximum sql server memory in sql server 2014 using sp_configure, do I need to reboot whole server or restart sql service?
View 4 Replieswe had activity last night we need to truncate Transactional Logs we pressed Restart button to initiate service , but it stopped successfully and failed to start the SQL Server service.We did not find anything find anything unusual in log file. Please confirm are we facing any bug or needing any fixes to installed on the server.Windows Server 2008 R2 Standard Service Pack 1 ( 64bit)
View 6 Replies View RelatedOne server, a part of a 2 node always on cluster, had problems, I had to restart.
I'm getting this error for example now:
Error: 49910, Severity: 10, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
+
SQL Server was unable to run a new system task, either because there is insufficient memory or the number of configured sessions exceeds the maximum allowed in the server. Verify that the server has adequate memory. Use sp_configure with option 'user connections' to check the maximum number of user connections allowed. Use sys.dm_exec_sessions to check the current number of sessions, including user processes.
Now, on the instance I have activated maximum servere memory, my question; Is it possible to adjust this setting without starting the service?
Some parameter for example?
The server itself have enough memory.
This computer gets set to autostart the SQL Server Service, which is set to local, (have also tried local network and user specific), and everything works fine. But when it gets rebooted, the service refuses to start.
We disabled the Mcafee and Windows firewall. No effect.
The SQL Browser and Full Text Index Services start automatically just fine.
Anyone have any experience with this?
Thanks,
Pat
Hello all,
We are using sql server 2005 for full text searching.
I removed some of the words in the noise word file (noiseENU.txt) and rebuilt the catalog. However i find that the changes made to the noise file do not reflect immediately. I had to restart sql server engine before my queries returned results according to the updated noise list. Is there a workaround for this ( wherein there isnt the neccesity of restarting sql server engine....this is becoming a problem on live environments as i cannot restart the server when needed)?
Thanks in advance,
Harish
hello,
View 1 Replies View RelatedHi
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.
View 1 Replies View RelatedI 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 have a few SQL instances on my server (jdjfdijdk)
They where called and organized like this:
MyServer - Database1
MyServer/BBserver - Database2
For some reason instance MyServer/BBserver has stopped and I couldn't make it start so I decided to reboot the server. After reboot the MyServer/BBserver was working but when open the other instance MyServer using Management Studio the Database1 disappear and the Database2 can be accessed by MyServer/BBserver and MyServer instances.
Even a backup made of Database1 and stored at
C:Program Files (x86)Microsoft SQL ServerMSSQL.2MSSQLBackup vanished.
How to recover Database1?
I need to be able to restart an application service after the SQL Cluster fails over. how to accomplish this as a SQL job?
View 1 Replies View RelatedHi,
I'm having trouble with restoring the master db on w2k3 sql2000 sp3a to a Secondary Standby server.
Firstly, I place the server in Single user mode and then restore the master db. The sql server then tries to restart sql services but immediately stops as soon as it starts up.
Can anyone help ?? Please !
Thx, Steve
Is a restart of SQL Server required after changing the 'clr enabled' setting? The SQL documentation clearly states that a restart of SQL Server is not required:
The clr enabled option is an advanced option. If you use the sp_configure system stored procedure to change the setting, you can change clr enabled only if show advanced options is set to 1. The setting takes effect immediately after sp_configure is run. No restart of the SQL Server instance is required.
I've seen updated documentation where it points out that this setting is not really an advanced setting, so, there is one error that was corrected. Also, the documentation seems to imply that RECONFIGURE is not needed. Although, after you run EXEC sp_configure 'clr enabled', 1;, you get:
Configuration option 'clr enabled' changed from 1 to 1. Run the RECONFIGURE statement to install.
My issue is that our installation kit runs the following comands:
EXEC sp_configure 'clr enabled', 1;
RECONFIGURE
I it tries to load a SQL stored procedure which references a CLR function that will be defined later in the process. The following error is returned.
Msg 5847, Level 16, State 88, Procedure f_altFillPriceFormatted, Line 20
Execution of .NET Framework code is disabled. Set "clr enabled" configuration option and restart the server.
The setting has already been set as I can see using SP_CONFIGURE. If I restart SQL Server as the error message states, the load of the stored procedure finishes successfully.
Is there some other setting that I can call to force SQL Server into believing that the clr is enabled? Or, is this simply a documentation error where a restart really is required?
thanks,
- Paul -
I have a clean SQL 2005 Ent. x64 SP1 clean with no user db's.....applied SP2 and everything showed "Success" except the Database Services (Error 29534)......
Time: 02/22/2007 08:29:50.134
KB Number: KB921896
Machine: TORCA8
OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790)
Package Language: 1033 (ENU)
Package Platform: x64
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
Cluster Installation: No
**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed
**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Setup Support Files ENU 9.1.2047 x64
Database Services (MSSQLSERVER) ENU SP1 2005.090.2047.00 x64 ENTERPRISE
Analysis Services (MSSQLSERVER) ENU SP1 2005.090.2047.00 x64 ENTERPRISE
Reporting Services (MSSQLSERVER) ENU SP1 9.00.2047.00 x64 ENTERPRISE
Notification Services ENU SP1 9.00.2047.00 x64 ENTERPRISE
Integration Services ENU SP1 9.00.2047.00 x64 ENTERPRISE
SQL Server Native Client ENU 9.00.2047.00 x64
Client Components ENU SP1 9.1.2047 x64 ENTERPRISE
MSXML 6.0 Parser ENU 6.00.3890.0 x64
SQLXML4 ENU 9.00.2047.00 x64
Backward Compatibility ENU 8.05.1704 x64
Microsoft SQL Server VSS Writer ENU 9.00.2047.00 x64
**********************************************************************************
Products Disqualified & Reason
Product Reason
**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID
**********************************************************************************
Product Installation Status
Product : Setup Support Files
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlSupport.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 2047
Product Version (Final) :
Status : Failure
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29534
Error Description : MSP Error: 29534 Service 'MSSQLSERVER' could not be started. Verify that you have sufficient privileges to start system services. The error code is (1067) The process terminated unexpectedly.
----------------------------------------------------------------------------------
Product : Analysis Services (MSSQLSERVER)
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixOLAP9_Hotfix_KB921896_sqlrun_as.msp.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Reporting Services (MSSQLSERVER)
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRS9_Hotfix_KB921896_sqlrun_rs.msp.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Notification Services
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixNS9_Hotfix_KB921896_sqlrun_ns.msp.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Integration Services
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixDTS9_Hotfix_KB921896_sqlrun_dts.msp.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : SQL Server Native Client
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_sqlncli.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Client Components
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : MSXML 6.0 Parser
Product Version (Previous): 3890
Product Version (Final) : 6.10.1129.0
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_msxml6.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : SQLXML4
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_sqlxml4.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Backward Compatibility
Product Version (Previous): 1704
Product Version (Final) : 2004
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SQLServer2005_BC.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Microsoft SQL Server VSS Writer
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlWriter.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
**********************************************************************************
Summary
One or more products failed to install, see above for details
Exit Code Returned: 29534
Now SQL Server service won't restart.....
2007-02-22 10:16:31.28 Server Microsoft SQL Server 2005 - 9.00.3042.00 (X64)
Feb 10 2007 00:59:02
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)
2007-02-22 10:16:31.28 Server (c) 2005 Microsoft Corporation.
2007-02-22 10:16:31.28 Server All rights reserved.
2007-02-22 10:16:31.28 Server Server process ID is 2056.
2007-02-22 10:16:31.28 Server Authentication mode is MIXED.
2007-02-22 10:16:31.28 Server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'.
2007-02-22 10:16:31.28 Server This instance of SQL Server last reported using a process ID of 576 at 2/22/2007 10:16:15 AM (local) 2/22/2007 3:16:15 PM (UTC). This is an informational message only; no user action is required.
2007-02-22 10:16:31.28 Server Registry startup parameters:
2007-02-22 10:16:31.28 Server -d E:SQLDatamaster.mdf
2007-02-22 10:16:31.28 Server -e C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG
2007-02-22 10:16:31.28 Server -l F:SQLLogsmastlog.ldf
2007-02-22 10:16:31.28 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-02-22 10:16:31.28 Server Detected 4 CPUs. This is an informational message; no user action is required.
2007-02-22 10:16:31.28 Server Cannot use Large Page Extensions: lock memory privilege was not granted.
2007-02-22 10:16:31.40 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2007-02-22 10:16:31.42 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2007-02-22 10:16:31.50 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 36200, committed (KB): 104760, memory utilization: 34%.
2007-02-22 10:16:33.45 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2007-02-22 10:16:33.45 Server Database mirroring has been enabled on this instance of SQL Server.
2007-02-22 10:16:33.47 spid5s Starting up database 'master'.
2007-02-22 10:16:33.47 spid5s SQL Trace ID 1 was started by login "sa".
2007-02-22 10:16:33.48 spid5s Starting up database 'mssqlsystemresource'.
2007-02-22 10:16:33.48 spid5s The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2007-02-22 10:16:33.48 spid5s Error: 5173, Severity: 16, State: 1.
2007-02-22 10:16:33.48 spid5s One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup.
2007-02-22 10:16:33.48 spid5s Error: 5173, Severity: 16, State: 1.
2007-02-22 10:16:33.48 spid5s One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup.
2007-02-22 10:16:33.48 spid5s Log file 'F:SQLLogsmssqlsystemresource.ldf' does not match the primary file. It may be from a different database or the log may have been rebuilt previously.
2007-02-22 10:16:33.48 spid5s The log cannot be rebuilt when the primary file is read-only.
2007-02-22 10:16:33.48 spid5s Error: 945, Severity: 14, State: 2.
2007-02-22 10:16:33.48 spid5s Database 'mssqlsystemresource' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2007-02-22 10:16:33.48 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
Tried reinstalling SP 2 in quiet mode using sapwd parameter.....now everything is showing the correct SP2 version but SQL Server Service won't start.......anyone????????
I have an issue with my production server regarding memory usage (Memory Utilization is above 95%.). Memory is : 12 GB and the service that is consuming the majority of memory 88%/10.5GB is sqlserver.exe. So it would appear that MSSQL is not set to restrict the amount of memory it uses ? How much should I set for min and max memory ? the defauld is min memory : 0 and max : 2 TB
View 5 Replies View RelatedI am running SQL 2005 Standard under Windows 2003 Standard with 8 GB of RAM in one of our 64 bit servers; I noticed min server memory was set for some reason to 128 MB and max server memory to 6114 MB by the previous DBA. We plan to upgrade it to 32 GB. What is the best approach when changing those values ? Should I change those values to the defaults (0 - 2147483647) or create min and max boundaries? . This box is only utilzed by SQL.
Also I know that those changes are reconfigured dynamically so no need to reboot, but would this place any performance hit in the server and should I use Management studio or sp_configure ? (for some reason I don't trust Management studio for these type of changes :))
Thanks,
Carlos
Is there any easy way to detect SQL Server memory is getting paged out? Any DMV query or tips to confirm it is paging out.
My SQL Server Version is: Microsoft SQL Server 2008 (SP3) - 10.0.5500.0 (X64)
Is there has any SQL query to check running out of "min memory per query SQL Server"(default value is 1024KB)?
View 2 Replies View RelatedGot an issue:
I am running SQL Server 7.0 on a Web server and recently the SQL Server has been acting up. Basically what happens is every time the server is restarted the Service Manager fails to restart. I even get an error telling me that the service failed to start. So, when I log back in I have to physically restart the Service Manager. I have the services set to start automatically. Can anyone direct me where to look...perhaps a SQL Server log that might give me a clue. My application and error logs only tell me that it stops. Any ideas?
I am curious about maximum memory setting .
Should we set maximum memory setting for each SQL server? For example a server has 6 GB memory then should we set maximum memory setting = 3.5 GB ?
How to set maximum server memory by using sql scripts in sql server 2014?
View 5 Replies View RelatedWe have a new set up on VM to run an application running 24*7 (migrated from SQL server 2008R2) with below configs:
1. OS- Windows server 2012 Standard 64 bit hosted on Virtual Machine
2. Memory 16 GB and Cores =4 with 2.4GhZ processor
3. SQL server 2012 SP2 , 64 bit Standard edition.
4. Total size of databases as of now 15 GB with biggest being 5 GB.
How should i go around in setting the MAX and MIN server memory settings. I have this set up for many of SQL 2005 and 2008R2 servers, but for 2012 i heard that things has slightly changed.
How should i start analyzing and setting the right value of this MAX and MIN?
On first Node A: The server has 16 GB of physical RAM.
On second Node B: The server has 10 GB of physical RAM.
Now, this being Active Active, Node A can be clustered on failure onto Node B..Now reporting server is configured under these two nodes, with defined MAX and MIN server memory of 12 as MAX and 0 is min IN GB.Now with this setting on SQL whenever the cluster moves, such config make OS goes low on node for 10 GB.I am only left with option of switching this MAX and MIN to a default setting or is there any other alternative such as script which can change this setting accordingly when cluster moves to respective server.
I am searching for query to find total memory allocated to sqlserver, and how much being used utilized as well cpu utilization percentage .
View 10 Replies View RelatedHi,
I am testing SQL 2005 Standard (32 bit) on a Windows 2003 Server 64 bit with 8GB of RAM? Should I enable the AWP Setting or not and should I change the maximum server memory (currently saying 2GB)?
Thanks!
Tom
We have several 2005 servers with "Maximum server memory" set to 214 gig, which I believe is the default at installation time. I am told that this means "use all the memory there is including paging." Well, this is nuts but the servers seem to work fine with this setting no matter how much physical memory they have.
One of our 2005 servers recently started paging like crazy, so I reduced "Maximum server memory" to 6000 and the paging disappeared (server has 8 gig of physical memory) and the server appears happy.
I can not explain why only this one server has this paging issue and the others do not. Should I be setting "Maximum server memory" on all my servers? Are there other considerations which might cause the server to eat-up all the memory? As far as I know no other applications run on this box.
Thanks,
Michael
Anyone know of a query that will cycle the SQL service?
View 6 Replies View RelatedWhen I re-boot the machine, if the sql server is set to "automatic", will the service re-start when re-booting the machine?
View 1 Replies View RelatedI am having trouble with a linked server using MSDASQL. I'm connecting to a PostgreSQL database and pulling over data. This process has been working fine.
In trying to pull data from a different client database (same schema), I received an error that the MSDASQL couldn't read the column names.
The actual problem I want help on is that after this happens, I am no longer able to make valid connections to any of my Linked Servers using MSDASQL. The only way I can get my other linked servers to work again is to restart the SQL Service. Usually this is impossible for me to do because of the number of active users.
Two questions:
1) Is there another way to restart a more targeted service or sub-set to reset MSDASQL connections, and clear out my problem?
2) Any idea why I'm getting this error connecting to PostgreSQL on a large dataset when it worked fine for a small dataset using the same linked server? "The provider reported an unexpected catastrophic failure."
Any help is appreciated.
Every so often I get an error when I pull up an ASP.NET 2.0 site using
SQL Express. It tells me that the login failed. If I go
into the server's administrative tools > services and restart SQL
Express and then refresh the site, it works just fine. Is this
some sort of bug or memory issue? Does the application need to
connect every so often or end up falling out somewhere?
Thanks
I inherited a SQL 2012 Ent server sitting on a 2008R2 server using AlwaysOn High Availability, two nodes.
Available Mode: Synchronous commit
Failover Mode: Manual
Connection in Primary role: Allow all connections
Readable secondary: No
seesion timeout: 10
Somebody decided to give SQL server priority boost so I need to change this ASAP. So I plan on doing the following.
1. Manually fail over to the secondary, which does not have the priority boost set to true
2. change the setting
3. restart the service
4. Manually fail over
My question is with the service restart. How does SQL handle if the DB changes on the new primary while the secondary is having the service restarted. Where can I see if the DB are sync again or if not where are they in the sync process.
A few service stop/start/restart questions on SQL Server 2005 SP2, whichI'll call SQLS.It looks as if there are *potentially* 6 ways to start/stop SQLSServices like the engine itself, integration services, reportingservice, Agent..-SQLS Configuration Manager-SQLS Surface Area Configuration (for Services and Connections)-Mgmt Studio Local (on server)-Mgmt Studio Remote (on client)-Windows Control Panel->Admin Tools->Services-Command Prompt (ala net start MSSQLSERVER)By policy, I am /not/ Administrator on the server. But I am SysAdminrole in SQLS. I have had various levels of success starting/stoppingservices in the ways listed above. In some I get Access denied, and inothers I get no msg and it simply doesn't work.Is there some special non-Admin OS group I need to be in to start/stopservices? Is this handled differently in the different interfaceslisted above?It seems like my best success for starting/stopping the engine and Agentis in /local/ Mgmt Studio, but /not/ remote Mgmt Studio - the optionsare greyed out on a remote client. Is this by design? Is it a SQLSbug?I'm sure I'm not the only SQLS DBA who does not have Admin rights on hisserver who wants to start/stop services. Generally speaking, how isthis intended to work?Any help appreciated.Allen JantzenA freshly minted DQLS DBA
View 1 Replies View RelatedI have a problem that has happened a couple of times now. I'm in the process of testing our 2005 deployment - Standard edition on 2003 x64 servers for principal and mirror and 2005 express witness. All are pre SP1. Two databases are being mirrored.
I have successfully set up mirroring which seems to work fine - but when I restart the MSSQL service on the principal, spurious things happen:
The server that *was* the principal before restart
database A is in (Mirror, Disconnected / In Recovery) state
database B is in (In Recovery)
The server that *was* the mirror:
database A is in (Principal, Disconnected)
database B is in (Principal, Disconnected)
I can connect to both servers via Studio Manager and when I try to go to the current principal database to stop mirroring, the Studio Manager hangs and becomes non-responsive.
Any ideas?
Thanks