Rolly said:
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.
From a supportability standpoint there is actually no difference between a
TSQL statement I write myself and a Partner written Windows Certified
application that makes edits to the db. Actually, in the case of a simple
SQL statement I used to try something they will talk to me and help me out
but if it is an SP or a third party app (even one written by a partner and
certified) they will still tell you to go talk to the people that wrote
that. PSS does not support third party apps. This includes ANY
modification to the OLAP extender\SAP solution starter code from MSDN. If
you do not edit any of the code they will support that but as soon as you
start editing code you start to venture out into nomans land.
What Im trying to say is that not every modification to the database will
void your support with MS. There are some that might stop them from being
able to support certain aspects of the product and there are obviously
changes that can be made that can cause them to stop supporting you
completely from what your customer says. Was this customer working with
the Project Server database or another product.
I just spoke with one of the leads in PSS for Project\Project Server and
they said that not every edit would be a problem.
They gave me permission to share this info with the public groups:
"We do not support modifying the database structure outside of the SDK
samples that we provide (such as the OLAP cube extensions)"
"We do not trouble shoot custom code – we will however assist with VBA
syntax if the customer can narrow down the problem area to 15 lines of
code."
"We do not recommend that a user go into the backend database and modify
data – however we will try to help the customer recover on a best effort
basis. "
"We do not support troubleshooting database issues when custom code has
made the modifications. We do recommend that customer use PDS methods to
write to the database. "
___
I just want to make sure that this is clear to everyone that just
modifying data in the database will not automatically void any warrenties
or sever any contracts with PSS. It may cause them to say that they cannot
help you with a specific problem caused by that editing but they will
still support you on other issues with that product and in some cases they
may be able to help you with your problem. It would depend on what kind of
edit you made and to what tables\fields.
