How to tell which service pack of SQLCE is installed on the desktop

The title about says it all. For merge replication, I need to make sure the
service packs match up between SQL2000 and SQLCE. How do I tell which SQLCE
version is in?
IIRC check the folder C:\Program Files\Microsoft SQL Server CE
2.0\Redist\Server, the latest one should be there.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:esst%23$86FHA.1864@.TK2MSFTNGP12.phx.gbl...
> The title about says it all. For merge replication, I need to make sure
> the service packs match up between SQL2000 and SQLCE. How do I tell which
> SQLCE version is in?
>
|||actually this is good up to sp2. After sp 2 you need to check the versions
of the binaries in C:\Program Files\Microsoft SQL Server CE 2.0\Server\
For sp 4 they are
sscesa20.dll 2.00.7331.0
sscerp20.dll 2.00.7331.0
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:esst%23$86FHA.1864@.TK2MSFTNGP12.phx.gbl...
> The title about says it all. For merge replication, I need to make sure
> the service packs match up between SQL2000 and SQLCE. How do I tell which
> SQLCE version is in?
>
|||Thanks Hilary; that's helpful.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uLeiiSD7FHA.1032@.TK2MSFTNGP11.phx.gbl...
> actually this is good up to sp2. After sp 2 you need to check the versions
> of the binaries in C:\Program Files\Microsoft SQL Server CE 2.0\Server\
> For sp 4 they are
> sscesa20.dll 2.00.7331.0
> sscerp20.dll 2.00.7331.0
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
> news:esst%23$86FHA.1864@.TK2MSFTNGP12.phx.gbl...
>

How to summerize Calculated Member in SQL2000

I have created a virtual cube in SQL2000. Then, I have generated a
Calculated Member. When I did rollup into a higher level, SQL2000 did
re-calculate the member. However, I want to summerize the Calculated
member. The Solve Order could not be worked in this situation since a
measure, which is used to generate the Calculate Member, will be
available only in the lowerest level of the dimension. Please help me!Anote Sangkunakupt (anote_un@.hotmail.com) writes:
> I have created a virtual cube in SQL2000. Then, I have generated a
> Calculated Member. When I did rollup into a higher level, SQL2000 did
> re-calculate the member. However, I want to summerize the Calculated
> member. The Solve Order could not be worked in this situation since a
> measure, which is used to generate the Calculate Member, will be
> available only in the lowerest level of the dimension. Please help me!

You might get better response in a group like
microsoft.sqlserver.public.olap.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

How to stop the TOP clause being added to query when defining a view

Hi

I've just switched over to SQL2005 Server Management Studio although most of my databases are SQL2000. Apart from noticing that everything takes longer than with Enterprise Manager I have one specific problem.

When I save a view that I have created in the visual toolbox it gets saved with the TOP 100 Percent clause added, even if I take the clause out of the SQL statement it gets put right back in when I save it. This is causing an application which worked fine before to fail with the error "cannot update a view with TOP clause"

Anyone any ideas how I can stop this clause being added?

Many thanks

? Hi Ian, >>Anyone any ideas how I can stop this clause being added? Take out the ORDER BY clause as well. An ORDER BY in a view is only allowed if there is also a TOP clause. Also, the only guaranteed effect the ORDER BY in the view will have is to define what rows to select and what rows to discard for satisfying the TOP requirement. No guarantee is made wrt the order of rows returned, unless you add an ORDER BY to the final SELECT statement you use to query your data. SQL Server 2000 did, usually, return the rows in the order that was specified in the view. New optimizing techniques in SQL Server 2005 have changed that behaviour. -- Hugo Kornelis, SQL Server MVP