How do a get a listing of all available SQL Servers on a network.

I want to create a web app that will allow a user to select from a drop down or lookup all available SQL Server databases.

Thanks in advance,
Jeremyi answered my own question... hope this helps some one

To restate my problem.
I need an app that will list all of the available SQL Servers on a network. There are many ways to do this ... this is one. I would like to see better ways if anyone has time.

1. Download the SQLUtils.dll from (watch for line wrap)
http://codeproject.com/useritems/listsqlservers.asp?print=true

2. Register the SQLUtils.dll using regsvr32.exe
> regsvr32 c:/inetpub/wwwroot/lib/sqlutils.dll

3. Build your web form

// C#

using SQLUtils;

protected System.Web.UI.WebControls.TextBox TextBox1;
protected System.Web.UI.WebControls.Button Button1;
protected System.Web.UI.WebControls.ListBox ListBox1;

private void Button1_Click(object sender, System.EventArgs e)
{
SQLUtils.ListServers oSqlUtils = new SQLUtils.ListServers();
// String svr = new String();
oSqlUtils.Domain = TextBox1.Text;
oSqlUtils.GetSQLServers();
foreach( String svr in oSqlUtils.Servers )
{
ListBox1.Items.Add(svr);
} // end of foreach loop
} // end of Button1_Click()

4. You will need to add a reference in your project to the .dll file. Right click on the project and select "Add Reference". Browse to the location and select.

I also found these... (watch for line wrap)
http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=14327

How could I do backups for my packages?

Hi all of you,

Formerly when we ran dts we had DtsBackup2000. So we could to arrange lots of backups around the network in a centralized way. But now how to run backups in groups no individually way?

We've got five sql25k along with its dtsx packages and we'd like have all of them in the same place.

Any tool or idea?

Thanks in advance,

What storage method do you use?

|||

Hi Darren,

Thanks for your answer. We've LEGATO system for our db. in regard packages we save them as .dtb and .dts files.

TIA

|||

I meant how do you store your SSIS packages, as that would impact what I suggest for a backup of them! I know about DTS, you told me you used DTSBackup.|||

Hi again,

Individually, people save them in its own local machines but, of course, that's not very safe.. I mean, VSS is not used at all.

The SSIS packages are stored on the production server and on the development server.

Up to the date the only way for me is do backup one after one.

Thanks Darren,

|||

All of them in MSDB.

I don't know if this answer finally clarifies this post.

|||

If the packages are deployed to MSDB as opposed to File System, backing up the SQL database on Production & Dev will effectively back up your packages.

Obvioulsy the "undeployed" latest or working versions on individual machines are at the mercy of the users! At least suggest they are saved on a network drive that is backed up if they cannot or will not use VSS. Local machine saves are madness

|||

Hi Will,

Thanks for your answer. But our main idea is to retrieve as soon as possible a concrete dtsx without have to do a restore when there's an issue or problem.

|||

If that is the case, go overboard... save all packages to a shared drive on the network (make sure that your sql agent user / proxy has access). Back that up nightly and run all imports into your MSDB from this drive. Also, make sure that you are doing full backups of the sql server in test and prod.

//mycomputername/SSISPackages/PackageName(s)

//mycomputername/SSISPackages/ConfigFiles

backup all files in SSISPackages...

|||

enric, if you need to rollback to a working version of a SSIS package then I woudl look to re-deploy that working package from your release management store or source control system.

DTSBackup made sense in DTS because it was very common to change packages on the server, just because the tools worked that way, but with SSIS, you should always have an offline copy with changes made by the developer, and that "should" be under some control, source control, release management etc.

How could I do backups for my packages?

Hi all of you,

Formerly when we ran dts we had DtsBackup2000. So we could to arrange lots of backups around the network in a centralized way. But now how to run backups in groups no individually way?

We've got five sql25k along with its dtsx packages and we'd like have all of them in the same place.

Any tool or idea?

Thanks in advance,

What storage method do you use?

|||

Hi Darren,

Thanks for your answer. We've LEGATO system for our db. in regard packages we save them as .dtb and .dts files.

TIA

|||I meant how do you store your SSIS packages, as that would impact what I suggest for a backup of them! I know about DTS, you told me you used DTSBackup.|||

Hi again,

