While helping one of my DBA friend (who works in big company in LA) to upgrade SQL Server 2000 to SQL Server 2005 I just found one thing, which I have not paid attention before. SQL Server 2005 has no backup support for named pipes.
SQL Server 2000 supported named pipe backup device. SQL Server 2005 does not support named pipe backup device, however SQL Server 2005 supports disk and tape devices.
I receive following question many times, I have answered this question earlier on this blog. I will still answer it again.
What is my preferred method of backup?
We use SAN with RAID 10 configuration. Some industry experts suggested we are overprotecting our database backup. Well, Better safe than sorrow.
Published by Pinal Dave on SQLAuthority. More of my work at pinaldave.com.
Discover more from SQL Authority with Pinal Dave
Subscribe to get the latest posts sent to your email.
4 Comments. Leave new
Discontinued Database Engine Functionality in SQL Server 2005!!
Hi Pinal ,
Lots of other things you will found regarding disscontinued feaature and their replacemnet .
check this link https://docs.microsoft.com/en-us/sql/database-engine/discontinued-database-engine-functionality-in-sql-server-2016?view=sql-server-2017
Thanks & regards
Praveen barath
Yeah that was one of a features that had been discontinued in SQL 2005. https://docs.microsoft.com/en-us/sql/database-engine/discontinued-database-engine-functionality-in-sql-server-2016?view=sql-server-2017 That is by design as to comply with new security features introduced in SQL Server 2005. That, however, isn’t as bad as it might seem for the first sight. Named pipes were a demon that often caused problems. Recall the well-known case https://support.microsoft.com/en-us/help/818806 with backup/restore not being disabled after disabling the named pipes protocol. There’s a nice technet article about performing database back up in SQL server 2005 . It’s also possible to use VSS writer https://docs.microsoft.com/en-us/previous-versions/sql/sql-server-2005/administrator/cc966520(v=technet.10). Finally how about backing up DB files using something that can retain all file security like Scriptlogic’s Secure Copy? While it’s more of a file server backup and migration tool, I personally got attached to it so that I am now using it for any backup-related operations on my farm as it’s just simple in use and keeps me from worrying about SID security problems. For such a tiny tool I am impressed as it has everything I need. I like when configuring software doesn’t take much time AND and the same very moment the software doesn’t limit YOUR capabilities. This Scriptlogic’s tool is an exception to the rule. Currently it works in my environment with a 24×7 schedule and it’s reporting functionality helps a lot as it allows performing multiple backup operations without any need for intervention from my side. I also like there that it keeps all the security and timestamp information about the files it backs up. There are many positive things I can tell about Secure Copy but it’s far more better to refer to the site page for additional information if needed.
Personally I liked this whitepaper about SQL migration.
Keep working on your blog. I am new to database management and I am glad that I’ve found so much interesting stuff about SQL here. Thank you.
Peter,
Thank you, your comment contains information worth one wonderful article.
Regards,
Pinal Dave ( http://blog.sqlauthority.com/ )
Thanks for the article. It is helpful for me.