Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 Enterprise to Standard

Author  Topic 

tbrothers
Yak Posting Veteran

83 Posts

Posted - 2012-01-10 : 16:16:17
Hello,

We are running SQL 2005 Enterprise because we needed the increased memory. We no longer have that need. Can databases be moved from 2005 Enterprise to 2005 Standard?

How about from 2005 Enterprise to 2008 Standard?

Regards,
Terry

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2012-01-10 : 16:23:08
Yes and yes. Those are valid restore paths.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 2012-01-10 : 16:33:05
Are you going to sell the license?

Why would you go to standard from Enterprise...I mean I can understand going to 2008 R2 Standard..but if you have 2k5 Enterprise...why bother?




Brett

8-)

Hint: Want your questions answered fast? Follow the direction in this link
http://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspx


Want to help yourself?

http://msdn.microsoft.com/en-us/library/ms130214.aspx

http://weblogs.sqlteam.com/brettk/

http://brettkaiser.blogspot.com/


Go to Top of Page

tbrothers
Yak Posting Veteran

83 Posts

Posted - 2012-01-10 : 16:45:57
Thanks Tara.

Brett - I'm actually setting up a new log shipping server. The production server is Ent and if I can I'll install Std on the backup server.

Later this year we'll be upgrading to SQL 2008.

It all has to do with our MS enterprise agreement. Standard will save us money every true-up ... every year.

Thanks,
Terry
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2012-01-10 : 16:48:11
You don't need to license your DR system, unless you are using it for reporting or the likes. And if you are using it for reporting, well I'd have to wonder about that decision.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

tbrothers
Yak Posting Veteran

83 Posts

Posted - 2012-01-10 : 16:56:05
Yes ... we do use it for reporting. I sense a question or comment coming

Terry
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2012-01-10 : 16:59:51
It just isn't a good reporting solution. Users have to get disconnected every time a restore happens.

Why not use transactional replication instead?

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

tbrothers
Yak Posting Veteran

83 Posts

Posted - 2012-01-10 : 17:09:55
Well this may seem lame ... but ... When log shipping was originally setup I did not know how to setup replication. In fact, I still don't.

But - When we upgrade to SQL 2008 I intend to learn and switch to replication. That's my plan anyway.

That being said - log restores take 15 seconds and get restored every 15 minutes and I have never once had a user tell me they had an issue. If I had any complaints then I would have addressed it long ago.

Terry
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2012-01-10 : 17:14:21
That's 15 seconds of downtime every 15 minutes, longer when the tlog backups are bigger due to index rebuilds. While they may not have complained, users are bound to encounter their report not completing and needing to do it again.

Glad to hear it's your plan to switch to replication. The only hard part about replication is troubleshooting it when things go wrong, but that should be very rare. Log shipping has problems too that aren't easily figured out, so it's six of one half dozen or the other.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page
   

- Advertisement -