sql server msde: Hi,
i have a msde installed on a Windows XP HE SP2 Computer. This Computer has a
3.06 GHz CPU with 1GB RAM!!! i am developing software with vb6 and go
through a odbc (JET 2.8) connection directly to the local installed msde. On
my notebook (WinXP PE SP2, 1.4 GHz, 512MB Ram) this software runs very fast
with about 15000 Addresses in my list.

On the 3.06GHz computer it takes about 4 seconds to open only the recordset
of the addresses?

Why is this computer so slow? does anyone know, how to get this msde faster
or are some other thinks to do, like driver update or something else?

thanx for your help and sorry for my english ;)

Alois

hi Alois,
[quoted text, click to view]

performance really are "individual" stuffs... :D
is the production machine dedicated for SQL Server use only or other
services/applications compete for resources on it (is Exchange running on
it)?
is the production machine hard disk(s) performing well? (or is it a slower
one then your?) is it fragmented?
is the production database logically fragmented?
are production database statistics updated?
are the data in both databases comparable or do you have 15000 rows in your
dev database and 15millions in the production on?
are you interacting with the production server locally or from remote
clients? are there network problems?
it's always difficult to have identical scenarios to compare...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
--------- remove DMO to reply

I would like to install MSDE in Windows XP Professional. When I tried
to install it gave me an error A strong SA password is required for
security reasons. Please use SAPWD switch
I do not know how it handle this error if you can please let me how to
install in XP.

Step by Step process.

Thanking You


Your's Truly

Raj

hi Raj,
[quoted text, click to view]
Setup.exe is a boostrap intaller for MSDE and accepts parameters you can
provide at the command line as long as in a companion .Ini file..
at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
you can find the list of all supported parameters...
please open a DOS command window and navigate to the folder hosting the
setup.exe file...
there you can run setup.exe with all the parameters of your choice..
- usually you have to provide the SAPWD parameter to specify a strong
password for the "sa" builtin login in order to protect it from both
internal and external attacks..
specify then
SAPWD=your_strong_password
- additional parameters let you specify if you want a named instance or a
default instance.... specify
INSTANCENAME=your_instance_name
if you want a named instance...
- another parameter let you specify if you want to allow remote connections
from other PCs in your lan to your MSDE instance.. specify
DISABLENETWORKPROTOCOLS=0
if you need this feature...
- by default, MSDE is installed allowing only WindowsNT authenticated
connections and preventing standard SQL Server authenticated ones.. more on
this at http://support.microsoft.com/default.aspx?scid=kb;en-us;325022
you can specify
SECURITYMODE=SQL
to allow mixed mode security, thus allowing both WInNT integrated security
and standard SQL Server authenticated connections..
- the final important parameter is
/L*v "c:\msdelog.txt"
where you will allow verbose logging of the installation process, resulting
in a text file of about 2mb for a successfull installation you can inspect,
in case of problems, for
RETURN VALUE 3
entries... about 10 lines before each entry some (sometime cryptic)
description of the problwm will be reported..

so, if you like to install a "named instace" named "Raj" with mixed security
and enabled network protocols for remote connections you can run setup.exe
boostrap installer providing all parameters as
c:\..\>setup.exe /qb INSTANCENAME=Raj SECURITYMODE=SQL
DISABLENETWORKPROTOCOLS=0 SAPWD=your_strong_password /L*v "c:\msdelog.txt"

you can later manage your installed instance via the native character tool
oSql.exe as described at
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q325003 or use a
third party tool, both commercial or free, like the ones listed at
http://www.microsoft.com/sql/msde/partners/ or
http://www.aspfaq.com/show.asp?id=2442... google for further..
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
--------- remove DMO to reply