Re: Getting an absolutely up to date version of MSDE
From: Andrea Montanari (andrea.sqlDMO_at_virgilio.it)
Date: 12/13/04
- Next message: Andrea Montanari: "Re: For Andrea...Install MSDE w/ MSDE Depl.Toolkit. cont."
- Previous message: Danny Gaethofs: "MSDE OSQL Utility"
- In reply to: John Morgan: "Re: Getting an absolutely up to date version of MSDE"
- Next in thread: John Morgan: "Re: Getting an absolutely up to date version of MSDE"
- Reply: John Morgan: "Re: Getting an absolutely up to date version of MSDE"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 13 Dec 2004 13:05:01 +0100
hi John,
"John Morgan" <jfm@XXwoodlander.co.uk> ha scritto nel messaggio
news:tf8pr05q6hueu7t4g4v7vrc8n424naru4h@4ax.com
>
> 1. The real reason for updating is that I have online SQL Server
> databases on an ISP's SQL Server. Within the last fornight the ISP
> has suddenly updated the security arrangements for its SQL Server and
> now allows only 'access through port 1433'. This has meant that my
> Enterprise Manager connection does not now work (has worked splendidly
> for 12 months) and I cannot access my online databases using
> Enterprise Manager. The ISP have given me simple instructions to set
> up an alias using Network Client (on port 1433) and to register that
> connection using Enterprise Manager but their instructions do not
> work. They say that this is because my MSDE has not been upgraded to
> SP3. Does this make sense to you?
actually not... your MSDE instance (which I consider a local instance on
your private pc) has nothing to do with your ISP's servers and services...
and as MSDE does not provide Enterprise Manager, the entire story is even
more obscure :)
port 1433 (TCP/IP) is the standard IANA assigned port to Microsoft for SQL
Server and, usually, default instances always listen on it, where named
instances required UDP 1434 port for the SQL Server Resolution Service that
will listen on it for incoming requests, redirecting them to the appropriate
dynamically assigned port (actually letting the remote MDAC client stack be
aware of the correct port) if dynamic port setting is enabled... if static
port has been set for an SQL Server(/MSDE) instance, that information must
be usually provided setting a local Alias (using the Client Network Utility
[cliconfg.exe]) on the (each) remote client or providing the correct port in
the connections string...
for Internet based installations/providers, I strongly advice using tools
working over standard 80 port using web based tools like
http://www.mylittletools.net/scripts/en/mla_sql/ ... a lite free version is
available too... or Web Data Administrator
(http://www.microsoft.com/downloads/details.aspx?FamilyId=C039A798-C57A-419E
-ACBC-2A332CB7F959&displaylang=en) but this last Microsoft tool is not very
usefull :(
> 2. I am not sure I understand you fully, can you confirm that
> sql2kdesksp3.exe installs a complete version of MSDE or is it a means
> of updating an existing instance of MSDE to SP3a ?
both :D
-- Andrea Montanari (Microsoft MVP - SQL Server) http://www.asql.biz/DbaMgr.shtm http://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
- Next message: Andrea Montanari: "Re: For Andrea...Install MSDE w/ MSDE Depl.Toolkit. cont."
- Previous message: Danny Gaethofs: "MSDE OSQL Utility"
- In reply to: John Morgan: "Re: Getting an absolutely up to date version of MSDE"
- Next in thread: John Morgan: "Re: Getting an absolutely up to date version of MSDE"
- Reply: John Morgan: "Re: Getting an absolutely up to date version of MSDE"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
