Issues when importing Structures into DDT


Author
Message
Melvin Xuereb
Melvin Xuereb
StrataFrame Novice (103 reputation)StrataFrame Novice (103 reputation)StrataFrame Novice (103 reputation)StrataFrame Novice (103 reputation)StrataFrame Novice (103 reputation)StrataFrame Novice (103 reputation)StrataFrame Novice (103 reputation)StrataFrame Novice (103 reputation)StrataFrame Novice (103 reputation)
Group: Forum Members
Posts: 29, Visits: 128
Hi Ivan,

We are importing from an SQL Server 2005. To correct my previous post, the data type of the columns which are being imported are 'numeric' and not decimal. Could this be the reason?

Thanks,
Melvin
Ivan George Borges
Ivan George Borges
Strategic Support Team Member (3.5K reputation)Strategic Support Team Member (3.5K reputation)Strategic Support Team Member (3.5K reputation)Strategic Support Team Member (3.5K reputation)Strategic Support Team Member (3.5K reputation)Strategic Support Team Member (3.5K reputation)Strategic Support Team Member (3.5K reputation)Strategic Support Team Member (3.5K reputation)Strategic Support Team Member (3.5K reputation)
Group: StrataFrame MVPs
Posts: 1.9K, Visits: 21K
Hi Melvin.

Where are you importing from? I have just tested it over here importing from a SQL Server database and it worked fine. The import procedure is certainly a feature to help on the DDT project creation, so if you still are getting this behavior, let us know from where you are importing and maybe just change the fields' data types on DDT after the import procedure so you can deploy your database correctly.
Melvin Xuereb
Melvin Xuereb
StrataFrame Novice (103 reputation)StrataFrame Novice (103 reputation)StrataFrame Novice (103 reputation)StrataFrame Novice (103 reputation)StrataFrame Novice (103 reputation)StrataFrame Novice (103 reputation)StrataFrame Novice (103 reputation)StrataFrame Novice (103 reputation)StrataFrame Novice (103 reputation)
Group: Forum Members
Posts: 29, Visits: 128
Hi,

We have imported a database structure into the DDT and we noticed that all fields which datatype is decimal were imported as INT.
This can be shown in the attached screenshot.

As also can be noted, the precision and scale values were noted by the DDT, however, the textbox is greyed out.

When we have deployed the package to create a new database, the field was created as INT.

Is there a fix for this issue?
Any feedback is appreciated

Thanks
Melvin
Attachments
InvalidInt.png (222 views, 23.00 KB)
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search