Showing posts with label mssql. Show all posts
Showing posts with label mssql. Show all posts

Tuesday, March 27, 2012

Backing up MSSQL Server on Windows 2003 Small Business Server

Hi guys, could you please provide me with the best solution to backup my MSSQL Server running on Windows 2003 Small Business Server.

I am currently using software that runs on four client computers and saves data in the Win2k3 SBS.

Where should I start and what is the safest way to back it up.

This is on a Dell Poweredge 1400 Server and will be moved to the new Dell Poweredge 2800 Server once it arrives - operating will be the Same Win2k3 SBS but the edition will be R2 both systems are 32bit

Thanks for your help in advance

Cyberdyne
-=Windows and Networking MOD=-Guys has anybody looked at this? I am bringing it up again, it is time sensitive.

Regards,

Cyberdyne|||http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlbackuprest.mspxsql

Sunday, March 25, 2012

Backing Up databases with Enterprise Manager

Please forgive my ignorance - I'm completely new to MSSQL.

Our office bought a set of Laserfiche licenses and had to also buy MSSQL to handle the database end of things. Part of my job is to make sure everything gets backed up. I want to use Enterprise Manager to back up the databases which seems straightforward enough - even though I've never done it.

Our Network Admin has installed a temporary USB drive to hold our back-ups until a more permanent form of media can be installed. He is using drive compression to maximize the space available. The server sees it as Drive F:

I created a folder on F: to contain my MSSQL Back-ups. Then I opened Enterprise Manager and clicked on SQL Server Group, which contains two databases:

(local) (Windows NT)

and

CYWD_IMAGE/LASERFICHE (Windows NT)

My understanding is that they both have to be backed up.

I clicked on the first one, then selected the Database Maintenence Plan Wizard from the 'Tools' menu. I stepped through the process (choosing 'all databases') until I got to the point where I could specify the back-up directory. I was able to browse right to the folder I created and choose it. I could then finish the process normally. The problem is that when I selected the second database (CYWD_IMAGE/LASERFICHE) and launched the wizard I was unable to browse to my folder. I could choose the F: Drive but no folder showed up under it. Oddly, it would not even show me my D: partition (just thought I'd mention that in case it is somehow relevent).

I don't see any difference in the properties tabs between these two databases. The obvious difference is the name, and that one says (local) and the other does not.

I really don't want to choose to dump the back-up into the root of F:

Can anyone tell me what I'm doing wrong?

Thanks in advance.

MacIf the plan created by your first Wizard backs up "all databases', why do you need to create a second backup plan?|||If the plan created by your first Wizard backs up "all databases', why do you need to create a second backup plan?

There are two servers under the SQL Servers Group, and each contain multiple databases. As far as I can tell the back-up plan will not span both servers, therefore the need for two plans.

It turns out the second server and it's databases are not currently in use so I lucked out. I am still curious why the second server and it's databases behaved this way, though.

Follow-up question. How to I review the plan I created to make modifications? If I pull up the Maintnence Planner there is no option to review exisiting plans.|||If the two servers are on different machines, then they will have different drives. You created a folder on the F drive of one machine, but not the other.

To review or edit the maitenance plans, open up the job they created in the SQL Server Agent tab.|||If the two servers are on different machines, then they will have different drives. You created a folder on the F drive of one machine, but not the other.

To review or edit the maitenance plans, open up the job they created in the SQL Server Agent tab.

Thanks - the servers both appear to be the same machine. Our other servers do not have external (or network) drives that would evaluate to F: - but it was a good thing to check for!

I was able to locate the SQL Server Agent Tab, I appreciate the information!

I'm sure I'll have other questions later, but I'm set for now.|||Be careful not to fill up your harddrive|||Be careful not to fill up your harddrive

Will do - Supposedly I'm going to have to burn off older jobs to dvd to avoid that.

Doesn't sounds like I'll be getting any additional storage drives any time soon, does it? ;)

Backing Up Data

