Is there any better way to detect sp_configure changes

begin
IF object_id('msdb..sys_configurations') is null
begin
select * into msdb..sys_configurations from master.sys.configurations
end

-- set servername in subject line
declare @sub nvarchar(255) = 'SQL Server Instance configuration has been changed ' + cast(@@servername as nvarchar)

-- pick one mail profile if there are multipal mail profiles
declare @pf nvarchar(255)
select top 1 @pf= sp.name from msdb..sysmail_profile sp
join msdb..sysmail_profileaccount spa on sp.profile_id=spa.profile_id
join msdb..sysmail_account sa on spa.account_id=sa.account_id

-- send email for notification ONLY if there is difference between master.sys.configurations and msdb..sys_configurations
if exists (select * from master.sys.configurations except select * from msdb..sys_configurations)
begin
EXEC msdb..sp_send_dbmail
@profile_name = @pf,
@recipients = 'sendit2me@somewhere.com',
@subject = @sub ,
@body = 'System configuration has been changed ',
@execute_query_database = 'msdb',
@query =
'with cte_config as
(select * from master.sys.configurations except select * from msdb..sys_configurations )
select ''CHANGED FROM <<--'' as [<<<<<<<<<<<<<<] ,* from msdb..sys_configurations where configuration_id in (select configuration_id from cte_config);
with cte_config as
(select * from master.sys.configurations except select * from msdb..sys_configurations )
select ''CHANGED TO ---->>'' as [>>>>>>>>>>>>>>] ,* from cte_config'

--, @attach_query_result_as_file = 1
--, @query_attachment_filename = 'configuration.csv'
, @query_result_header = 0
, @query_result_width = 32767
, @query_result_separator = ','
, @query_result_no_padding =1

-- since notification has been sent out, get rid of data as it is no longer valid
drop table msdb..sys_configurations

end
-- must create table to hold data for comparision for next run
IF object_id('msdb..sys_configurations') is null
begin
select * into msdb..sys_configurations from master.sys.configurations
end
end

That's a catalog view in all databases - it's querying the same thing (sys.configurations$) no matter where you run it so they would be the same.
Configuration changes are logged to the error log and are in the default trace as well.

Sue

GASQL.com - Focus on Database and Cloud

umm... here are other two methods

-- get it from default trace
DECLARE @trc_path VARCHAR(500)
SELECT @trc_path=CONVERT(VARCHAR(500),value) FROM fn_trace_getinfo(DEFAULT)
WHERE property=2

print @trc_path
SELECT TEXTData,HostName,ApplicationName,DatabaseName,LoginName,SPID,StartTime,EventSequence
FROM fn_trace_gettable(@trc_path,1) fn
WHERE TEXTData LIKE '%Configuration option%'
-- get it from errorlog
declare @sysconfigchanges TABLE
(
RowID int IDENTITY PRIMARY KEY,
EntryTime datetime,
source varchar(50),
LogEntry varchar(4000)
)

insert into @sysconfigchanges
exec sp_readerrorlog 0,1,'Configuration option'

select * from @sysconfigchanges where rowid=(select max(rowid) from @sysconfigchanges)

GASQL.com - Focus on Database and Cloud

Those are good. I don't know which one generates a bigger file or if the trace rolls over too many times to get what you need or the logs (but you can change that).
You can get more information from the trace than the log - it would have the login, not just the spid, host name, application name. You'd have a better chance of finding out who if that's important.

Sue

Go ahead and try creating a table named sys.configurations in msdb. I don't doubt that those are the queries goher2000 posted.

Sue

GASQL.com - Focus on Database and Cloud

Since trace has more information as to who,where,when I have created a job called 'DBA - Notify System Changes' with the code below, Also I am using Alert to detect system changes and trigger the job.

Job Code:
-- set servername in subject line
declare @sub nvarchar(255) = 'SQL Server Instance configuration has been changed ' + cast(@@servername as nvarchar)

-- pick one mail profile if there are multipal mail profiles
declare @pf nvarchar(255)
select top 1 @pf= sp.name from msdb..sysmail_profile sp
join msdb..sysmail_profileaccount spa on sp.profile_id=spa.profile_id
join msdb..sysmail_account sa on spa.account_id=sa.account_id

DECLARE @trc_path VARCHAR(500)
SELECT @trc_path=CONVERT(VARCHAR(500),value) FROM fn_trace_getinfo(DEFAULT)
WHERE property=2

--print @trc_path

declare @Qry varchar(8000) ='SELECT TEXTData,HostName,ApplicationName,DatabaseName,LoginName,SPID,StartTime,EventSequence FROM fn_trace_gettable('''
set @Qry=@Qry + @trc_path +''',1) fn WHERE TEXTData LIKE ''%Configuration option%'' and EventClass = 22'

--print @Qry
--exec(@Qry)

--declare @q=

EXEC msdb..sp_send_dbmail
@profile_name = @pf,
@recipients = 'sendIT2me@somewhere.com',
@subject = @sub ,
@body = 'System configuration has been changed ',
@execute_query_database = 'master',
@query = @Qry

--, @attach_query_result_as_file = 1
--, @query_attachment_filename = 'configuration.csv'
, @query_result_header = 0
, @query_result_width = 32767
, @query_result_separator = ','
, @query_result_no_padding =1


Alert Code :

USE [msdb]
GO

/****** Object: Alert [Alert - System Changes] Script Date: 2/9/2018 1:46:35 PM ******/
EXEC msdb.dbo.sp_add_alert @name=N'Alert - System Changes',
@message_id=0,
@severity=10,
@enabled=1,
@delay_between_responses=0,
@include_event_description_in=0,
@event_description_keyword=N'Configuration option',
@category_name=N'[Uncategorized]',
@job_name='DBA - Notify System Changes'
GO

That's actually very nice. There have been posts up here to find the changes as well as who made those changes. I'd keep playing around with it and think about submitting that for an article. There are requests for something like this often enough that I think it would be very beneficial for the community. Generally they seem to always want to know who which is the biggest benefit to using the trace file. The disadvantage that I got burned on with it once is if the instance gets hit with a ton of things that go into the trace, it can roll over before you capture it. So make sure you run the job often enough - I do now

Sue