determine the SP level of a client install?

Hello,
How can I tell what service pack has been installed on a local (non-server) client installation of SQL Server 2000?
I'd appreciate any feedback
Thanks,
John
Have you looked at Help | About within Query Analyzer?
--=20
Keith
"John P" <John P@.discussions.microsoft.com> wrote in message =
news:6A79F645-CBF8-4123-8FC8-CC0A8952A7F6@.microsoft.com...
> Hello,
>=20
> How can I tell what service pack has been installed on a local =
(non-server) client installation of SQL Server 2000?
>=20
> I'd appreciate any feedback
>=20
> Thanks,
>=20
> John
|||ahh...why didn't I think of that?! I tried that in Enterprise Manager but noticed it was MMC not SQL so I gave up!
Thanks Keith!
"Keith Kratochvil" wrote:

> Have you looked at Help | About within Query Analyzer?
> --
> Keith
>
> "John P" <John P@.discussions.microsoft.com> wrote in message news:6A79F645-CBF8-4123-8FC8-CC0A8952A7F6@.microsoft.com...
>
|||Yeah, Help | About within EM gives information about MMC, not about the =
specific snap in.
--=20
Keith
"John P" <JohnP@.discussions.microsoft.com> wrote in message =
news:62578D1D-7A60-440B-99A4-5B8B774A6E73@.microsoft.com...
> ahh...why didn't I think of that?! I tried that in Enterprise Manager =
but noticed it was MMC not SQL so I gave up![vbcol=seagreen]
>=20
> Thanks Keith!
>=20
> "Keith Kratochvil" wrote:
>=20
news:6A79F645-CBF8-4123-8FC8-CC0A8952A7F6@.microsoft.com...[vbcol=seagreen]
(non-server) client installation of SQL Server 2000?[vbcol=seagreen]

Determine ServicePack level

Hello,
how one can determine ServicePack level of SQL Server 2000 installation? I
would like to do this without server running (not neccessary, but
preferably).
Nice day
Ondra.Have a look here:
http://vyaskn.tripod.com/sqlsps.htm
--
Andrew J. Kelly
SQL Server MVP
"Ondrej Sevecek" <ondra@.sevecek.com> wrote in message
news:u2F33DZaDHA.1832@.TK2MSFTNGP09.phx.gbl...
> Hello,
> how one can determine ServicePack level of SQL Server 2000 installation?
I
> would like to do this without server running (not neccessary, but
> preferably).
> Nice day
> Ondra.
>
>|||Ondra,
Without the SQL Server running? May be you can check the SQL Server errorlog
(C:\Program Files\Microsoft SQL Server\<instancename>\LOG).The first section
is the output of @.@.version.The numbers in the first line indicate the
service pack level.
- 8.00.760(SP3/SP3a)
- 8.00.534 (SP2)
- 8.00.384 (SP1)
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Ondrej Sevecek" <ondra@.sevecek.com> wrote in message
news:u2F33DZaDHA.1832@.TK2MSFTNGP09.phx.gbl...
> Hello,
> how one can determine ServicePack level of SQL Server 2000 installation?
I
> would like to do this without server running (not neccessary, but
> preferably).
> Nice day
> Ondra.
>
>

Design to accomodate entity based schema versioning

in simple words it's about versioning at record level.

Example

TableEmployee - EmployeeId, EmployeeName,
EmployeeAddress, DepartmentId,
TableDesignationMap - EmployeeId, DesignationId, EffectiveDate,
validity
TableDepartment - DepartmentId, Department
TableDesignation - DesignationId, designation

Via Modify-Employee-Details screen following are editable
EmoyeeName
EmployeeAddress
Department
Designation

this screen should allow user to navigate through changes history.
Example :

Version -1
EmoyeeName John Smith
EmployeeAddress 60 NewYork
Department Accounts
Designation Accountant

Version -2
EmoyeeName John Smith
EmployeeAddress 60 NewYork
Department Accounts
Designation Chief Accountant - changed

Version -3
EmoyeeName John Smith
EmployeeAddress 60 NewYork
Department Sales - changed
Designation Marketing Manager - changed

Question :
What is the best proposed database design for maintaining history
records bound with version and retrieval technique

