Add Resource to Category

[James]

Hi,

How do I associate a user with a category in Project Server if I want to
create the entries directly in the tables in the Project Server SQL
database? I'm confused by the relationship between the various tables. I
previously did something similar for projects, and it was simply a case of
adding a row to MSP_WEB_SECURITY_OBJECTS but it seems to a bit more
complicated for a user and involves the MSP_WEB_SECURITY_SP_CAT_RELATIONS
table.

Am I on the right lines?

Regards,

James

 

[Rolly Perreaux]

Hi,

How do I associate a user with a category in Project Server if I want to
create the entries directly in the tables in the Project Server SQL
database? I'm confused by the relationship between the various tables. I
previously did something similar for projects, and it was simply a case of
adding a row to MSP_WEB_SECURITY_OBJECTS but it seems to a bit more
complicated for a user and involves the MSP_WEB_SECURITY_SP_CAT_RELATIONS
table.

Am I on the right lines?

Regards,

James

Hi James,

There is absolutely nothing to prevent you from making modifications to
the Project Server SQL database. But a friendly word of advice.

Don't do it!

You will lose your support from Microsoft PSS if you (for lack of a
better word) hack into the database directly.

Here's a little story that happen to a customer of mine...

A few years back I had a customer that had a developer on-staff that was
some-what of a SQL guru. He said that it was no problem directly making
changes to the database through the use of SQL scripts. So he was given
approval from his manager to do that. Afterall he was a SQL guru <g>

Well when the database was corrupted because said guru didn't know the
schema and table/view relationships, they placed a call to Microsoft
PSS. To their surprise they were essentially told that they have voided
their support because of what the guru did.

So guess what they had to do? Yup you guessed right.
They had to reinstall and rebuild the entire enterprise application.

Moral of the story
Just because you think you can do something, doesn't mean that you
should. And if you do, expect serious consequences.

Good Luck!

--
Rolly Perreaux
Project Server Trainer/Consultant

IT Summit Series
Advanced Microsoft Technology Training
http://www.itsummitseries.com

 

[Gary L. Chefetz [MVP]]

James:

The following link will give you a little guidance. It shows how to do this
with projects, which you can then alter for resources. Ask questions like
this at microsoft.public.project.developer for better answers.

 

[Gary L. Chefetz [MVP]]

It helps to post the link:

http://www.projectserverexperts.com/Shared Documents/ChangeSecurityCategories.htm

 

[Dale Howard [MVP]]

James --

I'm curious why you don't want to use the default features of Project Server
to add a resource to a Category. Here are the steps required:

1. Log into PWA with administrator permissions
2. Click Admin - Manage Security
3. Select the Category and then click the Modify Category button
4. In the Users and groups section, add the user to the Category
5. Click the Save Changes button

Hope this helps.

 

[Brian K - Project MVP]

There is absolutely nothing to prevent you from making modifications to
the Project Server SQL database. But a friendly word of advice.

Don't do it!

You will lose your support from Microsoft PSS if you (for lack of a
better word) hack into the database directly.

This is not 100% accurate. I have spoken with PSS about this and it would
depend completely on what you did in the database. It is not a blanket "if
you edited the database you are unsupported". They would have to look at
what you changed and if what you changed can be fixed if it was a problem.

In many cases editing the database is not only supported but suggested.
Extending the OLAP cube is a perfect example. PDS extentions are
encouraged by MS and they almost always directly edit the database. The
integrations with SAP and Peoplesoft that have been written by several
partners all make direct edits to the database.

So while it is possible that you could make changes to the database that
could cause MS to not support you in certain ways it is not correct to say
that any edit could cause you to stop supporting you. Also, an edit that
might cause MS to stop supporting you in certain areas of the product
would not necesarily stop them from supporting you with other parts of the
product.

 

[Rolly Perreaux]

This is not 100% accurate. I have spoken with PSS about this and it would
depend completely on what you did in the database. It is not a blanket "if
you edited the database you are unsupported". They would have to look at
what you changed and if what you changed can be fixed if it was a problem.

In many cases editing the database is not only supported but suggested.
Extending the OLAP cube is a perfect example. PDS extentions are
encouraged by MS and they almost always directly edit the database. The
integrations with SAP and Peoplesoft that have been written by several
partners all make direct edits to the database.

So while it is possible that you could make changes to the database that
could cause MS to not support you in certain ways it is not correct to say
that any edit could cause you to stop supporting you. Also, an edit that
might cause MS to stop supporting you in certain areas of the product
would not necesarily stop them from supporting you with other parts of the
product.

Hang on a sec Brian

When you say, "...editing the database is not only supported but
suggested", that not entirely true.

Your examples of extending the OLAP cube, PDS extensions and the
integrations with SAP and Peoplesoft is not the same thing that James is
trying to do.

Extending the OLAP cube is fully supported by Microsoft
http://www.microsoft.com/downloads/details.aspx?FamilyId=CEED7E60-C83F-
4B1D-980F-8298C0911E1E&displaylang=en OR http://tinyurl.com/ayn3n

PDS Extensions...Fully supported
http://www.microsoft.com/downloads/details.aspx?FamilyId=3C09FCB9-A9DC-
424B-8158-645278DBA124&displaylang=en OR http://tinyurl.com/7vozc

SAP Connector...Fully supported
http://www.microsoft.com/downloads/details.aspx?FamilyID=7E0EB648-9EEF-
4D53-88A8-3D7E6B9152E9&displaylang=en OR http://tinyurl.com/av793

Any Microsoft Partner that writes code for a Project Server addition
follows the Project 2003 Software Development Kit (SDK). That is if they
want their solution to be Microsoft Certified.
http://www.microsoft.com/downloads/details.aspx?familyid=4D2ABC8C-8BCA-
4DB9-8753-178C0D3099C5&displaylang=en OR http://tinyurl.com/bo6ro

Anyway...
The point that I'm trying to make is there is a BIG difference between
using Microsoft supported code or a Partner writing code for an
certified application that may add/change/delete the project database
AND
Writing a home-grown SQL script to add/change/delete the project
database. A Very Big Difference!!

I've had first hand experience with a client that hacked the SQL
database and trust me on this Brian, this will void your support
warranty with Microsoft.

--
Rolly Perreaux
Project Server Trainer/Consultant

IT Summit Series
Advanced Microsoft Technology Training
http://www.itsummitseries.com