This kb is a good example.
How to use DBCC CLONEDATABASE to generate a schema and statistics only copy of a user database in SQL Server 2014 SP2 and SQL Server 2016 SP1
Erin Stellato gave DBCC CLONEDATABASE a look in this blog post.
Expanding the uses of DBCC CLONEDATABASE
So among other assorted fun, today I did this on SQL Server 2016 SP1.
The resulting message.
So... what is in that new LONNY_CLONE database?
There's plenty in there :-)
How big is the database?
Not bad. 448 mb of database files, 968 mb of transaction log.
On a database with this much DDL (often databases like this have well over 60,000 query optimizer stats - this one just happened to be light in that area), using the scripts from SSMS to create a clone database can be really painful. This is kinda fun :-)
This is going to be a great tool to enable investigating estimates and plan selection/shape.
Its a good thing that not every performance issue falls into those categories, or I'd have fewer edge cases to cherish. :-)