Autogrowth values keep changing

Hi!

We have 2 dbs on our dw-server and the autogrowth values for both the data- and logfiles on both of these dbs changes about once a month. The data autogrowth value changes from 10megs to a percentage value between 3200 and 6400 and the log-file value changes from 10 percent to a percentage value between 3200 and 6400. Resulting in huge files and filling the drive.

What am I missing here?

BR John

The value does not change on its own. Someone/process must be changing this. Perhaps, you should turn on audit to see who's responsible.|||

Just did it. Created a trace with the SQL Profiler to catch the SQL Batch-events. Now we just have to wait it out...

John

|||

Not a helpful reply, it can and it does.

I have now experienced the same bug myself. SQL 2005 on x64, has been running okay for months. Last month the database jumped from 3Gb to something like 60Gb, I found the autogrowth setting had switched from xxMB to 2048%. I thought I must have done this by mistake, so I shrank the DB and reset the autogrowth values.

This morning I log in, database is now 204GB and the autogrowth is set to 32768% !!! It stopped at 204Gb as there was no diskspace left. I've reset the autogrow again also set "maxsize" to 10GB.

This is definitely a bug and quite a serious one - it could quite easily take out an operational server by eating up disk space.

|||

Yes this is quite serious. It stops our ETL-process because of the drive being full.

Nothing in our tracelog yet...

|||

It is a known bug, see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

b) it only manifests after the SQL server has been restarted

c) It has not been fixed in SP1 so here's hoping for SP2.

You won't see anything in the trace logs, it's a bug in the SQL engine. When it stores the settings for autogrow it does not correctly set one flag for percentage or non-percentage growth. If you restart SQL server you'll see the incorrect value/

Workarounds:

set Max size of the file to prevent the file from growing too large

turn off AutoGrow

use % based autogrow

|||

Thanks!

BR John

|||

HowardRichards wrote:

It is a known bug, see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

b) it only manifests after the SQL server has been restarted

c) It has not been fixed in SP1 so here's hoping for SP2.

You won't see anything in the trace logs, it's a bug in the SQL engine. When it stores the settings for autogrow it does not correctly set one flag for percentage or non-percentage growth. If you restart SQL server you'll see the incorrect value/

Workarounds:

set Max size of the file to prevent the file from growing too large

turn off AutoGrow

use % based autogrow

I was not aware of this bug. Thanks for the correction.|||

It is a known bug, see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

Regarding above comment ... I ran into that exact bug with a fresh install of SQL Server 2005 and SP1 on a completely new server. And it shut down my new 1 TB server!!!

Here's hoping SP2 does address it, as I have no interest in having my production servers needing that much coddling.

|||

Yes - we've been hit by this as well.

We had it set to autogrow by 250MB, until after a reboot where it changed to 32000%. Unfortunately we didn't spot this until we filled up our log file disk.

The annoying thing was that SQL Server Management Studio doesn't let you change back a value that has erroneously gone to 32000%, because it complains that the value exceeds the maximum allowed!!

So you need to change it using the alter database statement:

alter database dbname modify file (name = filename, filegrowth = 10%)

Roll on SP2...

|||

We just upgraded to SP2 for that reason (the fix is supposedly in there), but we're still unable to correct the value.

When attempting to change the value, the following error appears:

Value of ‘32768’ is not valid for “value’. “Value” should be between ‘Minimum’ and “Maximum’ Parameter name Value (System. Windows.Forms)

from the SQL Server 2005 SP2 fix list:

