FREMONT, Calif., Jan. 4, 2017 /PRNewswire/ — Denny Cherry & Associates Consulting announced today that it has been named to CIOReview’s 20 Most Promising Azure Solution Providers of 2016.
“It’s a great honor to select Denny Cherry & Associates Consulting as one of the 20 Most Promising Azure Solution Providers 2016,” said Jeevan George, Managing Editor of CIOReview.
Read Now >
One of the recent feature introductions to SQL Server is dbcc clonedatabase, a feature that lets you create a “data-less” clone of you database. All of the statistics and objects come into your cloned database, however none of the data does. This is perfect for development or performance tuning exercises, where you want all the metadata, but do not want the security risk of dealing with production data.
Recently I had the opportunity to use clonedatabase on a very large database. I was concerned about the size of the data files and how this would impact space on my volumes. Books Online is fairly clear, but I wanted to see for myself.
Note All files in the target database will inherit the size and growth settings from the model database. File name convention: The file names for the destination database will follow the source_file_name _underscore_random number convention. If the generated file name already exists in the destination folder, DBCC CLONEDATABASE will fail
So my thought in reading that, is that the same number of data files will be created in the clone, just with the settings in model. Let’s test that out.
The first thing I did was create a new database, and then add a few data files to it. I made them 20 MB, which is a different size than model—just for testing purposes.
Next, I ran the clone database command.
Then connect to the clone and look at the data files
I can see that all of the files were created, in the same location as the files on the source database, except with the size settings of model. While this shouldn’t be a big deal for most, if you do like I recommend and make model a reasonable size for your environment, and you happen to be tight on drive space, you could fill up a volume. So just be aware when using clonedatabase particularly with databases that have a lot of data files in them.
At SQL Bits this year I’ll be presenting my all day session Database Administration for the Non-DBA. This all day training day is a great session for those who work in shops where they have to function as the DBA, but their job isn’t to be the DBA (or someone who is brand new to being a DBA). We’re going to talk about all the great things that you have to worry about as the DBA including backups, restores, corruption, performance tuning, indexing, virtualization, High Availability, Disaster Recovery, and much more.
If you are an accidental DBA, or are just getting into the DBA field then this is the training day event that you want to sign up for. So stop waiting, and get registered (you select the training day during the normal registration process for SQL Bits).
The post Database Administration for the Non Database Administrator at SQL Bits appeared first on SQL Server with Mr. Denny.
In late 2016, Ken Hopkins, COO of AER Technologies, the largest automotive electronics warranty service center and distributor on the West Coast had a major problem. The company’s entire IT environment was failing, due to:
- Aging hardware (circa 2004)
- Out of support hardware
- Out of support software including SQL 2005
- Security issues
Ken explains, “If you go back to when the economy collapsed and 2 of the 3 largest automotive manufactures went bankrupt, we had minimal IT budgets available for hardware and software upgrades. Over the last couple of years, we started having critical failures in our server room that led to outages lasting from a few hours to more than two days. Without a high-availability solution in place, coupled with antiquated hardware and software, it put AER’s entire business in jeopardy.”
Read Now >