MSDE subscription expiration

Hi,
I need help on changing the subscription expiration using MSDE, i would
like to know how can i do this, im not familiar with OSQL commands.
Thanks
Is there anyone out there who knows this? i know this is simple for
those who already knows how, all i need is a simple parameter commands
on how to set the subscription expiration on the MSDE. If only the
requirement is SQL enterprise manager then i wont be here on the first
place. Please help.
Thanks
|||Since this is the SQL Server MSDE group then guys here should know at
least what im talking about.
|||> Since this is the SQL Server MSDE group then guys here should know at
> least what im talking about.
And i demand an answer right now?
MSDE can be downloaded for free and no subscription is needed So what are
you talking about?
Cheers,
Erik
"Angelo" <oracle_sigma@.yahoo.com> schreef in bericht
news:1138340405.295057.256040@.g43g2000cwa.googlegr oups.com...
> Since this is the SQL Server MSDE group then guys here should know at
> least what im talking about.
>
|||Hi Erik,
Thanks for the reply, what i need is a command parameters on how to set
the subscription expiration on MSDE, cause everytime when we didnt
synchronize our handhelds let say 3 weeks, it occurs a subscription
expiration. Could you tell me how can i set this just using the MSDE
osql commands?
really appreciate for your help
|||Hi Erik,
To clarify it more, please click on the link or copy and paste
http://groups.google.com.ph/group/mi...899b6eb4ce9f3a
All they are talking about is how to set USING enterprise manager, the
question is how can i set it using MSDE?
Thanks,
Angelo
|||Hi Erik,
To clarify it more, please copy and paste
http://groups.google.com.ph/group/mi...899b6eb4ce9f3a
All they are talking about is how to set USING enterprise manager, the
question is how can i set it using MSDE?
Thanks,
Angelo
|||See if these two articles help
http://msdn.microsoft.com/library/de...plmon_92ge.asp
http://msdn.microsoft.com/library/de..._repl_9b5a.asp
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Angelo" <oracle_sigma@.yahoo.com> wrote in message
news:1138590558.961274.264570@.g49g2000cwa.googlegr oups.com...
> Hi Erik,
> To clarify it more, please click on the link or copy and paste
> http://groups.google.com.ph/group/mi...899b6eb4ce9f3a
> All they are talking about is how to set USING enterprise manager, the
> question is how can i set it using MSDE?
> Thanks,
> Angelo
>
|||Hi Roger,
Many thanks for the info, yes it help me in some ways also. Can you
take a look on the scripts below if this is the one that i have to do?
Can you specifically key in all the necessary things?
************************************************** *******
DECLARE @.publication AS sysname
SET @.publication = N'[my_publication]'
USE [my_database]
EXEC sp_changepublication @.publication = @.publication,
@.property = N'retention',
@.value = [my_value]
GO
************************************************** ************
now the requirement is
Database Name = ServerDB
Publication Name = Pubserver1
Days required = at least 30 days
************************************************** ************
Actually someone gave me this instructions and i have to run this
scripts using osql -E -XXX.sql
Thanks,
Angelo
|||Hi Roger,
Can you help me put all the names to its proper place also?
When you have MSDE, is it 336 hours its default retention period
subscription expiration? or it depends on the service pack that it is
currently installed?
Thanks
Angelo

MSDE ReleaseA

Can i redistribute only osql.exe with my asp.net application
we are using licensed Install Shield for packaging..
we use this osql.exe for creating and setup database...
regards
sahridhayan
hi,
sahridhayan wrote:
> Can i redistribute only osql.exe with my asp.net application
> we are using licensed Install Shield for packaging..
> we use this osql.exe for creating and setup database...
I do not think you can separate oSql.exe from the full MSDE package from a
legal point of view..
but perhaps you've better ask Microsoft representatives...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I'm not sure about MSDE, but if you have a SQL Server license you can
distribute OSQL. Refer to REDIST.TXT for a listing of all the
redistributable components of SQL Server.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3h5uarFf6jcoU1@.individual.net...
> hi,
> sahridhayan wrote:
> I do not think you can separate oSql.exe from the full MSDE package from a
> legal point of view..
> but perhaps you've better ask Microsoft representatives...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi,
Desperado wrote:
> I'm not sure about MSDE, but if you have a SQL Server license you can
> distribute OSQL. Refer to REDIST.TXT for a listing of all the
> redistributable components of SQL Server.
>
again, I'm not sure you can "cannibalize" osql.exe that way... of course,
having a full SQL Server licence, you can install the Client Tools, that
include quiet all tools... but this way I'm little skeptic... but I'm not a
lawyer
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE regualr maintenance - help

Hi folks
New to MSDE...
1. What is the best options to use when doing backups?
option 1. OSQL -U sa -P password -S server -Q "BACKUP DATABASE db1 TO DISK
= 'c:\Backups\backup1.bck'"
option 2. OSQL -U sa -P password -S server -Q "BACKUP DATABASE db1 TO DISK =
'C:\backups\backup1.bck' WITH FORMAT, STATS"
2. Should I also be doing a reindex? I would like to do a batch sql job (
like above backup)
USE DB1
GO
sp_msforeachtable @.command1 = 'DBCC DBREINDEX ([?])'
3. Should I do a Database check if yes, before or after backup...
dbcc checkdb ('database')
4. Would also like to get information DB size - just to mkae sure its stay's
under the 2GB limit.
Someone recommend the followinf - but not sure what they all do...
Save the following commands to a file named "WhatsUpMaint.bat":
osql -E -D WhatsUp -Q "DBCC SHRINKDATABASE (WhatsUp)"
osql -E -D WhatsUp -Q "EXEC sp_MsForEachTable 'DBCC DBREINDEX (''?'', '''',
0)'"
osql -E -D WhatsUp -Q "EXEC sp_createstats"
osql -E -D WhatsUp -Q "EXEC sp_updatestats"
osql -E -D WhatsUp -Q "EXEC sp_MsForEachTable 'sp_recompile ''?'''"
osql -E -D WhatsUp -Q "DBCC UPDATEUSAGE ('WhatsUp')"
osql -E -D WhatsUp -Q "EXEC sp_cycle_errorlog"
hi Danny,
Danny wrote:
> 1. What is the best options to use when doing backups?
> option 1. OSQL -U sa -P password -S server -Q "BACKUP DATABASE db1
> TO DISK = 'c:\Backups\backup1.bck'"
> option 2. OSQL -U sa -P password -S server -Q "BACKUP DATABASE db1 TO
> DISK = 'C:\backups\backup1.bck' WITH FORMAT, STATS"
the "bad thing" of this batch is that it includes sa's password in clear
text... please do not code a cmd/bat file this way :D
create a "backup" login with appropriate permissions and hardcode it's
credentials, not "sa" ones :D
WITH FORMAT specifies a new media set will be created.. so this depends on
your actual requirements.. if you want to "append" your current backup to
existing ones, do not specify it, else, do it..
STATS, on the other hand, specify to output backup percentage to the
standard output..
if not specified you usually have an output like
BACKUP DATABASE pubs TO DISK = 'c:\pus.bak';
--<--
Processed 248 pages for database 'pubs', file 'pubs' on file 4.
Processed 1 pages for database 'pubs', file 'pubs_log' on file 4.
BACKUP DATABASE successfully processed 249 pages in 0.073 seconds (27.942
MB/sec).
where
BACKUP DATABASE pubs TO DISK = 'c:\pus.bak'
WITH STATS;
--<--
12 percent processed.
22 percent processed.
32 percent processed.
41 percent processed.
51 percent processed.
61 percent processed.
70 percent processed.
80 percent processed.
93 percent processed.
Processed 248 pages for database 'pubs', file 'pubs' on file 5.
100 percent processed.
Processed 1 pages for database 'pubs', file 'pubs_log' on file 5.
BACKUP DATABASE successfully processed 249 pages in 0.069 seconds (29.562
MB/sec).
if you do not specify a percent value, SQL Server uses a default of 10%..

> 2. Should I also be doing a reindex? I would like to do a batch sql
> job ( like above backup)
> USE DB1
> GO
> sp_msforeachtable @.command1 = 'DBCC DBREINDEX ([?])'
this statement uses an undocumented stored procedure, sp_msforeachtable, to
rebuild all indexes of each table object.. this obviously imply
"rebuilding" the whole table with clustered index.. so this implies both
time and file related implications... have a look at
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
for futher info, but, to our interest, reindexing is usually a "good thing"
to do :D

> 3. Should I do a Database check if yes, before or after backup...
> dbcc checkdb ('database')
you can go pre-backup

> 4. Would also like to get information DB size - just to mkae sure its
> stay's under the 2GB limit.
sorry, did not understand your requirement...

> Save the following commands to a file named "WhatsUpMaint.bat":
> osql -E -D WhatsUp -Q "DBCC SHRINKDATABASE (WhatsUp)"
about shrinking a database you can have a look at Tibor Karaszi's (SQL
Server MVP) article at http://www.karaszi.com/SQLServer/info_dont_shrink.asp
about the trusted connection you use here... -E indicates to connect as the
current logged in account.. and, as the statements you are executing require
high permissions in the instance context, this means the current interactive
Windows account is quite an admin... as this sounds to be a scheduled batch,
I'd opt for other credentials in order not to require to log in as such a
super man :D

> osql -E -D WhatsUp -Q "EXEC sp_MsForEachTable 'DBCC DBREINDEX (''?'',
> '''', 0)'"
> osql -E -D WhatsUp -Q "EXEC sp_createstats"
to my head this is not required as you usually set this at database level so
that statistics always are created and updated..

> osql -E -D WhatsUp -Q "EXEC sp_updatestats"
but this can be maintained as statistics are "rebuilt" when a certain
treshhold of changes is reached, so you can force it..

> osql -E -D WhatsUp -Q "EXEC sp_MsForEachTable 'sp_recompile ''?'''"
not correct.. this one is available for stored procedures only and not for
base tables...
causing the procedures to be recompiled at next execution time will
obviously imply penalties in their execution... I do usually not perform
that one..

> osql -E -D WhatsUp -Q "DBCC UPDATEUSAGE ('WhatsUp')"
this one re-syncs catalog's stats.. I do usually not do that if not
required.. but it does not hurt..

> osql -E -D WhatsUp -Q "EXEC sp_cycle_errorlog"
this one changes the current log to a new created one... I really do not do
that if not required in order to have a troubleshoot log to archive so some
reason.. but it does not imply penaltie/problems at all..
at the end of the game, I'd suggest to "log" the results of your
maintenances outputting them to a text file you can later inspect, send by
mail or whatever..
just add the
>filePathAndName.txt
parameter to your 1st oSql call to initilize your file and add[vbcol=seagreen]
parameter to the other ones, causing the results to be appended to that
file...
regards
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply

MSDE password change for "sa"

Hello,
If I can get into the default instance of MSDE using a Windows
account (trusted connection) using 'osql -E' is it possible for me to
change the 'sa' SQL account if I don't know the current password? The
Windows account is a domain admin and local box admin if that matters.
Also, can anyone point me to a Q article that will give me a step
by step on how to upgrade from MSDE to SQL so I can get past this 2GB
limitation?
If anyone can answer these I am definitely buying beers!!
Thanks,
Dan
If you can login as an admin on the box and the
builtin\administrators group login was not removed or
modified, you will be logged in as a member of the sysadmins
server role. As a sysadmin, you can execute the following to
change the sa password:
sp_password NULL, 'NewSaPassword', 'sa'
Upgrading to SQL Server isn't too bad. Run the SQL Server
installation CD. You will be asked if you want to upgrade
your existing instance or install a new one. Choose to
upgrade.
For more detailed steps on upgrading, you can refer to the
SQL Server Books Online topic:
How to perform an edition upgrade within SQL Server 2000
(Setup)
http://msdn.microsoft.com/library/en...stall_1d7y.asp
-Sue
On 15 Jun 2004 17:41:11 -0700, dankennedy24@.hotmail.com (Dan
Kennedy) wrote:

>Hello,
> If I can get into the default instance of MSDE using a Windows
>account (trusted connection) using 'osql -E' is it possible for me to
>change the 'sa' SQL account if I don't know the current password? The
>Windows account is a domain admin and local box admin if that matters.
> Also, can anyone point me to a Q article that will give me a step
>by step on how to upgrade from MSDE to SQL so I can get past this 2GB
>limitation?
>If anyone can answer these I am definitely buying beers!!
>Thanks,
>Dan
|||But the current "sa" password isn't blank... will that statement still
work? I login to the machine as a local admin and connect via the
osql statement as the same ID as I logon to the machine with.
Sue Hoegemeier <Sue_H@.nomail.please> wrote in message news:<np8vc0p2v2lfj8ke5mm0vf6f8vmrfg9plg@.4ax.com>. ..[vbcol=seagreen]
> If you can login as an admin on the box and the
> builtin\administrators group login was not removed or
> modified, you will be logged in as a member of the sysadmins
> server role. As a sysadmin, you can execute the following to
> change the sa password:
> sp_password NULL, 'NewSaPassword', 'sa'
> Upgrading to SQL Server isn't too bad. Run the SQL Server
> installation CD. You will be asked if you want to upgrade
> your existing instance or install a new one. Choose to
> upgrade.
> For more detailed steps on upgrading, you can refer to the
> SQL Server Books Online topic:
> How to perform an edition upgrade within SQL Server 2000
> (Setup)
> http://msdn.microsoft.com/library/en...stall_1d7y.asp
> -Sue
> On 15 Jun 2004 17:41:11 -0700, dankennedy24@.hotmail.com (Dan
> Kennedy) wrote:
|||Yes...it will still work. That's what you would use to reset any
password when you are logged in as a sysadmin. Just pass null for the
old password. It doesn't mean the password is null. It means you
aren't supplying the old password.
-Sue
On 16 Jun 2004 11:26:10 -0700, dankennedy24@.hotmail.com (Dan Kennedy)
wrote:
[vbcol=seagreen]
>But the current "sa" password isn't blank... will that statement still
>work? I login to the machine as a local admin and connect via the
>osql statement as the same ID as I logon to the machine with.
>Sue Hoegemeier <Sue_H@.nomail.please> wrote in message news:<np8vc0p2v2lfj8ke5mm0vf6f8vmrfg9plg@.4ax.com>. ..

MSDE password change for "sa"

Hello,
If I can get into the default instance of MSDE using a Windows
account (trusted connection) using 'osql -E' is it possible for me to
change the 'sa' SQL account if I don't know the current password? The
Windows account is a domain admin and local box admin if that matters.
Also, can anyone point me to a Q article that will give me a step
by step on how to upgrade from MSDE to SQL so I can get past this 2GB
limitation?
If anyone can answer these I am definitely buying beers!!
Thanks,
DanIf you can login as an admin on the box and the
builtin\administrators group login was not removed or
modified, you will be logged in as a member of the sysadmins
server role. As a sysadmin, you can execute the following to
change the sa password:
sp_password NULL, 'NewSaPassword', 'sa'
Upgrading to SQL Server isn't too bad. Run the SQL Server
installation CD. You will be asked if you want to upgrade
your existing instance or install a new one. Choose to
upgrade.
For more detailed steps on upgrading, you can refer to the
SQL Server Books Online topic:
How to perform an edition upgrade within SQL Server 2000
(Setup)
http://msdn.microsoft.com/library/en-us/howtosql/ht_install_1d7y.asp
-Sue
On 15 Jun 2004 17:41:11 -0700, dankennedy24@.hotmail.com (Dan
Kennedy) wrote:
>Hello,
> If I can get into the default instance of MSDE using a Windows
>account (trusted connection) using 'osql -E' is it possible for me to
>change the 'sa' SQL account if I don't know the current password? The
>Windows account is a domain admin and local box admin if that matters.
> Also, can anyone point me to a Q article that will give me a step
>by step on how to upgrade from MSDE to SQL so I can get past this 2GB
>limitation?
>If anyone can answer these I am definitely buying beers!!
>Thanks,
>Dan|||But the current "sa" password isn't blank... will that statement still
work? I login to the machine as a local admin and connect via the
osql statement as the same ID as I logon to the machine with.
Sue Hoegemeier <Sue_H@.nomail.please> wrote in message news:<np8vc0p2v2lfj8ke5mm0vf6f8vmrfg9plg@.4ax.com>...
> If you can login as an admin on the box and the
> builtin\administrators group login was not removed or
> modified, you will be logged in as a member of the sysadmins
> server role. As a sysadmin, you can execute the following to
> change the sa password:
> sp_password NULL, 'NewSaPassword', 'sa'
> Upgrading to SQL Server isn't too bad. Run the SQL Server
> installation CD. You will be asked if you want to upgrade
> your existing instance or install a new one. Choose to
> upgrade.
> For more detailed steps on upgrading, you can refer to the
> SQL Server Books Online topic:
> How to perform an edition upgrade within SQL Server 2000
> (Setup)
> http://msdn.microsoft.com/library/en-us/howtosql/ht_install_1d7y.asp
> -Sue
> On 15 Jun 2004 17:41:11 -0700, dankennedy24@.hotmail.com (Dan
> Kennedy) wrote:
> >Hello,
> > If I can get into the default instance of MSDE using a Windows
> >account (trusted connection) using 'osql -E' is it possible for me to
> >change the 'sa' SQL account if I don't know the current password? The
> >Windows account is a domain admin and local box admin if that matters.
> > Also, can anyone point me to a Q article that will give me a step
> >by step on how to upgrade from MSDE to SQL so I can get past this 2GB
> >limitation?
> >
> >If anyone can answer these I am definitely buying beers!!
> >
> >Thanks,
> >Dan|||Yes...it will still work. That's what you would use to reset any
password when you are logged in as a sysadmin. Just pass null for the
old password. It doesn't mean the password is null. It means you
aren't supplying the old password.
-Sue
On 16 Jun 2004 11:26:10 -0700, dankennedy24@.hotmail.com (Dan Kennedy)
wrote:
>But the current "sa" password isn't blank... will that statement still
>work? I login to the machine as a local admin and connect via the
>osql statement as the same ID as I logon to the machine with.
>Sue Hoegemeier <Sue_H@.nomail.please> wrote in message news:<np8vc0p2v2lfj8ke5mm0vf6f8vmrfg9plg@.4ax.com>...
>> If you can login as an admin on the box and the
>> builtin\administrators group login was not removed or
>> modified, you will be logged in as a member of the sysadmins
>> server role. As a sysadmin, you can execute the following to
>> change the sa password:
>> sp_password NULL, 'NewSaPassword', 'sa'
>> Upgrading to SQL Server isn't too bad. Run the SQL Server
>> installation CD. You will be asked if you want to upgrade
>> your existing instance or install a new one. Choose to
>> upgrade.
>> For more detailed steps on upgrading, you can refer to the
>> SQL Server Books Online topic:
>> How to perform an edition upgrade within SQL Server 2000
>> (Setup)
>> http://msdn.microsoft.com/library/en-us/howtosql/ht_install_1d7y.asp
>> -Sue
>> On 15 Jun 2004 17:41:11 -0700, dankennedy24@.hotmail.com (Dan
>> Kennedy) wrote:
>> >Hello,
>> > If I can get into the default instance of MSDE using a Windows
>> >account (trusted connection) using 'osql -E' is it possible for me to
>> >change the 'sa' SQL account if I don't know the current password? The
>> >Windows account is a domain admin and local box admin if that matters.
>> > Also, can anyone point me to a Q article that will give me a step
>> >by step on how to upgrade from MSDE to SQL so I can get past this 2GB
>> >limitation?
>> >
>> >If anyone can answer these I am definitely buying beers!!
>> >
>> >Thanks,
>> >Dan

MSDE password change for "sa"

Hello,
If I can get into the default instance of MSDE using a Windows
account (trusted connection) using 'osql -E' is it possible for me to
change the 'sa' SQL account if I don't know the current password? The
Windows account is a domain admin and local box admin if that matters.
Also, can anyone point me to a Q article that will give me a step
by step on how to upgrade from MSDE to SQL so I can get past this 2GB
limitation?
If anyone can answer these I am definitely buying beers!!
Thanks,
DanIf you can login as an admin on the box and the
builtin\administrators group login was not removed or
modified, you will be logged in as a member of the sysadmins
server role. As a sysadmin, you can execute the following to
change the sa password:
sp_password NULL, 'NewSaPassword', 'sa'
Upgrading to SQL Server isn't too bad. Run the SQL Server
installation CD. You will be asked if you want to upgrade
your existing instance or install a new one. Choose to
upgrade.
For more detailed steps on upgrading, you can refer to the
SQL Server Books Online topic:
How to perform an edition upgrade within SQL Server 2000
(Setup)
http://msdn.microsoft.com/library/e...nstall_1d7y.asp
-Sue
On 15 Jun 2004 17:41:11 -0700, dankennedy24@.hotmail.com (Dan
Kennedy) wrote:

>Hello,
> If I can get into the default instance of MSDE using a Windows
>account (trusted connection) using 'osql -E' is it possible for me to
>change the 'sa' SQL account if I don't know the current password? The
>Windows account is a domain admin and local box admin if that matters.
> Also, can anyone point me to a Q article that will give me a step
>by step on how to upgrade from MSDE to SQL so I can get past this 2GB
>limitation?
>If anyone can answer these I am definitely buying beers!!
>Thanks,
>Dan|||But the current "sa" password isn't blank... will that statement still
work? I login to the machine as a local admin and connect via the
osql statement as the same ID as I logon to the machine with.
Sue Hoegemeier <Sue_H@.nomail.please> wrote in message news:<np8vc0p2v2lfj8ke5mm0vf6f8vmrfg9p
lg@.4ax.com>...[vbcol=seagreen]
> If you can login as an admin on the box and the
> builtin\administrators group login was not removed or
> modified, you will be logged in as a member of the sysadmins
> server role. As a sysadmin, you can execute the following to
> change the sa password:
> sp_password NULL, 'NewSaPassword', 'sa'
> Upgrading to SQL Server isn't too bad. Run the SQL Server
> installation CD. You will be asked if you want to upgrade
> your existing instance or install a new one. Choose to
> upgrade.
> For more detailed steps on upgrading, you can refer to the
> SQL Server Books Online topic:
> How to perform an edition upgrade within SQL Server 2000
> (Setup)
> http://msdn.microsoft.com/library/e...nstall_1d7y.asp
> -Sue
> On 15 Jun 2004 17:41:11 -0700, dankennedy24@.hotmail.com (Dan
> Kennedy) wrote:
>|||Yes...it will still work. That's what you would use to reset any
password when you are logged in as a sysadmin. Just pass null for the
old password. It doesn't mean the password is null. It means you
aren't supplying the old password.
-Sue
On 16 Jun 2004 11:26:10 -0700, dankennedy24@.hotmail.com (Dan Kennedy)
wrote:
[vbcol=seagreen]
>But the current "sa" password isn't blank... will that statement still
>work? I login to the machine as a local admin and connect via the
>osql statement as the same ID as I logon to the machine with.
>Sue Hoegemeier <Sue_H@.nomail.please> wrote in message news:<np8vc0p2v2lfj8k
e5mm0vf6f8vmrfg9plg@.4ax.com>...

MSDE OSQL Utility

Dear all,
I have a question about the OSQL utility and the installation of MSDE. I
tried to install MSDE and SQL Server on the same machine. This should work
some people told me. As a result however my application is no longer showing
me the available servers on the machine. (laptop).
I removed everything and reinstalled only MSDE.
When I use the OSQL utility and enter OSQL -L it says there are no servers.
Should it not say which server is available.
Has anyone experienced this before. My system is no longer showing the
available servers. My application still seems to work because when I type in
the name of the server manually it is located.
How can I solve this problem.
regards,
Danny Gaethofs
hi Danny,
"Danny Gaethofs" <dangaet@.home.nl> ha scritto nel messaggio
news:uAGDu0P4EHA.2404@.TK2MSFTNGP14.phx.gbl
> Dear all,
> I have a question about the OSQL utility and the installation of
> MSDE. I tried to install MSDE and SQL Server on the same machine.
> This should work some people told me. As a result however my
> application is no longer showing me the available servers on the
> machine. (laptop).
> I removed everything and reinstalled only MSDE.
> When I use the OSQL utility and enter OSQL -L it says there are no
> servers. Should it not say which server is available.
> Has anyone experienced this before. My system is no longer showing the
> available servers. My application still seems to work because when I
> type in the name of the server manually it is located.
> How can I solve this problem.
> regards,
> Danny Gaethofs
MSDE installs by default disabling network protocols in order to minimize
external (malicious) attacks, preventing the installed instances to be
available for remote connections and disabling it's broadcast enlisting for
available SQL Server/MSDE instances...
to make it available for remote users and to enable server enlistment you
have to use Server Network Utility (svrnetcn.exe) and enable the
desired/preferred network protocol(s)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE OSQL command

Is there any books or website that will explain in depth about OSQL. Thanks.
Did you try the BOL ?
http://www.aspfaq.com/show.asp?id=2229
HTH, Jens Suessmeyer.
sql