Producing a usable SQL file [ddl] for a DBA to use

[tabb1458963]

The .sql file which is produced does not reatin the formatting and the DBa's i work with are unable to use the file.  How can this be?  Any advice on what i might be doing wrong?  

I am following the tutorial and have reviewed this online.
No one seems to be able to advise?  

we purchased this tool with the intention of producing db scripts for a separate team to use.  if it cannot do this then that is an issue. :-?

[qwerty]

It would probably help others to help you if you define what "unable to use" means.

q.

[tabb1458963]

When you view the file [within e.a.] it has formatting like you would expect to see it.  When opening the .sql file produced outside of e.a the file is in one long narrative.

[qwerty]

It's meant to be read by a machine, isn't it?

q.

[skiwi]

It's meant to be read by a machine, isn't it?

Careful about the way you describe our DBAs.

[MMA]

When you view the file [within e.a.] it has formatting like you would expect to see it.  When opening the .sql file produced outside of e.a the file is in one long narrative.

I could reproduce your problem in Windows' Notepad.

The reason is that the exported file is using "\n" (line feed) as line separator, your system (editor) might expect "\r" (carriage return) or "\r\n" (carriage return + line feed) .

You can easily get around of this issue by changing an editor. E.g. it  formats well on my Windows and Notepad++. Or you can use EA to open (Ctrl + Alt + O) this .sql file.

You can submit a ticket requesting the format be controlled by Tools | Options | Code Engineering | "output files use both CR & LF". If the option is ticked, it should generate "\r\n" instead of "\n", then it will work for all editors.

Hope that helps