October 12, 2011 at 2:56 am
I maintain monthly snapsnots of our live database on a SQL server on my own PC which is currently running SQL Express. This morning when trying to restore an October snapshot I ran into an error because the database was over 10gb in size.
I understand this is a limitation of the Express version, it seems the Developer version would solve this restriction?
All I'm using these snapshots for is the odd query to see how the data has changed month on month - probably used about 4 times a year if that, this isn't something used by anyone but me. It sounds like developer edition would fit the bill here?
Your thoughts and advice are most welcome 🙂
Thanks.
October 12, 2011 at 3:05 am
Sounds like a bit of grey area.
It could probably be argued either way as to whether this is a production use or not. Obviously, one of those invalidates the license use of developer edition.
The usual term I see is if you can and do query the production data you need a production license so developer edition is not suitable.
October 12, 2011 at 3:05 am
October 12, 2011 at 3:34 am
Sound ok.
You're not using the instance in a production environment, so it should be ok.
-- Gianluca Sartori
October 12, 2011 at 6:55 am
I disagree, this shoulds like you would be in breach of the licensing terms. I would try to seek an answer from Microsoft just in case.
Thanks
Chris
October 12, 2011 at 7:54 am
What are those snapshots used for?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 12, 2011 at 8:36 am
Typically three uses:
1. To see how the data has changed - i.e. I might look and see table A has X rows on our live DB and Y rows on snapshot 1 etc.
2. To test out update/insert statements before running them on a live environment
3. To look back at data as a sort of cobbled together audit process, we have others but on occasion this is useful.
So, nothing from this is ever presented to clients, or accessible to anyone but me really.
October 12, 2011 at 9:29 am
It sounds to me like since these are not being used in any disaster recovery or production use, you are fine. Fundamentally, you are using these snapshots for development purposes; i.e. Development Edition. I see no need to contact Microsoft. This becomes a problem when these snapshots are used for production maintenance or disaster recovery. However, restoring them to a development edition that is on a local machine is not an issue.
Thanks,
Jared
Jared
CE - Microsoft
October 12, 2011 at 9:31 am
They'd never be used for disaster recovery, we have more up to date daily snapshots stored both on the live SQL server, on a local server here as .bak files and in the cloud with shed loads of retention 🙂
October 12, 2011 at 9:46 am
Using them as a "cobbled together" audit process would surely invalidate the license terms?
Thansk
Chris
October 12, 2011 at 9:55 am
Perhaps that should be clarified, we have an 'official' audit process where by we could track down the changes made to some specific entities and see a massive list of these etc, however, sometimes it's quicker to just have a look in a couple of snapshots to see what would have happened before digging into an audit system.
Besides, I don't think I've even done that this year, if that was something which was problematic I could easily just not bother using them for that purpose.
October 12, 2011 at 9:59 am
MysteryJimbo (10/12/2011)
Sounds like a bit of grey area.
I suggest you seek clarification with Microsoft.
October 12, 2011 at 10:09 am
Look... The reality here is that this is small potatoes compared to what the BSA or Microsoft is looking for. IF and I mean a big IF Microsoft suspected a license violation here, the worst they would do is ask you to stop. They are worried "mainly" about number and type of licenses for boxes vs processor vs CAL, etc. Sure, if you want to be really safe you can call Microsoft or your vendor, but the reality is some of these things are completely subjective to who you talk to, even at Microsoft. This is one of those areas. The only person in this case who would make a determination would be a judge in court, and since it is open to complete interpretaion it is not something Microsoft would bother with. Especially for 1 little license...
Jared
Jared
CE - Microsoft
October 12, 2011 at 10:13 am
To be honest in the first instance I was making sure that Developer edition would actually do what I wanted, that was the aim of the post really!
It sounds like it would, we have plenty of fully licensed installs of SQL on various live environments 🙂
October 12, 2011 at 10:14 am
Rob-350472 (10/12/2011)
To be honest in the first instance I was making sure that Developer edition would actually do what I wanted, that was the aim of the post really!It sounds like it would, we have plenty of fully licensed installs of SQL on various live environments 🙂
lol Developer is same as Enterprise. 🙂
Thanks,
Jared
Jared
CE - Microsoft
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply