string beginning "c:\Data_Mi..." is too long. maximum size is 79 characters.

I am attempting to run scripts with paths that are longer than 79 characters and getting errors.

Is there any way around this?
With WIN2k I am not able to use the "@@" inside a file-path to solve the problem (like "@@\scripts\script.sql).

my path line currently looks something like this:
@D:\Data_Migration\Project\Name\Hardware\hard_metal_hammers\load_ballpean.sql


then I get the error:
string beginning "c:\Data_Mi..." is too long. maximum size is 79 characters.

Any suggestions or am I screwed.

thanks.

Set your SQLPATH to include your directory.

This could be a possible solution.

I was looking up the DOCS on this.
However, these are migration scripts that I want to automatically call at any given timeframe.

Going into the registry to edit the SQLPATH seems a bit excessive and not really possible.

in NT you could just specify the path further down the path you were already on.

ie: c:\test\test.sql reads "@@test2\test.sql"
which would call that next script residing in c:\test\test2\test.sql

Somewhere between NT and 2k something went wrong.
I am pretty sure I can do things like this in UNIX (if I remember correctly).

How many SQLPATHs in the registry can I make?
I am assuming only one.

Quote:

---

Originally posted by Cookies
This could be a possible solution.

I was looking up the DOCS on this.
However, these are migration scripts that I want to automatically call at any given timeframe.

Going into the registry to edit the SQLPATH seems a bit excessive and not really possible.

---

To quote Ron Popiel; "Set it, and Forget it!". You set it once on your machine and it's always set.

Quote:

---

in NT you could just specify the path further down the path you were already on.

ie: c:\test\test.sql reads "@@test2\test.sql"
which would call that next script residing in c:\test\test2\test.sql

---

sounds like kluge waiting to happen...

Quote:

---

How many SQLPATHs in the registry can I make?
I am assuming only one.

---

definitely more than one directory in your SQLPATH statement. There's probably a limit, but one or two directories shouldn't blow it out.

If only I knew what a Kluge was ...

Thanks for the help.
I set it, it works, and everyone is happy.
I didn't realize that the current default Path for SQLPATH was inconsequential and not really needed.

:D

http://www.houghi.org/jargon/kludge.html

Quote:

---

Originally posted by MARIST
This could be a possible solution.
in NT you could just specify the path further down the path you were already on.
ie: c:\test\test.sql reads "@@test2\test.sql"
which would call that next script residing in c:\test\test2\test.sql


sounds like kluge waiting to happen...

---

Well, now I can take offense ;)

At least NOW I am not 'Kluging'.

BTW - I can set multiple SQLPATHs just by seperating with a semi-colon? Did I read that correctly?

Kludge=bad

Using the features of the software to get the job done=priceless (ok, maybe not priceless, but better than a kludge).

Yes, you can put multiple directories in your SQLPATH by seperating with a ":" or ";" depending on your OS.