Problems with 'Modify Database' and SQL Server 2005

sambendayan

unread,

May 1, 2007, 1:00:14 PM5/1/07

to

Greetings,

I am trying to compare a PowerDesigner Physical data model
with a Microsoft SQL Server 2005 database, and I'm having
several issues. Basically, PowerDesigner is reporting a
bunch of false differences under several different
circumstances. Below is the list:

1. Any column default values that are NOT strings are being
modified. PowerDesigner is adding tilde marks (~) before
and after the values. This makes them show up as
differences in the compare window even though the values are
the same. I got around this by manually adding the tilde
marks myself to the model, but this is messy. Is there a
way to get PowerDesigner to not add these tilde marks?
2. I have the same problem as above, but with parentheses in
check constraints. Sometimes PowerDesigner puts parentheses
around numbers in check constraints and this causes them to
be reported as false differences. Is there any way to get
PowerDesigner to not add these parentheses?
3. Some table columns and constraint names are showing up as
different when they are EXACTLY the same (I even compared
the white spaces within them). Why is this and how to solve
it?
4. Some foreign key constraints in the database are set to
CASCADE on DELETE, but the compare window is showing them to
RESTRICT on DELETE, so they are reporting false differences.
How to solve this?
5. The VARCHAR(MAX) datatype (which is new to SQL2005) is
incorrectly being reported as 'varchar' in the compare
window. This is generating false differences. How to solve
this?
6. Some Unique Keys are being reporting as missing in the
database when they actually exist.
7. Finally, there seems to be great inconsistency as to how
PowerDesigner treats Business Rules versus Check
Constraints. I have many Business Rules set up and bound to
tables or columns and sometimes it finds them in the
database where sometimes it doesn't.

Any help/suggestions that anyone has on the above would be
greatly appreciated. This is causing me major pain right
now since the compare utility is not of much use when it
reports all these false differences.

Thanks,

Sam Bendayan
sam.be...@gmail.com

sambendayan

unread,

May 2, 2007, 12:02:00 PM5/2/07

to

I have some more issues to add to the list:

1. When comparing triggers, the trigger event
(insert/update/delete) is not coming through from the
database side.
2. Business rules that are bound to the triggers don't show
up in the compare window.

Mike Nicewarner

unread,

May 9, 2007, 9:10:25 PM5/9/07

to

Did you specify the version/build of PowerDesigner that you are using?

--
Mike Nicewarner [TeamSybase]
http://www.datamodel.org
mike[at]datamodel[dot]org (can you figure what to change?)
Sybase product enhancement requests:
http://www.isug.com/cgi-bin/ISUG2/submit_enhancement

sambendayan

unread,

May 10, 2007, 8:28:35 AM5/10/07

to

Version 12.1.0.1913.

SB

sambendayan

unread,

Jun 1, 2007, 3:20:18 PM6/1/07

to

Anyone have any ideas on this?

SB

Mike Nicewarner

unread,

Jun 6, 2007, 1:54:34 AM6/6/07

to

There are newer EBFs available from Sybase. It never hurts to check
that avenue out.
I don't have a SQL Server database to test with, so I'm not as helpful
as I would want to be. Sorry.
My guess is that the PD Reverse engineer code used against SQL Server
has a bug or two. You might be able to correct this in the XDB file,
but I'm not certain. When I see this sort of thing, I update to the
latest EBF, and if that doesn't fix it I call tech support.

sambendayan

unread,

Dec 11, 2007, 11:42:21 AM12/11/07

to

Sorry, what's an EBF?

Thanks,
SB

Mike Nicewarner

unread,

Dec 13, 2007, 11:17:23 PM12/13/07

to

EBF = Emergency Bug Fix
Go to the Sybase web site, select the Support & Downloads, then the
EBF/Maintenance link.
You can find everything you need there.