Strange behaviour with option GO n

Toad for SQL Server
1

Last version of TOAD 5.7. I use SQL Server 2005 Advanced Express Edition in italian language with service pack 4.

I test this simple script :

if OBJECT_ID(‘dbo.T1’,‘U’) is not null

drop table dbo.T1;

create table dbo.T1(col1 int identity);
insert into dbo.T1 default values;

go 100
select * from dbo.T1;

I create a simple DB TEST_TOAD in execute this script on this DB.
I execute the script statement by statement. I select first,second,third and fourth and press F9.
First :

if OBJECT_ID(‘dbo.T1’,‘U’) is not null

drop table dbo.T1;

Second : create table dbo.T1(col1 int identity);
Third : insert into dbo.T1 default values;

go 100

Fourth : select * from dbo.T1;

When I execute the last script I obtain only one row with one record with value 1.

If I execute the same script in the same mode with SSMS in the last script I obtain a grid with 100 records.

Why this with TOAD ?
It’s normal ?

I stay tune for your answer.

Best regards.

Sergio Bertolotti

2

Hi Sergio,

welcome back =) we missed you.

In regards of your report - this is toad limitation at this point of time - “GO 100” is not supported. We had a similar question in past and we are considering to add this feature going forward.

3

Hi Valentine,

I’m alive and continue to use TOAD. Next week I download new beta version 5.8 and test it.

Stay tune for some bugs in the future.

Regards GO n , I understand your position.
I hope to see this feature will be implemented in the future.
Why not in 5.8 ?

Best regards.

Sergio Bertolotti

4

Dear Valentine,

now in TOAD SS BETA 6.0 this little bug/feature is OK.
Many thank’s for this.

Best regards.

Sergio Bertolotti