Individually, people save them in its own local machines but, of course, that's not very safe.. I mean, VSS is not used at all.

The SSIS packages are stored on the production server and on the development server.

Up to the date the only way for me is do backup one after one.

Thanks Darren,

|||

All of them in MSDB.

I don't know if this answer finally clarifies this post.

|||

If the packages are deployed to MSDB as opposed to File System, backing up the SQL database on Production & Dev will effectively back up your packages.

Obvioulsy the "undeployed" latest or working versions on individual machines are at the mercy of the users! At least suggest they are saved on a network drive that is backed up if they cannot or will not use VSS. Local machine saves are madness

|||

Hi Will,

Thanks for your answer. But our main idea is to retrieve as soon as possible a concrete dtsx without have to do a restore when there's an issue or problem.

|||

If that is the case, go overboard... save all packages to a shared drive on the network (make sure that your sql agent user / proxy has access). Back that up nightly and run all imports into your MSDB from this drive. Also, make sure that you are doing full backups of the sql server in test and prod.

//mycomputername/SSISPackages/PackageName(s)

//mycomputername/SSISPackages/ConfigFiles

backup all files in SSISPackages...

|||

enric, if you need to rollback to a working version of a SSIS package then I woudl look to re-deploy that working package from your release management store or source control system.

DTSBackup made sense in DTS because it was very common to change packages on the server, just because the tools worked that way, but with SSIS, you should always have an offline copy with changes made by the developer, and that "should" be under some control, source control, release management etc.

How could I do backups for my packages?

Hi all of you,

Formerly when we ran dts we had DtsBackup2000. So we could to arrange lots of backups around the network in a centralized way. But now how to run backups in groups no individually way?

We've got five sql25k along with its dtsx packages and we'd like have all of them in the same place.

Any tool or idea?

Thanks in advance,

What storage method do you use?

|||

Hi Darren,

Thanks for your answer. We've LEGATO system for our db. in regard packages we save them as .dtb and .dts files.

TIA

|||I meant how do you store your SSIS packages, as that would impact what I suggest for a backup of them! I know about DTS, you told me you used DTSBackup.|||

Hi again,

Individually, people save them in its own local machines but, of course, that's not very safe.. I mean, VSS is not used at all.

The SSIS packages are stored on the production server and on the development server.

Up to the date the only way for me is do backup one after one.

Thanks Darren,

|||

All of them in MSDB.

I don't know if this answer finally clarifies this post.

|||

If the packages are deployed to MSDB as opposed to File System, backing up the SQL database on Production & Dev will effectively back up your packages.

Obvioulsy the "undeployed" latest or working versions on individual machines are at the mercy of the users! At least suggest they are saved on a network drive that is backed up if they cannot or will not use VSS. Local machine saves are madness

|||

Hi Will,

Thanks for your answer. But our main idea is to retrieve as soon as possible a concrete dtsx without have to do a restore when there's an issue or problem.

|||

If that is the case, go overboard... save all packages to a shared drive on the network (make sure that your sql agent user / proxy has access). Back that up nightly and run all imports into your MSDB from this drive. Also, make sure that you are doing full backups of the sql server in test and prod.

//mycomputername/SSISPackages/PackageName(s)

//mycomputername/SSISPackages/ConfigFiles

backup all files in SSISPackages...

|||

enric, if you need to rollback to a working version of a SSIS package then I woudl look to re-deploy that working package from your release management store or source control system.

DTSBackup made sense in DTS because it was very common to change packages on the server, just because the tools worked that way, but with SSIS, you should always have an offline copy with changes made by the developer, and that "should" be under some control, source control, release management etc.

How choose net lib on client side?