919611 (http://support.microsoft.com/kb/919611/)

FIX: The value of the automatic growth increment of a database file may be very large in SQL Server 2005 with Service Pack 1

Can anyone advise if running this statement will correct this issue permanently?

alter database MyTestDB
Modify File
(name=mytestdb, filegrowth = 500 mb)

Thanks!

|||Executing an alter database statement does not appear to prevent the behavior from resurfacing.

Autogrowth values keep changing

Hi!

We have 2 dbs on our dw-server and the autogrowth values for both the data- and logfiles on both of these dbs changes about once a month. The data autogrowth value changes from 10megs to a percentage value between 3200 and 6400 and the log-file value changes from 10 percent to a percentage value between 3200 and 6400. Resulting in huge files and filling the drive.

What am I missing here?

BR John

The value does not change on its own. Someone/process must be changing this. Perhaps, you should turn on audit to see who's responsible.|||

Just did it. Created a trace with the SQL Profiler to catch the SQL Batch-events. Now we just have to wait it out...

John

|||

Not a helpful reply, it can and it does.

I have now experienced the same bug myself. SQL 2005 on x64, has been running okay for months. Last month the database jumped from 3Gb to something like 60Gb, I found the autogrowth setting had switched from xxMB to 2048%. I thought I must have done this by mistake, so I shrank the DB and reset the autogrowth values.

This morning I log in, database is now 204GB and the autogrowth is set to 32768% !!! It stopped at 204Gb as there was no diskspace left. I've reset the autogrow again also set "maxsize" to 10GB.

This is definitely a bug and quite a serious one - it could quite easily take out an operational server by eating up disk space.

|||

Yes this is quite serious. It stops our ETL-process because of the drive being full.

Nothing in our tracelog yet...

|||

It is a known bug, see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

b) it only manifests after the SQL server has been restarted

c) It has not been fixed in SP1 so here's hoping for SP2.

You won't see anything in the trace logs, it's a bug in the SQL engine. When it stores the settings for autogrow it does not correctly set one flag for percentage or non-percentage growth. If you restart SQL server you'll see the incorrect value/

Workarounds:

set Max size of the file to prevent the file from growing too large

turn off AutoGrow

use % based autogrow

|||

Thanks!

BR John

|||

HowardRichards wrote:

It is a known bug, see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

b) it only manifests after the SQL server has been restarted

c) It has not been fixed in SP1 so here's hoping for SP2.

You won't see anything in the trace logs, it's a bug in the SQL engine. When it stores the settings for autogrow it does not correctly set one flag for percentage or non-percentage growth. If you restart SQL server you'll see the incorrect value/

Workarounds:

set Max size of the file to prevent the file from growing too large

turn off AutoGrow

use % based autogrow

I was not aware of this bug. Thanks for the correction.|||

It is a known bug, see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

Regarding above comment ... I ran into that exact bug with a fresh install of SQL Server 2005 and SP1 on a completely new server. And it shut down my new 1 TB server!!!

Here's hoping SP2 does address it, as I have no interest in having my production servers needing that much coddling.

|||

Yes - we've been hit by this as well.

We had it set to autogrow by 250MB, until after a reboot where it changed to 32000%. Unfortunately we didn't spot this until we filled up our log file disk.

The annoying thing was that SQL Server Management Studio doesn't let you change back a value that has erroneously gone to 32000%, because it complains that the value exceeds the maximum allowed!!

So you need to change it using the alter database statement:

alter database dbname modify file (name = filename, filegrowth = 10%)

Roll on SP2...

|||

We just upgraded to SP2 for that reason (the fix is supposedly in there), but we're still unable to correct the value.

When attempting to change the value, the following error appears:

Value of ‘32768’ is not valid for “value’. “Value” should be between ‘Minimum’ and “Maximum’ Parameter name Value (System. Windows.Forms)

from the SQL Server 2005 SP2 fix list:

919611 (http://support.microsoft.com/kb/919611/)

FIX: The value of the automatic growth increment of a database file may be very large in SQL Server 2005 with Service Pack 1

Can anyone advise if running this statement will correct this issue permanently?

alter database MyTestDB
Modify File
(name=mytestdb, filegrowth = 500 mb)

Thanks!

|||Executing an alter database statement does not appear to prevent the behavior from resurfacing.

Autogrowth values keep changing

Hi!

We have 2 dbs on our dw-server and the autogrowth values for both the data- and logfiles on both of these dbs changes about once a month. The data autogrowth value changes from 10megs to a percentage value between 3200 and 6400 and the log-file value changes from 10 percent to a percentage value between 3200 and 6400. Resulting in huge files and filling the drive.

What am I missing here?

BR John

The value does not change on its own. Someone/process must be changing this. Perhaps, you should turn on audit to see who's responsible.|||

Just did it. Created a trace with the SQL Profiler to catch the SQL Batch-events. Now we just have to wait it out...

John

|||

Not a helpful reply, it can and it does.

I have now experienced the same bug myself. SQL 2005 on x64, has been running okay for months. Last month the database jumped from 3Gb to something like 60Gb, I found the autogrowth setting had switched from xxMB to 2048%. I thought I must have done this by mistake, so I shrank the DB and reset the autogrowth values.

This morning I log in, database is now 204GB and the autogrowth is set to 32768% !!! It stopped at 204Gb as there was no diskspace left. I've reset the autogrow again also set "maxsize" to 10GB.

This is definitely a bug and quite a serious one - it could quite easily take out an operational server by eating up disk space.

|||

Yes this is quite serious. It stops our ETL-process because of the drive being full.

Nothing in our tracelog yet...

|||

It is a known bug, see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

b) it only manifests after the SQL server has been restarted

c) It has not been fixed in SP1 so here's hoping for SP2.

You won't see anything in the trace logs, it's a bug in the SQL engine. When it stores the settings for autogrow it does not correctly set one flag for percentage or non-percentage growth. If you restart SQL server you'll see the incorrect value/

Workarounds:

set Max size of the file to prevent the file from growing too large

turn off AutoGrow

use % based autogrow

|||

Thanks!

BR John

|||

HowardRichards wrote:

It is a known bug, see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

b) it only manifests after the SQL server has been restarted

c) It has not been fixed in SP1 so here's hoping for SP2.

You won't see anything in the trace logs, it's a bug in the SQL engine. When it stores the settings for autogrow it does not correctly set one flag for percentage or non-percentage growth. If you restart SQL server you'll see the incorrect value/

Workarounds:

set Max size of the file to prevent the file from growing too large

turn off AutoGrow

use % based autogrow

I was not aware of this bug. Thanks for the correction.|||

It is a known bug, see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

Regarding above comment ... I ran into that exact bug with a fresh install of SQL Server 2005 and SP1 on a completely new server. And it shut down my new 1 TB server!!!

Here's hoping SP2 does address it, as I have no interest in having my production servers needing that much coddling.

|||

Yes - we've been hit by this as well.

We had it set to autogrow by 250MB, until after a reboot where it changed to 32000%. Unfortunately we didn't spot this until we filled up our log file disk.

The annoying thing was that SQL Server Management Studio doesn't let you change back a value that has erroneously gone to 32000%, because it complains that the value exceeds the maximum allowed!!

So you need to change it using the alter database statement:

alter database dbname modify file (name = filename, filegrowth = 10%)

Roll on SP2...

|||

We just upgraded to SP2 for that reason (the fix is supposedly in there), but we're still unable to correct the value.

When attempting to change the value, the following error appears:

Value of ‘32768’ is not valid for “value’. “Value” should be between ‘Minimum’ and “Maximum’ Parameter name Value (System. Windows.Forms)

from the SQL Server 2005 SP2 fix list:

