Do I trust what my SMS agents are telling me?

This XML update that was originally released Oct 10th and then updated Oct
19th has got me .
I have roughly 600 SMS clients, 150 of which would be XP machines and 450
Windows 2000.
Right now I have a little over 400 SMS clients (a mix of XP and 2000)
requesting 924191 which SMS describes as a Security update for Windows (but
updates the XML parser and Core Services), and another 532 clients
requesting 925672, described as MSXML4.0 SP2 Security update.
Obviously, I've got a lot of clients requesting both (or requesting the same
update under two different names'). Is this simply because they have
multiple versions of these XML components on their machines, all of which
need updating? These updates aren't going to stomp on each other? Should I
be deploying both?
Advice for an SMS admin (not an XML guy) appreciated.
SMS 2003 SP1 on W2K3 SP1> Obviously, I've got a lot of clients requesting both (or requesting the
> same update under two different names').
The update released for MSXML3 was seperate from the update released for
MSXML4, even though the issue that each of these updates fixed was the same.

> Is this simply because they have multiple versions of these XML components
> on their machines, all of which need updating?
Yes

>These updates aren't going to stomp on each other? Should I be deploying
>both?
No they are not going to stomp on each other, yes, deploy both.
"Phil McNeill" <philmcneill@.NOSPAM4MEhydroottawa.com> wrote in message
news:uhwgP$G%23GHA.1224@.TK2MSFTNGP04.phx.gbl...
> This XML update that was originally released Oct 10th and then updated Oct
> 19th has got me .
> I have roughly 600 SMS clients, 150 of which would be XP machines and 450
> Windows 2000.
> Right now I have a little over 400 SMS clients (a mix of XP and 2000)
> requesting 924191 which SMS describes as a Security update for Windows
> (but updates the XML parser and Core Services), and another 532 clients
> requesting 925672, described as MSXML4.0 SP2 Security update.
> Obviously, I've got a lot of clients requesting both (or requesting the
> same update under two different names'). Is this simply because they
> have multiple versions of these XML components on their machines, all of
> which need updating? These updates aren't going to stomp on each other?
> Should I be deploying both?
> Advice for an SMS admin (not an XML guy) appreciated.
> SMS 2003 SP1 on W2K3 SP1
>
>|||Thanks for the reply Alex. I was fairly sure that was the case, but already
deployed to my test group prior to the Oct 19th update that added updates
for Windows 2000. I'll deploy the additional updates to that group and see
how it goes.
Thanks again,
Phil
"Alex Krawarik[MSFT]" <alexkr@.microsoft.com> wrote in message
news:eC2DC0I%23GHA.3456@.TK2MSFTNGP02.phx.gbl...
> The update released for MSXML3 was seperate from the update released for
> MSXML4, even though the issue that each of these updates fixed was the
> same.
>
> Yes
>
> No they are not going to stomp on each other, yes, deploy both.
>

Distributing SQL2000 Database

Is it possible to encrypt a database so that clients may
not view the table structure, relationships,triggers,
functions, etc.? Objective is to protect the back-end
design from being exposed.You can encrypt sps, udf and triggers, but I don't think you can select
without seeing the structure
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Mir Zaman" <anonymous@.discussions.microsoft.com> wrote in message
news:9bc601c3b739$dfbed3f0$a601280a@.phx.gbl...
> Is it possible to encrypt a database so that clients may
> not view the table structure, relationships,triggers,
> functions, etc.? Objective is to protect the back-end
> design from being exposed.

Distributing Setup files SQL Server 2005

Hi

I would like to know, if it is at all possible for Setup files of SQL Server 2005 to be distributed. We have clients who currently use our software which makes use SQL Server 2000. We are looking ahead at distributing our new version with SQL Server 2005 and would like create an Installation package that will upgrade the database engine to the Workgroup or Enterprise editions of SQL Server 2005. Are there any suggestions around this topic, we are looking at ways in making this task of upgrading the engine as streamlined and automated for our Client. Please include advise with regards to licensing.

cheers

Kevin

Here are a couple of resources that should point you in the 'right' direction:

Deploy Database with MSI
http://msdn.microsoft.com/msdnmag/issues/04/09/customdatabaseinstaller/

Deploy Database with Application

http://www.codeproject.com/useritems/Deploy_your_database.asp

distributing reports to multiple report servers

Hi,
I am trying to figure out how to package and deploy reports to multiple
report servers. We have 200+ clients, and are trying to switch over to
report server, but I can't find any documentation about deploying reports
outside of an organization.
To clarify a little, new releases come out quarterly, and are installed with
an msi installer, and we would like to be able to distribute reports with
our current process.
any help would be greatly appreciated...
Thanks
CraigCraig,
There is a sample script that shows how to automate the publishing of
the reports. Is this the kind of thing you're looking for?
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSAMPLES/htm/rss_sampleapps_v1_1apd.asp
Your msi installer could land the report rdl and collect the variables
necessary for running a script similar to this.
Andy Potter|||That should do just fine =)
Thanks,
Craig
"Potter" <drewpotter@.gmail.com> wrote in message
news:1135889173.574650.189300@.g43g2000cwa.googlegroups.com...
> Craig,
> There is a sample script that shows how to automate the publishing of
> the reports. Is this the kind of thing you're looking for?
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSAMPLES/htm/rss_sampleapps_v1_1apd.asp
> Your msi installer could land the report rdl and collect the variables
> necessary for running a script similar to this.
> Andy Potter
>|||To help automate the script generation have a look at
Reporting Services Scripter
http://www.sqldbatips.com/showarticle.asp?ID=62
--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Craig L" <craig.lonsbury@.diamondmunicipal.com> wrote in message
news:eShO$RLDGHA.516@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I am trying to figure out how to package and deploy reports to multiple
> report servers. We have 200+ clients, and are trying to switch over to
> report server, but I can't find any documentation about deploying reports
> outside of an organization.
> To clarify a little, new releases come out quarterly, and are installed
> with an msi installer, and we would like to be able to distribute reports
> with our current process.
> any help would be greatly appreciated...
> Thanks
> Craig
>

distributing data to client sites...

We have a large SQL database, and we need to send out updated records to many clients' sites which are not connected.

We currently have a tool which looks at the audit log of changes we made, creates a file based on this, which is then emailed to our clients. They then run a tool we created to remerge the changes.

I suspect SQL server replication might make all this possible. Am I right? Can SQL server produce a file automatically which can be applied to a remote database to update the tables as appropriate? From looking at some replication stuff it looks to me like you have to have the servers on the same network.Not necessarily. But your sysadmin needs to know his/her stuff.