I have SQL Server 7 and it has in the network config utility TCP, Named
Pipes and Multiprotocol. I want to use TCP on my clients, the only problem
is I don't know how to set them up to use this as opposed to named pipes. I
do not want to authenticate at the OS level so I'm trying to get it to use
plain old TCP. By default, all of them appear to be using named pipes. Is
there some way I can confirm or change this theory?
Thanks,
Ben
You can manage this using the Client Network Utillity on the client machine.
From the server, you can tell what netlib a client is connecting on by
looking at the net_library column in master..sysprocesses.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Becker" <ben@.benbecker.net> wrote in message
news:OAtKhaKdEHA.3988@.tk2msftngp13.phx.gbl...
> I have SQL Server 7 and it has in the network config utility TCP, Named
> Pipes and Multiprotocol. I want to use TCP on my clients, the only
problem
> is I don't know how to set them up to use this as opposed to named pipes.
I
> do not want to authenticate at the OS level so I'm trying to get it to use
> plain old TCP. By default, all of them appear to be using named pipes.
Is
> there some way I can confirm or change this theory?
> Thanks,
> Ben
>
|||Interesting, so if I don't have the sql client loaded on a machine, what net
library will it use by default? E.g. I have a fresh install of win 2k with
an app that connects to SQL Server, I haven't loaded a client on it but the
app works just fine and it is using named pipes. I want it to use tcp/ip,
do i have to load the client to specify something different?
Thanks,
Ben
"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:eD3OdfKdEHA.3864@.TK2MSFTNGP10.phx.gbl...
> You can manage this using the Client Network Utillity on the client
machine.[vbcol=seagreen]
> From the server, you can tell what netlib a client is connecting on by
> looking at the net_library column in master..sysprocesses.
> --
> Brian Moran
> Principal Mentor
> Solid Quality Learning
> SQL Server MVP
> http://www.solidqualitylearning.com
>
> "Becker" <ben@.benbecker.net> wrote in message
> news:OAtKhaKdEHA.3988@.tk2msftngp13.phx.gbl...
> problem
pipes.[vbcol=seagreen]
> I
use
> Is
>

How choose net lib on client side?

I have SQL Server 7 and it has in the network config utility TCP, Named
Pipes and Multiprotocol. I want to use TCP on my clients, the only problem
is I don't know how to set them up to use this as opposed to named pipes. I
do not want to authenticate at the OS level so I'm trying to get it to use
plain old TCP. By default, all of them appear to be using named pipes. Is
there some way I can confirm or change this theory?
Thanks,
BenYou can manage this using the Client Network Utillity on the client machine.
From the server, you can tell what netlib a client is connecting on by
looking at the net_library column in master..sysprocesses.
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Becker" <ben@.benbecker.net> wrote in message
news:OAtKhaKdEHA.3988@.tk2msftngp13.phx.gbl...
> I have SQL Server 7 and it has in the network config utility TCP, Named
> Pipes and Multiprotocol. I want to use TCP on my clients, the only
problem
> is I don't know how to set them up to use this as opposed to named pipes.
I
> do not want to authenticate at the OS level so I'm trying to get it to use
> plain old TCP. By default, all of them appear to be using named pipes.
Is
> there some way I can confirm or change this theory?
> Thanks,
> Ben
>|||Interesting, so if I don't have the sql client loaded on a machine, what net
library will it use by default? E.g. I have a fresh install of win 2k with
an app that connects to SQL Server, I haven't loaded a client on it but the
app works just fine and it is using named pipes. I want it to use tcp/ip,
do i have to load the client to specify something different?
Thanks,
Ben
"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:eD3OdfKdEHA.3864@.TK2MSFTNGP10.phx.gbl...
> You can manage this using the Client Network Utillity on the client
machine.
> From the server, you can tell what netlib a client is connecting on by
> looking at the net_library column in master..sysprocesses.
> --
> Brian Moran
> Principal Mentor
> Solid Quality Learning
> SQL Server MVP
> http://www.solidqualitylearning.com
>
> "Becker" <ben@.benbecker.net> wrote in message
> news:OAtKhaKdEHA.3988@.tk2msftngp13.phx.gbl...
> > I have SQL Server 7 and it has in the network config utility TCP, Named
> > Pipes and Multiprotocol. I want to use TCP on my clients, the only
> problem
> > is I don't know how to set them up to use this as opposed to named
pipes.
> I
> > do not want to authenticate at the OS level so I'm trying to get it to
use
> > plain old TCP. By default, all of them appear to be using named pipes.
> Is
> > there some way I can confirm or change this theory?
> >
> > Thanks,
> > Ben
> >
> >
>

How choose net lib on client side?