919611 (http://support.microsoft.com/kb/919611/) FIX: The value of the automatic growth increment of a database file may be very large in SQL Server 2005 with Service Pack 1

Can anyone advise if running this statement will correct this issue permanently?

alter database MyTestDB
Modify File
(name=mytestdb, filegrowth = 500 mb)

Thanks!

|||Executing an alter database statement does not appear to prevent the behavior from resurfacing.

Autogrowth values keep changing

Hi!

We have 2 dbs on our dw-server and the autogrowth values for both the data- and logfiles on both of these dbs changes about once a month. The data autogrowth value changes from 10megs to a percentage value between 3200 and 6400 and the log-file value changes from 10 percent to a percentage value between 3200 and 6400. Resulting in huge files and filling the drive.

What am I missing here?

BR John

The value does not change on its own. Someone/process must be changing this. Perhaps, you should turn on audit to see who's responsible.|||

Just did it. Created a trace with the SQL Profiler to catch the SQL Batch-events. Now we just have to wait it out...

John

|||

Not a helpful reply, it can and it does.

I have now experienced the same bug myself. SQL 2005 on x64, has been running okay for months. Last month the database jumped from 3Gb to something like 60Gb, I found the autogrowth setting had switched from xxMB to 2048%. I thought I must have done this by mistake, so I shrank the DB and reset the autogrowth values.

This morning I log in, database is now 204GB and the autogrowth is set to 32768% !!! It stopped at 204Gb as there was no diskspace left. I've reset the autogrow again also set "maxsize" to 10GB.

This is definitely a bug and quite a serious one - it could quite easily take out an operational server by eating up disk space.

|||

Yes this is quite serious. It stops our ETL-process because of the drive being full.

Nothing in our tracelog yet...

|||

It is a known bug, see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

b) it only manifests after the SQL server has been restarted

c) It has not been fixed in SP1 so here's hoping for SP2.

You won't see anything in the trace logs, it's a bug in the SQL engine. When it stores the settings for autogrow it does not correctly set one flag for percentage or non-percentage growth. If you restart SQL server you'll see the incorrect value/

Workarounds:

set Max size of the file to prevent the file from growing too large

turn off AutoGrow

use % based autogrow

|||

Thanks!

BR John

|||

HowardRichards wrote:

It is a known bug, see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

b) it only manifests after the SQL server has been restarted

c) It has not been fixed in SP1 so here's hoping for SP2.

You won't see anything in the trace logs, it's a bug in the SQL engine. When it stores the settings for autogrow it does not correctly set one flag for percentage or non-percentage growth. If you restart SQL server you'll see the incorrect value/

Workarounds:

set Max size of the file to prevent the file from growing too large

turn off AutoGrow

use % based autogrow

I was not aware of this bug. Thanks for the correction.|||

It is a known bug, see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

Regarding above comment ... I ran into that exact bug with a fresh install of SQL Server 2005 and SP1 on a completely new server. And it shut down my new 1 TB server!!!

Here's hoping SP2 does address it, as I have no interest in having my production servers needing that much coddling.

|||

Yes - we've been hit by this as well.

We had it set to autogrow by 250MB, until after a reboot where it changed to 32000%. Unfortunately we didn't spot this until we filled up our log file disk.

The annoying thing was that SQL Server Management Studio doesn't let you change back a value that has erroneously gone to 32000%, because it complains that the value exceeds the maximum allowed!!

So you need to change it using the alter database statement:

alter database dbname modify file (name = filename, filegrowth = 10%)

Roll on SP2...

|||

We just upgraded to SP2 for that reason (the fix is supposedly in there), but we're still unable to correct the value.

When attempting to change the value, the following error appears:

Value of ‘32768’ is not valid for “value’. “Value” should be between ‘Minimum’ and “Maximum’ Parameter name Value (System. Windows.Forms)

from the SQL Server 2005 SP2 fix list:

919611 (http://support.microsoft.com/kb/919611/)

FIX: The value of the automatic growth increment of a database file may be very large in SQL Server 2005 with Service Pack 1

Can anyone advise if running this statement will correct this issue permanently?

alter database MyTestDB
Modify File
(name=mytestdb, filegrowth = 500 mb)

Thanks!

|||Executing an alter database statement does not appear to prevent the behavior from resurfacing.

Autogrowth values keep changing

Hi!

We have 2 dbs on our dw-server and the autogrowth values for both the data- and logfiles on both of these dbs changes about once a month. The data autogrowth value changes from 10megs to a percentage value between 3200 and 6400 and the log-file value changes from 10 percent to a percentage value between 3200 and 6400. Resulting in huge files and filling the drive.

What am I missing here?

BR John

The value does not change on its own. Someone/process must be changing this. Perhaps, you should turn on audit to see who's responsible.|||

Just did it. Created a trace with the SQL Profiler to catch the SQL Batch-events. Now we just have to wait it out...

John

|||

Not a helpful reply, it can and it does.

I have now experienced the same bug myself. SQL 2005 on x64, has been running okay for months. Last month the database jumped from 3Gb to something like 60Gb, I found the autogrowth setting had switched from xxMB to 2048%. I thought I must have done this by mistake, so I shrank the DB and reset the autogrowth values.

This morning I log in, database is now 204GB and the autogrowth is set to 32768% !!! It stopped at 204Gb as there was no diskspace left. I've reset the autogrow again also set "maxsize" to 10GB.

This is definitely a bug and quite a serious one - it could quite easily take out an operational server by eating up disk space.

|||

Yes this is quite serious. It stops our ETL-process because of the drive being full.

Nothing in our tracelog yet...

|||

It is a known bug, see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

b) it only manifests after the SQL server has been restarted

c) It has not been fixed in SP1 so here's hoping for SP2.

You won't see anything in the trace logs, it's a bug in the SQL engine. When it stores the settings for autogrow it does not correctly set one flag for percentage or non-percentage growth. If you restart SQL server you'll see the incorrect value/

Workarounds:

set Max size of the file to prevent the file from growing too large

turn off AutoGrow

use % based autogrow

|||

Thanks!

BR John

|||

HowardRichards wrote:

It is a known bug, see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

b) it only manifests after the SQL server has been restarted

c) It has not been fixed in SP1 so here's hoping for SP2.

You won't see anything in the trace logs, it's a bug in the SQL engine. When it stores the settings for autogrow it does not correctly set one flag for percentage or non-percentage growth. If you restart SQL server you'll see the incorrect value/

Workarounds:

set Max size of the file to prevent the file from growing too large

turn off AutoGrow

use % based autogrow

I was not aware of this bug. Thanks for the correction.|||

It is a known bug, see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

Regarding above comment ... I ran into that exact bug with a fresh install of SQL Server 2005 and SP1 on a completely new server. And it shut down my new 1 TB server!!!

Here's hoping SP2 does address it, as I have no interest in having my production servers needing that much coddling.

|||

Yes - we've been hit by this as well.

We had it set to autogrow by 250MB, until after a reboot where it changed to 32000%. Unfortunately we didn't spot this until we filled up our log file disk.

The annoying thing was that SQL Server Management Studio doesn't let you change back a value that has erroneously gone to 32000%, because it complains that the value exceeds the maximum allowed!!

So you need to change it using the alter database statement:

alter database dbname modify file (name = filename, filegrowth = 10%)

Roll on SP2...

|||

We just upgraded to SP2 for that reason (the fix is supposedly in there), but we're still unable to correct the value.

When attempting to change the value, the following error appears:

Value of ‘32768’ is not valid for “value’. “Value” should be between ‘Minimum’ and “Maximum’ Parameter name Value (System. Windows.Forms)

from the SQL Server 2005 SP2 fix list:

919611 (http://support.microsoft.com/kb/919611/)

FIX: The value of the automatic growth increment of a database file may be very large in SQL Server 2005 with Service Pack 1

Can anyone advise if running this statement will correct this issue permanently?

alter database MyTestDB
Modify File
(name=mytestdb, filegrowth = 500 mb)

Thanks!

|||Executing an alter database statement does not appear to prevent the behavior from resurfacing.

autocontained selects

Dear gurus,
select 'insert into cargafrecuencias([id],tipo,horas) values(' +
convert(char(2),[id]) + ',
''' + rtrim(ltrim(tipo)) + ''',
' + convert(char(5), horas) + ')'
from cargafrecuencias
That query returns fine INSERTS and ready for be executed:
insert into cargafrecuencias([id],tipo,horas) values(1 , 'Semanal',
168 )
insert into cargafrecuencias([id],tipo,horas) values(2 , 'Mensual',
720 )
insert into cargafrecuencias([id],tipo,horas) values(3 , 'Diaria',
24 )
insert into cargafrecuencias([id],tipo,horas) values(4 , 'Cuando llegue
el fichero', 8640 )
It's easy and useful without a doubt. But can you imagine do the same with a
table with 80 columns?
I would like do something like that (it would be gorgeous):
select 'insert into table(f1,f2,f3... fn) values (sp_help table)'
from table
On the other hand is very annonying.
Does anyone have any ideas or thoughts?
Thanks in advance and regards,CREATE PROCEDURE SPInserttest
(
@.Test varchar(50)
)
AS
BEGIN
PRINT 'Do something with the test varchar(50)'
Select 'Jens'
UNION
SELECT 'BOB'
END
CREATE TABLE #Tabname
(
Names varchar(50)
)
INSERT INTo #Tabname
EXEC('SPInserttest ''Test''')
Select * from #Tabname
DROP Procedure SPInserttest
DROP Table #Tabname
--
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Enric" wrote:

> Dear gurus,
> select 'insert into cargafrecuencias([id],tipo,horas) values(' +
> convert(char(2),[id]) + ',
> ''' + rtrim(ltrim(tipo)) + ''',
> ' + convert(char(5), horas) + ')'
> from cargafrecuencias
>
> That query returns fine INSERTS and ready for be executed:
> insert into cargafrecuencias([id],tipo,horas) values(1 , 'Semanal',
> 168 )
> insert into cargafrecuencias([id],tipo,horas) values(2 , 'Mensual',
> 720 )
> insert into cargafrecuencias([id],tipo,horas) values(3 , 'Diaria',
> 24 )
> insert into cargafrecuencias([id],tipo,horas) values(4 , 'Cuando llegue
> el fichero', 8640 )
>
> It's easy and useful without a doubt. But can you imagine do the same with
a
> table with 80 columns?
> I would like do something like that (it would be gorgeous):
> select 'insert into table(f1,f2,f3... fn) values (sp_help table)'
> from table
> On the other hand is very annonying.
> Does anyone have any ideas or thoughts?
> Thanks in advance and regards,
>|||Try this one.
http://vyaskn.tripod.com/code/generate_inserts.txt
Roji. P. Thomas
Net Asset Management
http://toponewithties.blogspot.com
"Enric" <Enric@.discussions.microsoft.com> wrote in message
news:1BD06558-758F-490C-B228-7090641DA685@.microsoft.com...
> Dear gurus,
> select 'insert into cargafrecuencias([id],tipo,horas) values(' +
> convert(char(2),[id]) + ',
> ''' + rtrim(ltrim(tipo)) + ''',
> ' + convert(char(5), horas) + ')'
> from cargafrecuencias
>
> That query returns fine INSERTS and ready for be executed:
> insert into cargafrecuencias([id],tipo,horas) values(1 , 'Semanal',
> 168 )
> insert into cargafrecuencias([id],tipo,horas) values(2 , 'Mensual',
> 720 )
> insert into cargafrecuencias([id],tipo,horas) values(3 , 'Diaria',
> 24 )
> insert into cargafrecuencias([id],tipo,horas) values(4 , 'Cuando
> llegue
> el fichero', 8640 )
>
> It's easy and useful without a doubt. But can you imagine do the same with
> a
> table with 80 columns?
> I would like do something like that (it would be gorgeous):
> select 'insert into table(f1,f2,f3... fn) values (sp_help table)'
> from table
> On the other hand is very annonying.
> Does anyone have any ideas or thoughts?
> Thanks in advance and regards,
>|||Great, thanks a lot, it works very well
"Roji. P. Thomas" wrote:

> Try this one.
> http://vyaskn.tripod.com/code/generate_inserts.txt
>
> --
> Roji. P. Thomas
> Net Asset Management
> http://toponewithties.blogspot.com
>
> "Enric" <Enric@.discussions.microsoft.com> wrote in message
> news:1BD06558-758F-490C-B228-7090641DA685@.microsoft.com...
>
>|||XXXXing life. That doesn't works with my table, it is too large in terms of
columns.
"Roji. P. Thomas" wrote:

> Try this one.
> http://vyaskn.tripod.com/code/generate_inserts.txt
>
> --
> Roji. P. Thomas
> Net Asset Management
> http://toponewithties.blogspot.com
>
> "Enric" <Enric@.discussions.microsoft.com> wrote in message
> news:1BD06558-758F-490C-B228-7090641DA685@.microsoft.com...
>
>

Autocomplete combobox

Dear all,

I have a parametrized report which displays the available values for the parameter in a combobox (dropdownlist). I need to make that combobox autocomplete what the user types.

Is there any way for that?!

Thank you.Here is some code in c#. You will need to use a custom application to display the report & parameters.

|||There is no way out of the box to do this. You would have to write your own code to accomplish this. You could use the .Net 2.0 ReportViewer control to display the report and then handle the parameters yourself.

Hope that helps.
-Daniel

Autocomplete combobox

Dear all,

I have a parametrized report which displays the available values for the parameter in a combobox (dropdownlist). I need to make that combobox autocomplete what the user types.

Is there any way for that?!

Thank you.Here is some code in c#. You will need to use a custom application to display the report & parameters.|||There is no way out of the box to do this. You would have to write your own code to accomplish this. You could use the .Net 2.0 ReportViewer control to display the report and then handle the parameters yourself.

Hope that helps.
-Daniel

auto incrementing->Updating values in two related tables :Help!

hi there,
i am new to sql server database.i am doing small projects rightnow using asp.net and sql to create webpages (very basic webpages)
My problem is:
Problem :

i have two tables ....table 1 and table 2.
Table 1 has following fields: studentid,student name,student address.
Table 2 has following fields:studentid and course .
table1 student id is the primary key refrencing table 2 student id.
Now i delete a record in table 1 which will in turn also get deleted intable 2 . so for eg if i have three records 1 ,2 and 3 ...then idelete 2 in table 1 ...i will have 1 and 3 in both table 1 and table2...now i want 3 to become 2 in both table 1 and table 2...so that idont have empty space between two student id's 1 and 3. so this is myproblem...if any one can help me out with suggestions pleasedo.
thank you all......
ahmed_ind
if you want my advice ... this is not a good solution or methodto follow .... you should not really care about the space ...once you create ID for a record and delete it, you should notreally care about it to have stabled data not to have confliced IDs.
if your concerns about the ID number that you will reach in 1 year ..you can avoid that when you create the ID columns and assign the datatype that has the range for what you know it will enough for you...... if i were you i will not bother myself with what are youlooking for.
By the way this is my idea from my experience and what database expertsthink..... but if some one has different opinion and beleive there isa better technique ... you can advise !!
|||hi fadil.....thanx for u r suggestion.
i wanted to have automation of operation at the background ; i.e. in the database (sql ) ...so i used identity function toauto-increment values of student id by one ....then i wanted to deleteby performing auto-decrement function.....so thats how i camewith the idea, i jus wanted to learn tough things...ok any way thanxagain for ur suggestion and if u have any way of solution for myquestion please do reply..thank u..
ahmed
|||look at this case and see what i mean
ID Name
1 Ahmed
2 John
3 Ali

if you deleted 'Ali' the decrement would be ok as it is the last one on the list but if you delete 'Ahmed' you will loose the primar key integritiy for John and Ali as they will be 1 and 2.....i beleive this is not a good methodlogy to do... you might injure your data !!|||hi fadil,
i get u...i understand what umean...ok then my logic is not a good one then...may be i have to trysomething else than auto decrementing.....
thanxanyway for the suggestions : i will take them and follow them now andin my future...

............ahmed