I changed the Fill Factor option from 1 to 75.
When I run a query that displays the fill Factor I am seeing 75
But I read online that I have to stop and start the sql Server services inorder for this change to be effective. Is that True?
Blockquote
You must stop and restart the SQL Server service for the change to take effect. The new fill factor will be in effect when you see it in the run-value column.
Blockquote
In my 2008r2 enterprise when I changed it via clicking on the instance, right clicking selecting database and changing the fill factor the change did not take effect until I stopped and started the instance.
I tried changing it through TSQL:
EXEC sys.sp_configure 'show advanced options', '1'
RECONFIGURE WITH OVERRIDE
GO
EXEC sys.sp_configure 'fill factor (%)', '30'
GO
RECONFIGURE WITH OVERRIDE
GO
EXEC sys.sp_configure 'show advanced options', '0'
RECONFIGURE WITH OVERRIDE
GO
Still need a stop/start (bounce) to take effect.
Related
I can't find the 'locks' information in sp_configure.
I am using SQL Server 2016 (v13.0.5820.21).
I understand I should be able to find it on the 'Advanced' tab on the server properties, but is that normal? How can I bring up the 'locks' information in sp_configure?
Thank you for your answer..
The locks option is an advanced one, and is not shown by sp_configure by default. In order to see it, you need to enable advanced options first:
exec sp_configure 'show advanced options', 1;
go
reconfigure;
go
Then it will show up.
I have a very strange situation on SQL Server that I cannot fathom out.
Environment : SQL Server 2012 SP3 CU3 running on a 2 node Windows 2008 R2 cluster
In SQL Server Management Studio\Management\Maintenance Plans\ I am unable to create or edit existing plans.
I receive the error:
'Agent XPs' component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Agent XPs' by using sp_configure. For more information about enabling 'Agent XPs', see "Surface Area Configuration" in SQL Server Books Online. (ObjectExplorer)
Checking around that error I expected the following config was going to be required.
-- To allow advanced options to be changed.
EXEC sp_configure 'show advanced options', 1;
GO
-- To update the currently configured value for advanced options.
RECONFIGURE;
GO
-- To enable the feature.
EXEC sp_configure 'Agent XPs', 1;
GO
-- To update the currently configured value for this feature.
RECONFIGURE;
GO
However, I noticed that SQL Agent was already running so I thought I would also check existing config options for 'Agent XPs'
What was interesting was that config_value = 0, run_value = 1 where I was expecting config_value = 1, run_value = 1.
I thought I'd try the sp_configure solution to 'force' the config but when I ran it (step by step), the first RECONFIGURE statement just hung and indeed when it ran I could not even run an sp_who2 to see if it was blocking or being blocked.
The only way I could kill the RECONFIGURE was to close the query window which cancelled it. I therefore am unable to run EXEC sp_configure 'Agent XPs', 1 as the required RECONFIGURE cannot be run.
After a failover of the cluster, the config settings for 'Agent XPs'
remains at config_value = 0, run_value = 1.
Has anyone got any ideas as to how to fix it?
I stumbled across an internet post with a similar issue and that contained a nugget of information that allowed me to ultimately fix the issue.
I documented the case over at SQLServerCentral
https://www.sqlservercentral.com/Forums/1927277/SQL-Server-2012-tells-me-Agent-XPs-component-is-turned-off-but-SQL-Agent-is-running
I'm currently on a host(A), connecting to a MSSQL database on server(B).
When I do a System call, such as
EXEC xp_cmdshell 'Systeminfo' GO
from within MS SQL 2008 it always returns me system information from the client(A) I'm currently running my SQL management tool on.
Is there a possibility to run System calls that will return me information from the server(B)?
I have since asking this question rebooted, and tried all the steps again:
1. Turn off local server
2. Connect to external server
3. Turn on XP_CMDSHELL command for the external server using
-- To allow advanced options to be changed.
EXEC sp_configure 'show advanced options', 1;
GO
-- To update the currently configured value for advanced options.
RECONFIGURE;
GO
-- To enable the feature.
EXEC sp_configure 'xp_cmdshell', 1;
GO
-- To update the currently configured value for this feature.
RECONFIGURE;
GO
And then just run
EXEC xp_cmdshell 'Systeminfo';
GO
Weird that it works now,because I couldn't get it to work past weeks.
It might be very basic question for you friends, but how to allow multiple users on SQL Server installed on remote windows server 2012 machine.?
right now only two user can work at the same time if third one comes one of two who are active has to allow and get out himself.
we are building new server which will allow multiple user to work on the same time.
My question is once we install SQL server on windows server machine what configuration needs to be done to achieve our goal(Multiple user can work on same time) on server machine as well as what configuration needs to be done on computers of people who will be logging into it.
do we need same number of instance similar to how many people will be working on it? if yes it means that many number of same database on the server and more space will be occupied right?
Thanks.
EXEC sp_configure 'show advanced options', 1;
GO
RECONFIGURE;
GO
EXEC sp_configure 'user connections', 777;
GO
RECONFIGURE;
GO
Replace 777 with your limit of connections.
When I run MPR test for Microsoft azure, I got below two issues:
1. Which parameters I have to select in 'SQL Server 2014 Online Transaction Processing and Data Warehouse Gold Tests'
Partitioning
In-Memory OLTP Tables
Clustered Columnstore Index
Resource Governor
Encrypted Backups
2.'Default Trace should be turn on' Status shown as 'off', How to handle this?
1.Those tests are designed to see ,if your application passes them,one way I see them is select all,if you are not using those features,you will not see any issues.If you are using those,they will be tested to see if they meet criteria..
2.
This turns default trace on
sp_configure 'default trace enabled' ,1
reconfigure
Default trace runs always ,I am not sure why it is stopped in your infra .if you want to stop it,you can use below command
sp_configure 'default trace enabled' ,0
reconfigure