I have SQL Server 7 and it has in the network config utility TCP, Named
Pipes and Multiprotocol. I want to use TCP on my clients, the only problem
is I don't know how to set them up to use this as opposed to named pipes. I
do not want to authenticate at the OS level so I'm trying to get it to use
plain old TCP. By default, all of them appear to be using named pipes. Is
there some way I can confirm or change this theory?
Thanks,
BenYou can manage this using the Client Network Utillity on the client machine.
From the server, you can tell what netlib a client is connecting on by
looking at the net_library column in master..sysprocesses.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Becker" <ben@.benbecker.net> wrote in message
news:OAtKhaKdEHA.3988@.tk2msftngp13.phx.gbl...
> I have SQL Server 7 and it has in the network config utility TCP, Named
> Pipes and Multiprotocol. I want to use TCP on my clients, the only
problem
> is I don't know how to set them up to use this as opposed to named pipes.
I
> do not want to authenticate at the OS level so I'm trying to get it to use
> plain old TCP. By default, all of them appear to be using named pipes.
Is
> there some way I can confirm or change this theory?
> Thanks,
> Ben
>|||Interesting, so if I don't have the sql client loaded on a machine, what net
library will it use by default? E.g. I have a fresh install of win 2k with
an app that connects to SQL Server, I haven't loaded a client on it but the
app works just fine and it is using named pipes. I want it to use tcp/ip,
do i have to load the client to specify something different?
Thanks,
Ben
"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:eD3OdfKdEHA.3864@.TK2MSFTNGP10.phx.gbl...
> You can manage this using the Client Network Utillity on the client
machine.
> From the server, you can tell what netlib a client is connecting on by
> looking at the net_library column in master..sysprocesses.
> --
> Brian Moran
> Principal Mentor
> Solid Quality Learning
> SQL Server MVP
> http://www.solidqualitylearning.com
>
> "Becker" <ben@.benbecker.net> wrote in message
> news:OAtKhaKdEHA.3988@.tk2msftngp13.phx.gbl...
> problem
pipes.[vbcol=seagreen]
> I
use[vbcol=seagreen]
> Is
>

How can one Connect (remotely) to SQLExpress which is installed on "Windows XP Home"

Hi all,

I have to deal with a private network of laptops which are all equiped with preinstalled "Windows XP home"

I've installed SQLExpress on one of these, but I cannot connect on it from the rest of the laptops. (I've successfuly done this with "Windows XP profesional" though, and local connections work fine as well).

I've already setup the SQLExpress to accept conections throuigh TCP/IP but I can not think of something else. (Security comes to mind, but I do not know how to resolve it on "Windows XP Home").

Thank you

Ioannis

Allow port 1433 and 1434 for TCP to come though as this should be blocked by the firewall by default. Try this first by disabling the firewall for a moment to see if this is the case.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||

Hi Ioannis,

Did opening the firewall solve this issue for you?

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

|||

Hi,

The firewall was already wide open!

What solved my problem was starting the "Browser" service.

Is this service supposed to be "down" by default?

thank you both for your kind responses

Ioannis

|||That is a question of settings in the setup during the installation, you can check the service to autimatically startup, if you don′t it will put it on Manual.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Yes, this is by design.

SQL Express installs with the minimum external exposure possible. We also have remote connections disabled by default.

Mike

How can one Connect (remotely) to SQLExpress which is installed on "Windows XP Home&quo

Hi all,

I have to deal with a private network of laptops which are all equiped with preinstalled "Windows XP home"

I've installed SQLExpress on one of these, but I cannot connect on it from the rest of the laptops. (I've successfuly done this with "Windows XP profesional" though, and local connections work fine as well).

I've already setup the SQLExpress to accept conections throuigh TCP/IP but I can not think of something else. (Security comes to mind, but I do not know how to resolve it on "Windows XP Home").

Thank you

Ioannis

Allow port 1433 and 1434 for TCP to come though as this should be blocked by the firewall by default. Try this first by disabling the firewall for a moment to see if this is the case.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||

Hi Ioannis,

Did opening the firewall solve this issue for you?

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

|||

Hi,

The firewall was already wide open!

What solved my problem was starting the "Browser" service.

Is this service supposed to be "down" by default?

thank you both for your kind responses

Ioannis

|||That is a question of settings in the setup during the installation, you can check the service to autimatically startup, if you don′t it will put it on Manual.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Yes, this is by design.

SQL Express installs with the minimum external exposure possible. We also have remote connections disabled by default.

Mike