Hello
I have a MSSQL database supplied by my web host. I'd like to be able to perf
orm periodic backups (1 or more times a week). The database is small and I h
ave a fast connection so the speed isn't a problem. I would like the backups
to be automated. I have a
linux server where I'd like to store the data, I'm not sure if this can be d
one? How do users backup?
Thanks
DiDianne
Please refer to the BOL on BACKUP DATABASE databasename TO......
"Dianne" <anonymous@.discussions.microsoft.com> wrote in message
news:A12148F5-B98A-48AD-8B57-429976325C87@.microsoft.com...
> Hello
> I have a MSSQL database supplied by my web host. I'd like to be able to
perform periodic backups (1 or more times a week). The database is small and
I have a fast connection so the speed isn't a problem. I would like the
backups to be automated. I have a linux server where I'd like to store the
data, I'm not sure if this can be done? How do users backup?
> Thanks
> Di|||hi dianne,
you can automate backup process using Enterprise manager.
open enterprise manager,click on the any user database. go to the Tools menu
, click on
database maintenance planner. click next, check the required database you wa
nt. click next 2
times(since they are not specific to backup) you will come to a screen "spec
ify the database
backup plan". you can specify the destination as tape or disk. on the same s
creen you will get
an option to schedule(click the required frequency). click next, here you ca
n specify the
directory to which backup file will go. on the next screen if required sched
ule "tran. log"
backup.
This way you can automate the database backup using Enterprise manager.
<<
Never done above process, so you may have to take care of some OS level util
ity to transfer
backup files to linux server.
Vishal Parkar
vgparkar@.yahoo.co.in|||Hi,
1.Execute the BACKUP database command to backup the database to SQL server
local hard disk drive
2. Using FTP send the Backup file to Linux machine
How to automate
--
1. Using OSQL -Usa -Ppassword -Sserver -Q"backup database dbname to
disk='c:\backup\dbanme.bak' with init'
2. FTP the dbname.bak file to Linux server ip.
You can put the avobe 2 in a batch file and schedule it thru SQL agent ..
Jobs.
Thanks
Hari
MCDBA
"Dianne" <anonymous@.discussions.microsoft.com> wrote in message
news:A12148F5-B98A-48AD-8B57-429976325C87@.microsoft.com...
> Hello
> I have a MSSQL database supplied by my web host. I'd like to be able to
perform periodic backups (1 or more times a week). The database is small and
I have a fast connection so the speed isn't a problem. I would like the
backups to be automated. I have a linux server where I'd like to store the
data, I'm not sure if this can be done? How do users backup?
> Thanks
> Di|||Thank you very much. I appreciate all your help.
I may be missing something, and I am new to MSSQL. My access to the host run
ning MSSQL is limited. It's a web host account and I only have access using
Enterprise Manager on my workstation. I haven't got access to Windows server
s to run an agent at my end
and I can't on the host either because I don't have the permssions.
It looks like I will need a Windows server to do this?
Thank you.

Monday, February 13, 2012

Available MSSQL Servers during registration ...

Hi all,
Observation: When I use the "Register SQL Server Wizard" I noticed that
there are a number of SQL DB Servers that are not populating the "Available
servers" listbox. Note: this also occurs when I programatically generate a
list of database servers using the ODBC32 API's.
Question: How can I get this list to accurately reflect the databases on my
network? Are there settings on the database server that neet to be changed?
For example, my local development workstation has three databases on it --
the "(local)" instance, and two additional instances ("\DEV" and "\TEST").
The "(local)" instance shows up, but I am not seeing the two other instances
"<COMPUTERNAME>\DEV" and "<COMPUTERNAME>\TEST".
Thoughts?
Thanks!
WadeHi
You may have hide server checked in the SQL Servers TCP/IP setting.
John
"Wade" wrote:
> Hi all,
> Observation: When I use the "Register SQL Server Wizard" I noticed that
> there are a number of SQL DB Servers that are not populating the "Available
> servers" listbox. Note: this also occurs when I programatically generate a
> list of database servers using the ODBC32 API's.
> Question: How can I get this list to accurately reflect the databases on my
> network? Are there settings on the database server that neet to be changed?
> For example, my local development workstation has three databases on it --
> the "(local)" instance, and two additional instances ("\DEV" and "\TEST").
> The "(local)" instance shows up, but I am not seeing the two other instances
> "<COMPUTERNAME>\DEV" and "<COMPUTERNAME>\TEST".
> Thoughts?
> Thanks!
> Wade
>
>|||Hi John,
Thanks for the suggestion. However, I just checked, and all of these DB
servers have TCP/IP and Named Pipes enabled, and the "Hide server" checkbox
has not been checked.
Any other ideas?
Thanks,
Wade
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:EBECB381-89A7-456A-9016-921FDA02413B@.microsoft.com...
> Hi
> You may have hide server checked in the SQL Servers TCP/IP setting.
> John
> "Wade" wrote:
>> Hi all,
>> Observation: When I use the "Register SQL Server Wizard" I noticed that
>> there are a number of SQL DB Servers that are not populating the
>> "Available
>> servers" listbox. Note: this also occurs when I programatically generate
>> a
>> list of database servers using the ODBC32 API's.
>> Question: How can I get this list to accurately reflect the databases on
>> my
>> network? Are there settings on the database server that neet to be
>> changed?
>> For example, my local development workstation has three databases on
>> it --
>> the "(local)" instance, and two additional instances ("\DEV" and
>> "\TEST").
>> The "(local)" instance shows up, but I am not seeing the two other
>> instances
>> "<COMPUTERNAME>\DEV" and "<COMPUTERNAME>\TEST".
>> Thoughts?
>> Thanks!
>> Wade
>>|||The browsing implementation isn't guaranteed to find all servers, quite simply. Type the name.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Wade" <wwegner23NOEMAILhotmail.com> wrote in message
news:%23Dl9gR0pFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi John,
> Thanks for the suggestion. However, I just checked, and all of these DB servers have TCP/IP and
> Named Pipes enabled, and the "Hide server" checkbox has not been checked.
> Any other ideas?
> Thanks,
> Wade
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:EBECB381-89A7-456A-9016-921FDA02413B@.microsoft.com...
>> Hi
>> You may have hide server checked in the SQL Servers TCP/IP setting.
>> John
>> "Wade" wrote:
>> Hi all,
>> Observation: When I use the "Register SQL Server Wizard" I noticed that
>> there are a number of SQL DB Servers that are not populating the "Available
>> servers" listbox. Note: this also occurs when I programatically generate a
>> list of database servers using the ODBC32 API's.
>> Question: How can I get this list to accurately reflect the databases on my
>> network? Are there settings on the database server that neet to be changed?
>> For example, my local development workstation has three databases on it --
>> the "(local)" instance, and two additional instances ("\DEV" and "\TEST").
>> The "(local)" instance shows up, but I am not seeing the two other instances
>> "<COMPUTERNAME>\DEV" and "<COMPUTERNAME>\TEST".
>> Thoughts?
>> Thanks!
>> Wade
>>
>|||Thanks for the info Tibor. Just curious -- is this a definitive answer, or
just your experience? Do you know of any KB article (or anything else) that
discusses this?
Thanks!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eFcIbl0pFHA.3572@.TK2MSFTNGP09.phx.gbl...
> The browsing implementation isn't guaranteed to find all servers, quite
> simply. Type the name.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Wade" <wwegner23NOEMAILhotmail.com> wrote in message
> news:%23Dl9gR0pFHA.3064@.TK2MSFTNGP15.phx.gbl...
>> Hi John,
>> Thanks for the suggestion. However, I just checked, and all of these DB
>> servers have TCP/IP and Named Pipes enabled, and the "Hide server"
>> checkbox has not been checked.
>> Any other ideas?
>> Thanks,
>> Wade
>> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
>> news:EBECB381-89A7-456A-9016-921FDA02413B@.microsoft.com...
>> Hi
>> You may have hide server checked in the SQL Servers TCP/IP setting.
>> John
>> "Wade" wrote:
>> Hi all,
>> Observation: When I use the "Register SQL Server Wizard" I noticed that
>> there are a number of SQL DB Servers that are not populating the
>> "Available
>> servers" listbox. Note: this also occurs when I programatically
>> generate a
>> list of database servers using the ODBC32 API's.
>> Question: How can I get this list to accurately reflect the databases
>> on my
>> network? Are there settings on the database server that neet to be
>> changed?
>> For example, my local development workstation has three databases on
>> it --
>> the "(local)" instance, and two additional instances ("\DEV" and
>> "\TEST").
>> The "(local)" instance shows up, but I am not seeing the two other
>> instances
>> "<COMPUTERNAME>\DEV" and "<COMPUTERNAME>\TEST".
>> Thoughts?
>> Thanks!
>> Wade
>>
>>
>|||I think there might be a KN article, should be quick to find out, with a few good keyword to search
for. Also, check www.sqldev.net. There are some examples on calling this browser functionality from
code and there might also be some text on the shortcomings. Below is some text I saved from GertD,
from a previous posting. Come to thing of it, searching the ng archives can be a good idea as well:
There is no way to do return a guaranteed list of install SQL Servers, not
even using the old LAN Manager NetServersEnum looking for SV_TYPE_SQLSERVER
ListAvailableServers using the ODBC function SQLBrowseConnect. This function
performs a discovery broadcast on the network to discover installed SQL
Servers, the SQL Server have to respond on the discovery broadcast, hence
that you will find that not all servers will show up. Some conditions:
1: Only running SQL Servers will show up, however there is a detail (mostly
15 min.) after which the broadcast can be responded by the master browser
services on the network, incase the SQL Server just stopped.
2: On 7.0 the default protocol is Named Pipes which is NetBIOS based, in
2000 it is TCP/IP sockets, hence the broadcast in 7.0 was a NetBIOS
broadcast, which one does not have guaranteed delivery, two most routers are
configured not to pass on NetBIOS broadcast so you only will get subset of
the list of servers, mainly the one in you subnet. For sure the broadcast
does not go beyond or between NT domains. In 2000 this has been changed to a
TCP UDP broadcast.
3: In 7.0, Win9x versions do not respond on the NetBIOS broadcast, hence do
not show up in the list, in 2000 this has been changed to TCP UDP which is
understood by Win9x
4: The response has to be back to the originator within a certain timeout,
otherwise the server named is not included in the list.
Bottom-line, this is never going to return a list of SQL Server that you can
rely on. In 2000 the ability to register a SQL Server in the Active
Directory has been added, this would be a better solution.
That is not what SQL-DMO uses in SQL Server 7.0 and later. This was the case
in 6.5 and previous releases, when only NT was supported.
In 7.0 and later SQL-DMO uses the ODBC function SQLBrowseConnect to retrieve
a list of servers.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Wade" <wwegner23NOEMAILhotmail.com> wrote in message news:Op5cma1pFHA.2076@.TK2MSFTNGP14.phx.gbl...
> Thanks for the info Tibor. Just curious -- is this a definitive answer, or just your experience?
> Do you know of any KB article (or anything else) that discusses this?
> Thanks!
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:eFcIbl0pFHA.3572@.TK2MSFTNGP09.phx.gbl...
>> The browsing implementation isn't guaranteed to find all servers, quite simply. Type the name.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Wade" <wwegner23NOEMAILhotmail.com> wrote in message
>> news:%23Dl9gR0pFHA.3064@.TK2MSFTNGP15.phx.gbl...
>> Hi John,
>> Thanks for the suggestion. However, I just checked, and all of these DB servers have TCP/IP and
>> Named Pipes enabled, and the "Hide server" checkbox has not been checked.
>> Any other ideas?
>> Thanks,
>> Wade
>> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
>> news:EBECB381-89A7-456A-9016-921FDA02413B@.microsoft.com...
>> Hi
>> You may have hide server checked in the SQL Servers TCP/IP setting.
>> John
>> "Wade" wrote:
>> Hi all,
>> Observation: When I use the "Register SQL Server Wizard" I noticed that
>> there are a number of SQL DB Servers that are not populating the "Available
>> servers" listbox. Note: this also occurs when I programatically generate a
>> list of database servers using the ODBC32 API's.
>> Question: How can I get this list to accurately reflect the databases on my
>> network? Are there settings on the database server that neet to be changed?
>> For example, my local development workstation has three databases on it --
>> the "(local)" instance, and two additional instances ("\DEV" and "\TEST").
>> The "(local)" instance shows up, but I am not seeing the two other instances
>> "<COMPUTERNAME>\DEV" and "<COMPUTERNAME>\TEST".
>> Thoughts?
>> Thanks!
>> Wade
>>
>>
>>
>|||Thanks, Tibor.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%239l9QZ7pFHA.620@.TK2MSFTNGP15.phx.gbl...
>I think there might be a KN article, should be quick to find out, with a
>few good keyword to search for. Also, check www.sqldev.net. There are some
>examples on calling this browser functionality from code and there might
>also be some text on the shortcomings. Below is some text I saved from
>GertD, from a previous posting. Come to thing of it, searching the ng
>archives can be a good idea as well:
> There is no way to do return a guaranteed list of install SQL Servers, not
> even using the old LAN Manager NetServersEnum looking for
> SV_TYPE_SQLSERVER
> ListAvailableServers using the ODBC function SQLBrowseConnect. This
> function
> performs a discovery broadcast on the network to discover installed SQL
> Servers, the SQL Server have to respond on the discovery broadcast, hence
> that you will find that not all servers will show up. Some conditions:
> 1: Only running SQL Servers will show up, however there is a detail
> (mostly
> 15 min.) after which the broadcast can be responded by the master browser
> services on the network, incase the SQL Server just stopped.
> 2: On 7.0 the default protocol is Named Pipes which is NetBIOS based, in
> 2000 it is TCP/IP sockets, hence the broadcast in 7.0 was a NetBIOS
> broadcast, which one does not have guaranteed delivery, two most routers
> are
> configured not to pass on NetBIOS broadcast so you only will get subset of
> the list of servers, mainly the one in you subnet. For sure the broadcast
> does not go beyond or between NT domains. In 2000 this has been changed to
> a
> TCP UDP broadcast.
> 3: In 7.0, Win9x versions do not respond on the NetBIOS broadcast, hence
> do
> not show up in the list, in 2000 this has been changed to TCP UDP which is
> understood by Win9x
> 4: The response has to be back to the originator within a certain timeout,
> otherwise the server named is not included in the list.
> Bottom-line, this is never going to return a list of SQL Server that you
> can
> rely on. In 2000 the ability to register a SQL Server in the Active
> Directory has been added, this would be a better solution.
>
> That is not what SQL-DMO uses in SQL Server 7.0 and later. This was the
> case
> in 6.5 and previous releases, when only NT was supported.
> In 7.0 and later SQL-DMO uses the ODBC function SQLBrowseConnect to
> retrieve
> a list of servers.
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Wade" <wwegner23NOEMAILhotmail.com> wrote in message
> news:Op5cma1pFHA.2076@.TK2MSFTNGP14.phx.gbl...
>> Thanks for the info Tibor. Just curious -- is this a definitive answer,
>> or just your experience? Do you know of any KB article (or anything else)
>> that discusses this?
>> Thanks!
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:eFcIbl0pFHA.3572@.TK2MSFTNGP09.phx.gbl...
>> The browsing implementation isn't guaranteed to find all servers, quite
>> simply. Type the name.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Wade" <wwegner23NOEMAILhotmail.com> wrote in message
>> news:%23Dl9gR0pFHA.3064@.TK2MSFTNGP15.phx.gbl...
>> Hi John,
>> Thanks for the suggestion. However, I just checked, and all of these
>> DB servers have TCP/IP and Named Pipes enabled, and the "Hide server"
>> checkbox has not been checked.
>> Any other ideas?
>> Thanks,
>> Wade
>> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
>> news:EBECB381-89A7-456A-9016-921FDA02413B@.microsoft.com...
>> Hi
>> You may have hide server checked in the SQL Servers TCP/IP setting.
>> John
>> "Wade" wrote:
>> Hi all,
>> Observation: When I use the "Register SQL Server Wizard" I noticed
>> that
>> there are a number of SQL DB Servers that are not populating the
>> "Available
>> servers" listbox. Note: this also occurs when I programatically
>> generate a
>> list of database servers using the ODBC32 API's.
>> Question: How can I get this list to accurately reflect the databases
>> on my
>> network? Are there settings on the database server that neet to be
>> changed?
>> For example, my local development workstation has three databases on
>> it --
>> the "(local)" instance, and two additional instances ("\DEV" and
>> "\TEST").
>> The "(local)" instance shows up, but I am not seeing the two other
>> instances
>> "<COMPUTERNAME>\DEV" and "<COMPUTERNAME>\TEST".
>> Thoughts?
>> Thanks!
>> Wade
>>
>>
>>
>>
>

Available MSSQL Servers during registration ...

Hi all,
Observation: When I use the "Register SQL Server Wizard" I noticed that
there are a number of SQL DB Servers that are not populating the "Available
servers" listbox. Note: this also occurs when I programatically generate a
list of database servers using the ODBC32 API's.
Question: How can I get this list to accurately reflect the databases on my
network? Are there settings on the database server that neet to be changed?
For example, my local development workstation has three databases on it --
the "(local)" instance, and two additional instances ("\DEV" and "\TEST").
The "(local)" instance shows up, but I am not seeing the two other instances
"<COMPUTERNAME>\DEV" and "<COMPUTERNAME>\TEST".
Thoughts?
Thanks!
Wade
Hi
You may have hide server checked in the SQL Servers TCP/IP setting.
John
"Wade" wrote:

> Hi all,
> Observation: When I use the "Register SQL Server Wizard" I noticed that
> there are a number of SQL DB Servers that are not populating the "Available
> servers" listbox. Note: this also occurs when I programatically generate a
> list of database servers using the ODBC32 API's.
> Question: How can I get this list to accurately reflect the databases on my
> network? Are there settings on the database server that neet to be changed?
> For example, my local development workstation has three databases on it --
> the "(local)" instance, and two additional instances ("\DEV" and "\TEST").
> The "(local)" instance shows up, but I am not seeing the two other instances
> "<COMPUTERNAME>\DEV" and "<COMPUTERNAME>\TEST".
> Thoughts?
> Thanks!
> Wade
>
>
|||Hi John,
Thanks for the suggestion. However, I just checked, and all of these DB
servers have TCP/IP and Named Pipes enabled, and the "Hide server" checkbox
has not been checked.
Any other ideas?
Thanks,
Wade
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:EBECB381-89A7-456A-9016-921FDA02413B@.microsoft.com...[vbcol=seagreen]
> Hi
> You may have hide server checked in the SQL Servers TCP/IP setting.
> John
> "Wade" wrote:
|||The browsing implementation isn't guaranteed to find all servers, quite simply. Type the name.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Wade" <wwegner23NOEMAILhotmail.com> wrote in message
news:%23Dl9gR0pFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi John,
> Thanks for the suggestion. However, I just checked, and all of these DB servers have TCP/IP and
> Named Pipes enabled, and the "Hide server" checkbox has not been checked.
> Any other ideas?
> Thanks,
> Wade
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:EBECB381-89A7-456A-9016-921FDA02413B@.microsoft.com...
>
|||Thanks for the info Tibor. Just curious -- is this a definitive answer, or
just your experience? Do you know of any KB article (or anything else) that
discusses this?
Thanks!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eFcIbl0pFHA.3572@.TK2MSFTNGP09.phx.gbl...
> The browsing implementation isn't guaranteed to find all servers, quite
> simply. Type the name.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Wade" <wwegner23NOEMAILhotmail.com> wrote in message
> news:%23Dl9gR0pFHA.3064@.TK2MSFTNGP15.phx.gbl...
>
|||I think there might be a KN article, should be quick to find out, with a few good keyword to search
for. Also, check www.sqldev.net. There are some examples on calling this browser functionality from
code and there might also be some text on the shortcomings. Below is some text I saved from GertD,
from a previous posting. Come to thing of it, searching the ng archives can be a good idea as well:
There is no way to do return a guaranteed list of install SQL Servers, not
even using the old LAN Manager NetServersEnum looking for SV_TYPE_SQLSERVER
ListAvailableServers using the ODBC function SQLBrowseConnect. This function
performs a discovery broadcast on the network to discover installed SQL
Servers, the SQL Server have to respond on the discovery broadcast, hence
that you will find that not all servers will show up. Some conditions:
1: Only running SQL Servers will show up, however there is a detail (mostly
15 min.) after which the broadcast can be responded by the master browser
services on the network, incase the SQL Server just stopped.
2: On 7.0 the default protocol is Named Pipes which is NetBIOS based, in
2000 it is TCP/IP sockets, hence the broadcast in 7.0 was a NetBIOS
broadcast, which one does not have guaranteed delivery, two most routers are
configured not to pass on NetBIOS broadcast so you only will get subset of
the list of servers, mainly the one in you subnet. For sure the broadcast
does not go beyond or between NT domains. In 2000 this has been changed to a
TCP UDP broadcast.
3: In 7.0, Win9x versions do not respond on the NetBIOS broadcast, hence do
not show up in the list, in 2000 this has been changed to TCP UDP which is
understood by Win9x
4: The response has to be back to the originator within a certain timeout,
otherwise the server named is not included in the list.
Bottom-line, this is never going to return a list of SQL Server that you can
rely on. In 2000 the ability to register a SQL Server in the Active
Directory has been added, this would be a better solution.
That is not what SQL-DMO uses in SQL Server 7.0 and later. This was the case
in 6.5 and previous releases, when only NT was supported.
In 7.0 and later SQL-DMO uses the ODBC function SQLBrowseConnect to retrieve
a list of servers.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Wade" <wwegner23NOEMAILhotmail.com> wrote in message news:Op5cma1pFHA.2076@.TK2MSFTNGP14.phx.gbl...
> Thanks for the info Tibor. Just curious -- is this a definitive answer, or just your experience?
> Do you know of any KB article (or anything else) that discusses this?
> Thanks!
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:eFcIbl0pFHA.3572@.TK2MSFTNGP09.phx.gbl...
>
|||Thanks, Tibor.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%239l9QZ7pFHA.620@.TK2MSFTNGP15.phx.gbl...
>I think there might be a KN article, should be quick to find out, with a
>few good keyword to search for. Also, check www.sqldev.net. There are some
>examples on calling this browser functionality from code and there might
>also be some text on the shortcomings. Below is some text I saved from
>GertD, from a previous posting. Come to thing of it, searching the ng
>archives can be a good idea as well:
> There is no way to do return a guaranteed list of install SQL Servers, not
> even using the old LAN Manager NetServersEnum looking for
> SV_TYPE_SQLSERVER
> ListAvailableServers using the ODBC function SQLBrowseConnect. This
> function
> performs a discovery broadcast on the network to discover installed SQL
> Servers, the SQL Server have to respond on the discovery broadcast, hence
> that you will find that not all servers will show up. Some conditions:
> 1: Only running SQL Servers will show up, however there is a detail
> (mostly
> 15 min.) after which the broadcast can be responded by the master browser
> services on the network, incase the SQL Server just stopped.
> 2: On 7.0 the default protocol is Named Pipes which is NetBIOS based, in
> 2000 it is TCP/IP sockets, hence the broadcast in 7.0 was a NetBIOS
> broadcast, which one does not have guaranteed delivery, two most routers
> are
> configured not to pass on NetBIOS broadcast so you only will get subset of
> the list of servers, mainly the one in you subnet. For sure the broadcast
> does not go beyond or between NT domains. In 2000 this has been changed to
> a
> TCP UDP broadcast.
> 3: In 7.0, Win9x versions do not respond on the NetBIOS broadcast, hence
> do
> not show up in the list, in 2000 this has been changed to TCP UDP which is
> understood by Win9x
> 4: The response has to be back to the originator within a certain timeout,
> otherwise the server named is not included in the list.
> Bottom-line, this is never going to return a list of SQL Server that you
> can
> rely on. In 2000 the ability to register a SQL Server in the Active
> Directory has been added, this would be a better solution.
>
> That is not what SQL-DMO uses in SQL Server 7.0 and later. This was the
> case
> in 6.5 and previous releases, when only NT was supported.
> In 7.0 and later SQL-DMO uses the ODBC function SQLBrowseConnect to
> retrieve
> a list of servers.
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Wade" <wwegner23NOEMAILhotmail.com> wrote in message
> news:Op5cma1pFHA.2076@.TK2MSFTNGP14.phx.gbl...
>

Available MSSQL Servers during registration ...

Hi all,
Observation: When I use the "Register SQL Server Wizard" I noticed that
there are a number of SQL DB Servers that are not populating the "Available
servers" listbox. Note: this also occurs when I programatically generate a
list of database servers using the ODBC32 API's.
Question: How can I get this list to accurately reflect the databases on my
network? Are there settings on the database server that neet to be changed?
For example, my local development workstation has three databases on it --
the "(local)" instance, and two additional instances ("\DEV" and "\TEST").
The "(local)" instance shows up, but I am not seeing the two other instances
"<COMPUTERNAME>\DEV" and "<COMPUTERNAME>\TEST".
Thoughts?
Thanks!
WadeHi
You may have hide server checked in the SQL Servers TCP/IP setting.
John
"Wade" wrote:

> Hi all,
> Observation: When I use the "Register SQL Server Wizard" I noticed that
> there are a number of SQL DB Servers that are not populating the "Availabl
e
> servers" listbox. Note: this also occurs when I programatically generate
a
> list of database servers using the ODBC32 API's.
> Question: How can I get this list to accurately reflect the databases on m
y
> network? Are there settings on the database server that neet to be change
d?
> For example, my local development workstation has three databases on it --
> the "(local)" instance, and two additional instances ("\DEV" and "\TEST").
> The "(local)" instance shows up, but I am not seeing the two other instanc
es
> "<COMPUTERNAME>\DEV" and "<COMPUTERNAME>\TEST".
> Thoughts?
> Thanks!
> Wade
>
>|||Hi John,
Thanks for the suggestion. However, I just checked, and all of these DB
servers have TCP/IP and Named Pipes enabled, and the "Hide server" checkbox
has not been checked.
Any other ideas?
Thanks,
Wade
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:EBECB381-89A7-456A-9016-921FDA02413B@.microsoft.com...[vbcol=seagreen]
> Hi
> You may have hide server checked in the SQL Servers TCP/IP setting.
> John
> "Wade" wrote:
>|||The browsing implementation isn't guaranteed to find all servers, quite simp
ly. Type the name.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Wade" <wwegner23NOEMAILhotmail.com> wrote in message
news:%23Dl9gR0pFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi John,
> Thanks for the suggestion. However, I just checked, and all of these DB s
ervers have TCP/IP and
> Named Pipes enabled, and the "Hide server" checkbox has not been checked.
> Any other ideas?
> Thanks,
> Wade
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:EBECB381-89A7-456A-9016-921FDA02413B@.microsoft.com...
>|||Thanks for the info Tibor. Just curious -- is this a definitive answer, or
just your experience? Do you know of any KB article (or anything else) that
discusses this?
Thanks!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eFcIbl0pFHA.3572@.TK2MSFTNGP09.phx.gbl...
> The browsing implementation isn't guaranteed to find all servers, quite
> simply. Type the name.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Wade" <wwegner23NOEMAILhotmail.com> wrote in message
> news:%23Dl9gR0pFHA.3064@.TK2MSFTNGP15.phx.gbl...
>|||I think there might be a KN article, should be quick to find out, with a few
good keyword to search
for. Also, check www.sqldev.net. There are some examples on calling this bro
wser functionality from
code and there might also be some text on the shortcomings. Below is some te
xt I saved from GertD,
from a previous posting. Come to thing of it, searching the ng archives can
be a good idea as well:
There is no way to do return a guaranteed list of install SQL Servers, not
even using the old LAN Manager NetServersEnum looking for SV_TYPE_SQLSERVER
ListAvailableServers using the ODBC function SQLBrowseConnect. This function
performs a discovery broadcast on the network to discover installed SQL
Servers, the SQL Server have to respond on the discovery broadcast, hence
that you will find that not all servers will show up. Some conditions:
1: Only running SQL Servers will show up, however there is a detail (mostly
15 min.) after which the broadcast can be responded by the master browser
services on the network, incase the SQL Server just stopped.
2: On 7.0 the default protocol is Named Pipes which is NetBIOS based, in
2000 it is TCP/IP sockets, hence the broadcast in 7.0 was a NetBIOS
broadcast, which one does not have guaranteed delivery, two most routers are
configured not to pass on NetBIOS broadcast so you only will get subset of
the list of servers, mainly the one in you subnet. For sure the broadcast
does not go beyond or between NT domains. In 2000 this has been changed to a
TCP UDP broadcast.
3: In 7.0, Win9x versions do not respond on the NetBIOS broadcast, hence do
not show up in the list, in 2000 this has been changed to TCP UDP which is
understood by Win9x
4: The response has to be back to the originator within a certain timeout,
otherwise the server named is not included in the list.
Bottom-line, this is never going to return a list of SQL Server that you can
rely on. In 2000 the ability to register a SQL Server in the Active
Directory has been added, this would be a better solution.
That is not what SQL-DMO uses in SQL Server 7.0 and later. This was the case
in 6.5 and previous releases, when only NT was supported.
In 7.0 and later SQL-DMO uses the ODBC function SQLBrowseConnect to retrieve
a list of servers.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Wade" <wwegner23NOEMAILhotmail.com> wrote in message news:Op5cma1pFHA.2076@.TK2MSFTNGP14.phx
.gbl...
> Thanks for the info Tibor. Just curious -- is this a definitive answer, o
r just your experience?
> Do you know of any KB article (or anything else) that discusses this?
> Thanks!
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n message
> news:eFcIbl0pFHA.3572@.TK2MSFTNGP09.phx.gbl...
>|||Thanks, Tibor.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%239l9QZ7pFHA.620@.TK2MSFTNGP15.phx.gbl...
>I think there might be a KN article, should be quick to find out, with a
>few good keyword to search for. Also, check www.sqldev.net. There are some
>examples on calling this browser functionality from code and there might
>also be some text on the shortcomings. Below is some text I saved from
>GertD, from a previous posting. Come to thing of it, searching the ng
>archives can be a good idea as well:
> There is no way to do return a guaranteed list of install SQL Servers, not
> even using the old LAN Manager NetServersEnum looking for
> SV_TYPE_SQLSERVER
> ListAvailableServers using the ODBC function SQLBrowseConnect. This
> function
> performs a discovery broadcast on the network to discover installed SQL
> Servers, the SQL Server have to respond on the discovery broadcast, hence
> that you will find that not all servers will show up. Some conditions:
> 1: Only running SQL Servers will show up, however there is a detail
> (mostly
> 15 min.) after which the broadcast can be responded by the master browser
> services on the network, incase the SQL Server just stopped.
> 2: On 7.0 the default protocol is Named Pipes which is NetBIOS based, in
> 2000 it is TCP/IP sockets, hence the broadcast in 7.0 was a NetBIOS
> broadcast, which one does not have guaranteed delivery, two most routers
> are
> configured not to pass on NetBIOS broadcast so you only will get subset of
> the list of servers, mainly the one in you subnet. For sure the broadcast
> does not go beyond or between NT domains. In 2000 this has been changed to
> a
> TCP UDP broadcast.
> 3: In 7.0, Win9x versions do not respond on the NetBIOS broadcast, hence
> do
> not show up in the list, in 2000 this has been changed to TCP UDP which is
> understood by Win9x
> 4: The response has to be back to the originator within a certain timeout,
> otherwise the server named is not included in the list.
> Bottom-line, this is never going to return a list of SQL Server that you
> can
> rely on. In 2000 the ability to register a SQL Server in the Active
> Directory has been added, this would be a better solution.
>
> That is not what SQL-DMO uses in SQL Server 7.0 and later. This was the
> case
> in 6.5 and previous releases, when only NT was supported.
> In 7.0 and later SQL-DMO uses the ODBC function SQLBrowseConnect to
> retrieve
> a list of servers.
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Wade" <wwegner23NOEMAILhotmail.com> wrote in message
> news:Op5cma1pFHA.2076@.TK2MSFTNGP14.phx.gbl...
>

Auto-truncate log file

I have MSSQL server 2000.
I want that when log file is full, he would be truncated.
how to do this?
thanks
Set the database to simple recovery mode.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"aa" <vaidas.gudas@.rst.lt> wrote in message news:eJc7j2qWFHA.132@.TK2MSFTNGP14.phx.gbl...
>I have MSSQL server 2000.
> I want that when log file is full, he would be truncated.
> how to do this?
> thanks
>
|||To add to Tibor's response, the transaction log is truncated automatically
when the database is in the SIMPLE recovery model. This model is
appropriate when your recovery plan is to restore from database backup and
it is acceptable to lose database changes made since the backup.
In the FULL or BULK_LOGGED recovery model, you need to schedule regular
transaction log backups to provide forward recovery capability and keep the
log size reasonable. The log still needs to be sized to accommodate
activity between log backups. Although you can truncate the log even in the
FULL or BULK_LOGGED model with BACKUP LOG ... TRUNCATE_ONLY, this breaks the
log backup sequence and defeats the purpose of these recovery models.
Hope this helps.
Dan Guzman
SQL Server MVP
"aa" <vaidas.gudas@.rst.lt> wrote in message
news:eJc7j2qWFHA.132@.TK2MSFTNGP14.phx.gbl...
>I have MSSQL server 2000.
> I want that when log file is full, he would be truncated.
> how to do this?
> thanks
>

Auto-truncate log file

I have MSSQL server 2000.
I want that when log file is full, he would be truncated.
how to do this?
thanksSet the database to simple recovery mode.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"aa" <vaidas.gudas@.rst.lt> wrote in message news:eJc7j2qWFHA.132@.TK2MSFTNGP14.phx.gbl...[vbc
ol=seagreen]
>I have MSSQL server 2000.
> I want that when log file is full, he would be truncated.
> how to do this?
> thanks
>[/vbcol]|||To add to Tibor's response, the transaction log is truncated automatically
when the database is in the SIMPLE recovery model. This model is
appropriate when your recovery plan is to restore from database backup and
it is acceptable to lose database changes made since the backup.
In the FULL or BULK_LOGGED recovery model, you need to schedule regular
transaction log backups to provide forward recovery capability and keep the
log size reasonable. The log still needs to be sized to accommodate
activity between log backups. Although you can truncate the log even in the
FULL or BULK_LOGGED model with BACKUP LOG ... TRUNCATE_ONLY, this breaks the
log backup sequence and defeats the purpose of these recovery models.
Hope this helps.
Dan Guzman
SQL Server MVP
"aa" <vaidas.gudas@.rst.lt> wrote in message
news:eJc7j2qWFHA.132@.TK2MSFTNGP14.phx.gbl...
>I have MSSQL server 2000.
> I want that when log file is full, he would be truncated.
> how to do this?
> thanks
>

Auto-truncate log file

I have MSSQL server 2000.
I want that when log file is full, he would be truncated.
how to do this?
thanksSet the database to simple recovery mode.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"aa" <vaidas.gudas@.rst.lt> wrote in message news:eJc7j2qWFHA.132@.TK2MSFTNGP14.phx.gbl...
>I have MSSQL server 2000.
> I want that when log file is full, he would be truncated.
> how to do this?
> thanks
>|||To add to Tibor's response, the transaction log is truncated automatically
when the database is in the SIMPLE recovery model. This model is
appropriate when your recovery plan is to restore from database backup and
it is acceptable to lose database changes made since the backup.
In the FULL or BULK_LOGGED recovery model, you need to schedule regular
transaction log backups to provide forward recovery capability and keep the
log size reasonable. The log still needs to be sized to accommodate
activity between log backups. Although you can truncate the log even in the
FULL or BULK_LOGGED model with BACKUP LOG ... TRUNCATE_ONLY, this breaks the
log backup sequence and defeats the purpose of these recovery models.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"aa" <vaidas.gudas@.rst.lt> wrote in message
news:eJc7j2qWFHA.132@.TK2MSFTNGP14.phx.gbl...
>I have MSSQL server 2000.
> I want that when log file is full, he would be truncated.
> how to do this?
> thanks
>