This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 69%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKS%3C/text%3E%3C/svg%3E)
How we can get database schema change result in query sql server? Is there any tool ? Suppose we do any change in schema. I want the result of that change in query.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi @Kanav Sharma
You can use the Schema Changes History report available in SQL Server Management Studio.
To access this report, right click the database then from the context menu choose Reports -> Standard Reports -> Schema Changes History.
You can refer to the previous thread.
Best regards,
Percy Tang
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(86.4, 54%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
Hi Percy, how can I extend the period of this log, it only shows the last few days for me. Is there a way to set a start date and retain the log for all schema changes after that date?
I believe that report reads from the default trace. Possibly, you could change how many rollover files and/or the size of the files, but I am not sure it is a good idea. That trace collects quite more information.
It's better to set up separate audit for DDL changes, for instance with SQL Server Audit.
If you have followup questions, please do not them here, but ask a new Question, describing your problem from start to end.
ok, thank you for your timely response! Much appreciated!