Sql Server Programming :: named pipes


	named pipes Hi I'm current investigation a chance to increase performance of backups to a logical drive over the network on the same LAN. As far as I can understand from BOL named pipes are relatively fast for one way communication on the same LAN. This was what caught my attention of using this to make my backup over the network. All backups go to a central machine on the network. Which makes the effort in terms of setting up security for named pipes worth while. What I want to know is if my theory is correct. - Using named pipes would speed up backup times to a network machine within the same LAN to such an extent that it would be worth doing named pipes instead of TCPIP. Anyone with experience using named pipes could comment. Thanks in advance. Mal Actually - TCP/IP is faster, however, I'm not sure that there will be 'that' much noticeable time difference in the backup as I'm pretty sure that the backup process would not use this setting. The setting is used for clients/servers to talk to each other whilst sending data back and forth. Technically all your SQL server would be doing when performing a backup is pumping out a flat file to a network location. Have a read up on this article anyway and best of luck. http://www.databasejournal.com/features/mssql/article.php/3334851 Immy "Mal .mullerjan@hotmail.com>" <<removethis> wrote in message news:2D54BB2C-4B48-4930-A075-4EE8F488A854@microsoft.com... - Hide quoted text - > Hi > I'm current investigation a chance to increase performance of backups to a > logical drive over the network on the same LAN. > As far as I can understand from BOL named pipes are relatively fast for > one > way communication on the same LAN. > This was what caught my attention of using this to make my backup over the > network. All backups go to a central machine on the network. Which makes > the > effort in terms of setting up security for named pipes worth while. > What I want to know is if my theory is correct. - Using named pipes would > speed up backup times to a network machine within the same LAN to such an > extent that it would be worth doing named pipes instead of TCPIP. > Anyone with experience using named pipes could comment. > Thanks in advance. > Mal Hey Immy I'm pretty sure backups can use this, when you add a device you can specific if u want to use named pipes, disk or tape device - Hide quoted text - "Immy" wrote: > Actually - TCP/IP is faster, however, I'm not sure that there will be 'that' > much noticeable time difference in the backup as I'm pretty sure that the > backup process would not use this setting. > The setting is used for clients/servers to talk to each other whilst sending > data back and forth. > Technically all your SQL server would be doing when performing a backup is > pumping out a flat file to a network location. > Have a read up on this article anyway and best of luck. > http://www.databasejournal.com/features/mssql/article.php/3334851 > Immy > "Mal .mullerjan@hotmail.com>" <<removethis> wrote in message > news:2D54BB2C-4B48-4930-A075-4EE8F488A854@microsoft.com... > > Hi > > I'm current investigation a chance to increase performance of backups to a > > logical drive over the network on the same LAN. > > As far as I can understand from BOL named pipes are relatively fast for > > one > > way communication on the same LAN. > > This was what caught my attention of using this to make my backup over the > > network. All backups go to a central machine on the network. Which makes > > the > > effort in terms of setting up security for named pipes worth while. > > What I want to know is if my theory is correct. - Using named pipes would > > speed up backup times to a network machine within the same LAN to such an > > extent that it would be worth doing named pipes instead of TCPIP. > > Anyone with experience using named pipes could comment. > > Thanks in advance. > > Mal - Hide quoted text - "Immy" wrote: > Actually - TCP/IP is faster, however, I'm not sure that there will be 'that' > much noticeable time difference in the backup as I'm pretty sure that the > backup process would not use this setting. > The setting is used for clients/servers to talk to each other whilst sending > data back and forth. > Technically all your SQL server would be doing when performing a backup is > pumping out a flat file to a network location. > Have a read up on this article anyway and best of luck. > http://www.databasejournal.com/features/mssql/article.php/3334851 > Immy > "Mal .mullerjan@hotmail.com>" <<removethis> wrote in message > news:2D54BB2C-4B48-4930-A075-4EE8F488A854@microsoft.com... > > Hi > > I'm current investigation a chance to increase performance of backups to a > > logical drive over the network on the same LAN. > > As far as I can understand from BOL named pipes are relatively fast for > > one > > way communication on the same LAN. > > This was what caught my attention of using this to make my backup over the > > network. All backups go to a central machine on the network. Which makes > > the > > effort in terms of setting up security for named pipes worth while. > > What I want to know is if my theory is correct. - Using named pipes would > > speed up backup times to a network machine within the same LAN to such an > > extent that it would be worth doing named pipes instead of TCPIP. > > Anyone with experience using named pipes could comment. > > Thanks in advance. > > Mal In SQL2005 - yes, correct, but it will use the default network protocol (i.e. as you set it in the config). I would suggest reading the implications of using the different types and then test to see if you actually see a performance gain on the speed. "Mal .mullerjan@hotmail.com>" <<removethis> wrote in message news:014E2666-3A4F-4F35-9FDB-FD9436890299@microsoft.com... - Hide quoted text - > "Immy" wrote: >> Actually - TCP/IP is faster, however, I'm not sure that there will be >> 'that' >> much noticeable time difference in the backup as I'm pretty sure that the >> backup process would not use this setting. >> The setting is used for clients/servers to talk to each other whilst >> sending >> data back and forth. >> Technically all your SQL server would be doing when performing a backup >> is >> pumping out a flat file to a network location. >> Have a read up on this article anyway and best of luck. >> http://www.databasejournal.com/features/mssql/article.php/3334851 >> Immy >> "Mal .mullerjan@hotmail.com>" <<removethis> wrote in message >> news:2D54BB2C-4B48-4930-A075-4EE8F488A854@microsoft.com... >> > Hi >> > I'm current investigation a chance to increase performance of backups >> > to a >> > logical drive over the network on the same LAN. >> > As far as I can understand from BOL named pipes are relatively fast for >> > one >> > way communication on the same LAN. >> > This was what caught my attention of using this to make my backup over >> > the >> > network. All backups go to a central machine on the network. Which >> > makes >> > the >> > effort in terms of setting up security for named pipes worth while. >> > What I want to know is if my theory is correct. - Using named pipes >> > would >> > speed up backup times to a network machine within the same LAN to such >> > an >> > extent that it would be worth doing named pipes instead of TCPIP. >> > Anyone with experience using named pipes could comment. >> > Thanks in advance. >> > Mal Are you referring to the backup device of the type PIPE? If so, I think that is only meant to be used by 3:rd party backup vendors, and the replacement has been around since 7.0, and PIPE is no longer available in 2005. -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi "Mal .mullerjan@hotmail.com>" <<removethis> wrote in message news:2D54BB2C-4B48-4930-A075-4EE8F488A854@microsoft.com... - Hide quoted text - > Hi > I'm current investigation a chance to increase performance of backups to a > logical drive over the network on the same LAN. > As far as I can understand from BOL named pipes are relatively fast for one > way communication on the same LAN. > This was what caught my attention of using this to make my backup over the > network. All backups go to a central machine on the network. Which makes the > effort in terms of setting up security for named pipes worth while. > What I want to know is if my theory is correct. - Using named pipes would > speed up backup times to a network machine within the same LAN to such an > extent that it would be worth doing named pipes instead of TCPIP. > Anyone with experience using named pipes could comment. > Thanks in advance. > Mal Hi Immy I'm talking about 2000, I've attached a bit of BOL [@devtype =] 'device_type', Is the type of backup device. device_type is varchar(20), with no default, and can be one of these values. Value Description disk Hard disk file as a backup device. pipe Named pipe. tape Any tape devices supported by Microsoft Windows NT. If device is tape, noskip is the default. - Hide quoted text - "Immy" wrote: > In SQL2005 - yes, correct, but it will use the default network protocol > (i.e. as you set it in the config). > I would suggest reading the implications of using the different types and > then test to see if you actually see a performance gain on the speed. > "Mal .mullerjan@hotmail.com>" <<removethis> wrote in message > news:014E2666-3A4F-4F35-9FDB-FD9436890299@microsoft.com... > > "Immy" wrote: > >> Actually - TCP/IP is faster, however, I'm not sure that there will be > >> 'that' > >> much noticeable time difference in the backup as I'm pretty sure that the > >> backup process would not use this setting. > >> The setting is used for clients/servers to talk to each other whilst > >> sending > >> data back and forth. > >> Technically all your SQL server would be doing when performing a backup > >> is > >> pumping out a flat file to a network location. > >> Have a read up on this article anyway and best of luck. > >> http://www.databasejournal.com/features/mssql/article.php/3334851 > >> Immy > >> "Mal .mullerjan@hotmail.com>" <<removethis> wrote in message > >> news:2D54BB2C-4B48-4930-A075-4EE8F488A854@microsoft.com... > >> > Hi > >> > I'm current investigation a chance to increase performance of backups > >> > to a > >> > logical drive over the network on the same LAN. > >> > As far as I can understand from BOL named pipes are relatively fast for > >> > one > >> > way communication on the same LAN. > >> > This was what caught my attention of using this to make my backup over > >> > the > >> > network. All backups go to a central machine on the network. Which > >> > makes > >> > the > >> > effort in terms of setting up security for named pipes worth while. > >> > What I want to know is if my theory is correct. - Using named pipes > >> > would > >> > speed up backup times to a network machine within the same LAN to such > >> > an > >> > extent that it would be worth doing named pipes instead of TCPIP. > >> > Anyone with experience using named pipes could comment. > >> > Thanks in advance. > >> > Mal Mal, Now I see what you are referring to from BOL. This is a feature used for 3rd parties. We actually used this feature in our organization with DELL integration (before we replaced our systems). I believe you cannot use this manually in TSQL? Immy "Mal .mullerjan@hotmail.com>" <<removethis> wrote in message news:E3BE15C0-F2B8-4526-8DED-2296322EE48E@microsoft.com... - Hide quoted text - > Hi Immy > I'm talking about 2000, I've attached a bit of BOL > [@devtype =] 'device_type', > Is the type of backup device. device_type is varchar(20), with no default, > and can be one of these values. > Value Description > disk Hard disk file as a backup device. > pipe Named pipe. > tape Any tape devices supported by Microsoft Windows NT. If device is > tape, > noskip is the default. > "Immy" wrote: >> In SQL2005 - yes, correct, but it will use the default network protocol >> (i.e. as you set it in the config). >> I would suggest reading the implications of using the different types and >> then test to see if you actually see a performance gain on the speed. >> "Mal .mullerjan@hotmail.com>" <<removethis> wrote in message >> news:014E2666-3A4F-4F35-9FDB-FD9436890299@microsoft.com... >> > "Immy" wrote: >> >> Actually - TCP/IP is faster, however, I'm not sure that there will be >> >> 'that' >> >> much noticeable time difference in the backup as I'm pretty sure that >> >> the >> >> backup process would not use this setting. >> >> The setting is used for clients/servers to talk to each other whilst >> >> sending >> >> data back and forth. >> >> Technically all your SQL server would be doing when performing a >> >> backup >> >> is >> >> pumping out a flat file to a network location. >> >> Have a read up on this article anyway and best of luck. >> >> http://www.databasejournal.com/features/mssql/article.php/3334851 >> >> Immy >> >> "Mal .mullerjan@hotmail.com>" <<removethis> wrote in message >> >> news:2D54BB2C-4B48-4930-A075-4EE8F488A854@microsoft.com... >> >> > Hi >> >> > I'm current investigation a chance to increase performance of >> >> > backups >> >> > to a >> >> > logical drive over the network on the same LAN. >> >> > As far as I can understand from BOL named pipes are relatively fast >> >> > for >> >> > one >> >> > way communication on the same LAN. >> >> > This was what caught my attention of using this to make my backup >> >> > over >> >> > the >> >> > network. All backups go to a central machine on the network. Which >> >> > makes >> >> > the >> >> > effort in terms of setting up security for named pipes worth while. >> >> > What I want to know is if my theory is correct. - Using named pipes >> >> > would >> >> > speed up backup times to a network machine within the same LAN to >> >> > such >> >> > an >> >> > extent that it would be worth doing named pipes instead of TCPIP. >> >> > Anyone with experience using named pipes could comment. >> >> > Thanks in advance. >> >> > Mal