IO.Pipes.NamedPipeServerStream And ClientSteam?
Mar 28, 2011IO.Pipes.NamedPipeServerStream and ClientSteam
View 3 RepliesIO.Pipes.NamedPipeServerStream and ClientSteam
View 3 RepliesI am trying to connect to SQL Server 2008 from my windows application using vb.net through named pipes.
I did some browsing and I found, to connect through named pipes we just have to mention "Initial Catalog =Test_DB; Data Source = np:Server_Name;integrated security=SSPI;".
But this doesn't connect to the server at all. Is this the right way to connect to sql sererver using named pipes?
I'm struggling with finding the best way to implement named pipes IPC with a robust timeout management. I don't mean timeout on establishing a connection but timeout on read/write streams.
All examples I find don't have a timeout implementation.
The client/server communication will only take place in the same network.I can use TCP, but then I have to configure separate IP ports for every server instance. I can however simply use named pipes so I don't have to think about port numbers and simply use the name of the server instance.There will not be very frequent and/or large data client/server communication. It's some sort of a ERP application that will only communicate once per 30 seconds on average.
View 2 Repliesi am trying to make a console app that basically makes a big X between pipes, but with a fixed line on the bottom where you can freely move a <#> with the arrow keys i did the giant x but i have no clue how to make the fixed line and i cannot find any information about it. i tried using the Console.write() but that only gives move a line that i cant use. Il paste the code i have to far.
[Code]...
I'm building a tool that consists of a Webservice that will run commandline tools at specific times. On average there will be running 15-20 CL tools at the same time. Every CL tool runs no longer than about 0,5-1 minute on average. The webservice needs to be able to check each CL's status every 2-3 seconds or so.
I've got some advice about how to do this; named pipes looks likes the best "technical" solution. However I'm wondering if communicating with simple very small text "status" files would be a better, less complicated and less error-risk, way. I prefer the solution that is the most resource friendly.
i have 2 computers - a Server and a Client pc which is running on local area network with MICROSOFT SQL SERVER 2008 R2 Developer kit at the main pc and Client computer will need to connect to SQL SERVER at main pc using connection string.Let me named server computer as 'MAGNA-PC' and the client pc as 'LAC-PC' and database name is 'db_referafriend' so the code for MAGNA-PC(server) connection string is:[code] i GOOGLE and YOUTUBE for almost 2 weeks before i post . I know that i need to configure the sql configuration manager and enable tcp/ip also add a new port at firewall to allow remote connection also add the sqlserver.exe and sqlbrowser in firewall and I have also chosen "Using both TCP/IP and named pipes" under Remote Connections in the SQL Server 2005 Surface Area Configuration. and all of this doesnt work!
View 10 Replies