Re: OSQL Input File Size

The last portion of the stored procedures.

In other words, the script file looks like:


IF EXISTS (sp_A) DROP sp_A
GO
CREATE PROCEDURE sp_A AS ....
GO
IF EXISTS (sp_B) DROP sp_B
GO
CREATE PROCEDURE sp_B AS ....
GO

Then, assume there are 1000 stored procedures in this script file. Only the
first 800 of those stored procedures are actually created. To further
diagnose the problem, I added PRINT statements around the end of the script
(and at the very end) and the PRINT statements were being output. So, the
script seems to run in its entirety; however, it does not seem to actually
apply the last 200 or so objects.
None of the last objects are created.

Also note that I've seen this same type of behavior with other large script
files containing other types of objects (i.e., triggers).


"Ciprian Gerea [MSFT]" wrote:

What exactly does not get created?

--
Ciprian Gerea
SDE, SqlServer

This posting is provided "AS IS" with no warranties, and confers no rights.


"DP" <DP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:36EF0657-89F5-4948-B6AF-4CBB6800E912@xxxxxxxxxxxxxxxx
Running SQL Server SP4 / Win2K SP4

Have input file (containing all stored procedures batch separated with GO)
of about 7MB. When running this file using OSQL utility, only about 80%
of
the objects get applied. No errors in the output (only sysdepends
warnings).

If I split the file in half and run OSQL on the two halves, works just
fine.
The script file works just fine in ISQL and ISQLW.

Any ideas?





.

Loading