Best Regards
SasankaSasanka Pinidiya (pinidiya@.yahoo.com) writes:
> in simple words it's about versioning at record level.
> Example
> TableEmployee - EmployeeId, EmployeeName,
> EmployeeAddress, DepartmentId,
> TableDesignationMap - EmployeeId, DesignationId, EffectiveDate,
> validity
> TableDepartment - DepartmentId, Department
> TableDesignation - DesignationId, designation
> Via Modify-Employee-Details screen following are editable
> EmoyeeName
> EmployeeAddress
> Department
> Designation
>...
> Question :
> What is the best proposed database design for maintaining history
> records bound with version and retrieval technique

There are several techniques, and which is the best depends on the actual
business case.

One techniques which makes it very simple to retrieve the data at a
certain date, is store one version each day. Clearly, this technique
is not appropriate here. This technique is good for things that changes
about daily as for instance currency prices.

Another technique is store key, date and then what changed. But this
makes is difficult to retrieve the complete information at a given point
in time.

So the best technique seems to be to have a table with the same columns
as the base table, and with a datetime column added to hold the time
of the change.

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

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

Design Question: Dimension made up of several Tables, skip one Level in one Hierarchy

Greetings!

I wonder if someone can give a hint such a design task:

I have a dimension that consists of several tables each chained 1-n to the next one. "Country, City, Shop" maybe. Within this dimension I build a hierarchy down this path, and it works perfectly fine. My measures add up along this path, all good.

Now, say, each Shop has a property describing the location (lets name it LocationSurroundings), like "HighStreet" or "Mall" or "Suburb".

I'd like to get a 2nd look upon this dimension, with the levels being "Country, LocationSurroundings, Shop". I do want to skip City for this view, I want to able to see all Shops that are situated in Malls for a country.

If City was part of that view, I would always get totals to city levels, but not be able to compare shops from different citys in the same country. Is there a solution to this? I need the city property in some way to connect shop to country, but I do not want it to be visible or to generate subtotals at this level...

Thanks for your ideas!

Ralf

Hello. I am not sure about the problem here. If you are using SSAS2005 you have both attribute hierarchies, with each attribute not belonging to a hierarchy,and the user hierarchies, which are the ones you describe like Country-City-Shop.

Could you not simply add Locationsurrondings as an attribute(attribute dimension) in the dimension?

Regards

Thomas Ivarsson

|||

Hi Ralf,

Please expand a bit on your problem.

As I see it you can just make a second hierarchy and make city a hidden level. In the DIM designer, create the complete hierarchy (including city), choose the hierarchy, choose the level (city) right-mouse > properties > Visible - false

But when you are talking about a view, you mean a data source view or a SQL-view.

Kind regards,

Johan Blad (also somewhere in Europe)

|||

Thanks both of you, I got it working as I need.

What I meant to acomplish were really 2 goals:

a) A hierarchy with a level missing. This can be done by chaining together the attributes as they need to be, but on the hierarchy you just leave out the one you do not want. SSAS is smart enough to understand that. I now got 2 hierarchies in this dimension, one that includes all levels and another one that skips some levels.

b) Include another attribute (here: the shop area description) into the hierarchy. This is not possible, as it has no relations. I solved that by just making it an attribute, as suggested. Works fine!

That is solved. Thanks VERY MUCH.

But another question that now came up:

I have a self-referencing dimension table (a) that contains a hierarchy of levels. The lowest level items are NOT the ones that join to the fact table... the lowest level joins to another table (b) where a lot of attributes for a complete different type or real life object are listed, and this table finally joins the fact data (c).

What I mean: Imagine a company employee hierarchy down from manager to department leaders to regular employees (that is the hierarchy, a). Now each employee has several accounts to work with (stored in the account table, b). Finally, these accounts are referenced in the fact table c.

I would not want to make this one table, an employee is a complete different thing than an account with a different set of attributes.

Whatever I try, I cannot build a dimension that contains a self-referencing table AND a normal one... is that so? Is there a way to do that? How? What? Where?

|||

As far as I know, you cannot blend a parent-child and a normal dimension.

One option would be to use a referenced dimension relationship (from "fact table c" to account to employee).

Another option would be creating a fact-less fact table that shows the relationships between employees and accounts. So employee and accounts are related to new fact EmployeeAccounts. Then create a many-to-many dimension relationship from your "fact table c" to Employees.

Third (and simplest) option - just add both dimension keys to the fact.

None of these will give you a single dimension representing Employees and accounts. But, if they are two different entities, is that really what you want to do?