"trunc. log on chkpt" help

First time poster...
Alright this is what I got...I am running MSSQL server 2000.
I have already restored a copy of the production db to our test sql server.

What I need to do is run some update scripts (from 3rd party vendor, going to newer version of their product). The database is about 60Gb and I filled up the transaction log (causing later updates to fail) while running one of their scripts that executed 194 routines of:

alter table Table_Name add New_Column int
GO
EXEC sp_bindefault mg_zero_dflt, [Table_Name.New_Column]
GO
update Table_Name set New_Column=1
GO

Will "sp_dboption 'dbname' 'trunc. log on chkpt' 'TRUE' " automatically truncate the transaction log when approaching the transaction log file limit while running these update scripts. Then when the updates are complete go ahead and "sp_dboption 'dbname' 'trunc. log on chkpt' 'FALSE' "

I'm not worried about logging the transactions during this process, I just don't want to have the transaction log fill up while running these scripts causing it to error out.

Or is there a way to make those changes using bcp?In the database properties window, go to the options tab and set your database recovery model to "simple". This should keep the log from filling up.
When you are finished, set the recovery model back to "full" and run an immediate backup.|||Thanks for the help. I remember seeing something about that and got sidetracked with the whole 'trunc. log on chkpt' idea. I'm in the process of finishing the scripts on the test server and I'll update with results. Thanks again!|||I finished running the scripts late yesterday without any hitches. That was exactly what I was looking for!

"Timeout expired"

In a legacy project on the production server, we have a database which
generated the following error when executing a report (written in ASP).
Microsoft OLE DB Provider for ODBC Drivers error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
I then created a SQL dump of this database and exported the tables to Access
MDB file.
Using another test server, I re-created the entire database using the SQL
dump file and imported the data using Access MDB file. Next, I copied the
entire ASP source tree over to this test server.
Lo and behold, when I ran the same report program, it ran successfully!
Could someone tell me why the legacy project running on the production
server caused this timeout error, while the exact same program running on a
test server runs without problem?
Could it be an indexing issue?
Thanks.Ed,
"Ed" <eddiemarino@.hotmail.com> wrote in message
news:OjVEPFt6DHA.2392@.TK2MSFTNGP11.phx.gbl...

quote:

---

> Could someone tell me why the legacy project running on the production
> server caused this timeout error, while the exact same program running on

---

a

quote:

---

> test server runs without problem?
> Could it be an indexing issue?

---

Yes, it could be indexing.
It could also be locks, server load, etc.
Dev servers tend to be less busy than production machines, and what works
well in the sandbox might not be so hot when the server's really up against
it.
If you've not done so, start by having ASP developers set a custom timeout
value to something other than the default.
(Assuming, of course, identical schema between test and production <g> )
James Hokes

"Timeout expired"

In a legacy project on the production server, we have a database which
generated the following error when executing a report (written in ASP).
Microsoft OLE DB Provider for ODBC Drivers error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
I then created a SQL dump of this database and exported the tables to Access
MDB file.
Using another test server, I re-created the entire database using the SQL
dump file and imported the data using Access MDB file. Next, I copied the
entire ASP source tree over to this test server.
Lo and behold, when I ran the same report program, it ran successfully!
Could someone tell me why the legacy project running on the production
server caused this timeout error, while the exact same program running on a
test server runs without problem?
Could it be an indexing issue?
Thanks.Ed,
"Ed" <eddiemarino@.hotmail.com> wrote in message
news:OjVEPFt6DHA.2392@.TK2MSFTNGP11.phx.gbl...
> Could someone tell me why the legacy project running on the production
> server caused this timeout error, while the exact same program running on
a
> test server runs without problem?
> Could it be an indexing issue?
Yes, it could be indexing.
It could also be locks, server load, etc.
Dev servers tend to be less busy than production machines, and what works
well in the sandbox might not be so hot when the server's really up against
it.
If you've not done so, start by having ASP developers set a custom timeout
value to something other than the default.
(Assuming, of course, identical schema between test and production <g>)
James Hokes

"Keys out of order on page (1:10579653), slots 24 and 25..." error messages

Hi,
I have sql server 2000, sp3, and several production databases on this
server. From time to time, my integrity check jobs fail on some of databases
with the error message shown above (not always the same page/slot). This
errors occur on index pages, and I resolve them by rebuilding affected
indexes. Then everything works fine 1-2 weeks, and then again.
Hardware check didn't show anything wrong, but I'm still suspecting that
something is wrong with the disks (EMC, btw). It might be that some disk
block is corrupted. How can I check if it is always the same disk block
(from (1:10579653), slots 24 and 25)?
Interesting part is that I can use corrupted index by forcing the query
through hint, and it doesn't report any error.
Any help?
Thanks,
Peja
I'd run a DBCC CheckDB immediately.
"peja" <peja@.sympatico.ca> wrote in message
news:eJQ76UXrFHA.2072@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have sql server 2000, sp3, and several production databases on this
> server. From time to time, my integrity check jobs fail on some of
> databases
> with the error message shown above (not always the same page/slot). This
> errors occur on index pages, and I resolve them by rebuilding affected
> indexes. Then everything works fine 1-2 weeks, and then again.
> Hardware check didn't show anything wrong, but I'm still suspecting that
> something is wrong with the disks (EMC, btw). It might be that some disk
> block is corrupted. How can I check if it is always the same disk block
> (from (1:10579653), slots 24 and 25)?
> Interesting part is that I can use corrupted index by forcing the query
> through hint, and it doesn't report any error.
> Any help?
> Thanks,
> Peja
>

"Keys out of order on page (1:10579653), slots 24 and 25..." error messages

Hi,
I have sql server 2000, sp3, and several production databases on this
server. From time to time, my integrity check jobs fail on some of databases
with the error message shown above (not always the same page/slot). This
errors occur on index pages, and I resolve them by rebuilding affected
indexes. Then everything works fine 1-2 weeks, and then again.
Hardware check didn't show anything wrong, but I'm still suspecting that
something is wrong with the disks (EMC, btw). It might be that some disk
block is corrupted. How can I check if it is always the same disk block
(from (1:10579653), slots 24 and 25)?
Interesting part is that I can use corrupted index by forcing the query
through hint, and it doesn't report any error.
Any help?
Thanks,
PejaI'd run a DBCC CheckDB immediately.
"peja" <peja@.sympatico.ca> wrote in message
news:eJQ76UXrFHA.2072@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have sql server 2000, sp3, and several production databases on this
> server. From time to time, my integrity check jobs fail on some of
> databases
> with the error message shown above (not always the same page/slot). This
> errors occur on index pages, and I resolve them by rebuilding affected
> indexes. Then everything works fine 1-2 weeks, and then again.
> hardware check didn't show anything wrong, but I'm still suspecting that
> something is wrong with the disks (EMC, btw). It might be that some disk
> block is corrupted. How can I check if it is always the same disk block
> (from (1:10579653), slots 24 and 25)?
> Interesting part is that I can use corrupted index by forcing the query
> through hint, and it doesn't report any error.
> Any help?
> Thanks,
> Peja
>

"Keys out of order on page (1:10579653), slots 24 and 25..." error messages

Hi,
I have sql server 2000, sp3, and several production databases on this
server. From time to time, my integrity check jobs fail on some of databases
with the error message shown above (not always the same page/slot). This
errors occur on index pages, and I resolve them by rebuilding affected
indexes. Then everything works fine 1-2 weeks, and then again.
Hardware check didn't show anything wrong, but I'm still suspecting that
something is wrong with the disks (EMC, btw). It might be that some disk
block is corrupted. How can I check if it is always the same disk block
(from (1:10579653), slots 24 and 25)?
Interesting part is that I can use corrupted index by forcing the query
through hint, and it doesn't report any error.
Any help?
Thanks,
PejaI'd run a DBCC CheckDB immediately.
"peja" <peja@.sympatico.ca> wrote in message
news:eJQ76UXrFHA.2072@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have sql server 2000, sp3, and several production databases on this
> server. From time to time, my integrity check jobs fail on some of
> databases
> with the error message shown above (not always the same page/slot). This
> errors occur on index pages, and I resolve them by rebuilding affected
> indexes. Then everything works fine 1-2 weeks, and then again.
> Hardware check didn't show anything wrong, but I'm still suspecting that
> something is wrong with the disks (EMC, btw). It might be that some disk
> block is corrupted. How can I check if it is always the same disk block
> (from (1:10579653), slots 24 and 25)?
> Interesting part is that I can use corrupted index by forcing the query
> through hint, and it doesn't report any error.
> Any help?
> Thanks,
> Peja
>

"Invalid Object.." error when using Copy SQL Server Objects task

SQL Server 2000. I have a production database, of which, I want to
make a copy. I created a DTS with the Copy SQL Server Obj Task to copy
all objects from MyDbName to MyDbName_Test (on the same instance of SQL
Server). I've used this method on other databases many times and it
completes just fine. On this db, however, I get "Invalid object name
'dbo.vwWhereUsed'" when trying to complete the task. vwWhereUsed is, of
course, one of my views. This view functions properly when ran. I
later found that the error seemed to be happening when the DTS attempts
to copy another view that calls vwWhereUsed. This other view does not
get copied to MyDbName_Test before the DTS fails, but vwWhereUsed is
copied.
My thought was that the other view is being copied to the new db before
vwWhereUsed and blowing up because vwWhereUsed is not there yet... but
from what I just explained, that doesn't seem to be the case.
On another DTS attempt to move a few tables,that have nothing to do
with vwWhereUsed, into a new clean database (MyDBName_Test) I got the
same error message (Invalid object name 'dbo.vwWhereUsed').
Interestingly enough, if I UNcheck the "Drop Destination Objects First"
option before moving those tables, the error does not occur. This does
not make sense, because it was a NEW db.. there was nothing to DROP.
Is there something I'm not seeing here? or..
Is there techniques to help me discover exactly whats happening.. or
any tips on making copies of databases using the Copy SQL Server Object
Task that may help correct this issue?
TIALindsey,
Seems like a lot of unnecessary work. Why not use a BACKUP/RESTORE
approach? Or if the DB can be offline (say afterhours)
sp_detach_db/sp_attach_db?
HTH
Jerry
"lindseyhansen" <lindsey.hansen@.fmc-na.com> wrote in message
news:1128614409.695658.177570@.o13g2000cwo.googlegroups.com...
> SQL Server 2000. I have a production database, of which, I want to
> make a copy. I created a DTS with the Copy SQL Server Obj Task to copy
> all objects from MyDbName to MyDbName_Test (on the same instance of SQL
> Server). I've used this method on other databases many times and it
> completes just fine. On this db, however, I get "Invalid object name
> 'dbo.vwWhereUsed'" when trying to complete the task. vwWhereUsed is, of
> course, one of my views. This view functions properly when ran. I
> later found that the error seemed to be happening when the DTS attempts
> to copy another view that calls vwWhereUsed. This other view does not
> get copied to MyDbName_Test before the DTS fails, but vwWhereUsed is
> copied.
> My thought was that the other view is being copied to the new db before
> vwWhereUsed and blowing up because vwWhereUsed is not there yet... but
> from what I just explained, that doesn't seem to be the case.
> On another DTS attempt to move a few tables,that have nothing to do
> with vwWhereUsed, into a new clean database (MyDBName_Test) I got the
> same error message (Invalid object name 'dbo.vwWhereUsed').
> Interestingly enough, if I UNcheck the "Drop Destination Objects First"
> option before moving those tables, the error does not occur. This does
> not make sense, because it was a NEW db.. there was nothing to DROP.
>
> Is there something I'm not seeing here? or..
> Is there techniques to help me discover exactly whats happening.. or
> any tips on making copies of databases using the Copy SQL Server Object
> Task that may help correct this issue?
> TIA
>|||Thanks Jerry.. I haven't tried that before.. I'll give it a shot. It
still makes me nervous, however, that I can't get the dts to complete
successfully. I've run the dbcc check on the database and everything
is fine. I'm not sure what else to look at.
Thanks, though.

"Invalid Object.." error when using Copy SQL Server Objects task

SQL Server 2000. I have a production database, of which, I want to
make a copy. I created a DTS with the Copy SQL Server Obj Task to copy
all objects from MyDbName to MyDbName_Test (on the same instance of SQL
Server). I've used this method on other databases many times and it
completes just fine. On this db, however, I get "Invalid object name
'dbo.vwWhereUsed'" when trying to complete the task. vwWhereUsed is, of
course, one of my views. This view functions properly when ran. I
later found that the error seemed to be happening when the DTS attempts
to copy another view that calls vwWhereUsed. This other view does not
get copied to MyDbName_Test before the DTS fails, but vwWhereUsed is
copied.
My thought was that the other view is being copied to the new db before
vwWhereUsed and blowing up because vwWhereUsed is not there yet... but
from what I just explained, that doesn't seem to be the case.
On another DTS attempt to move a few tables,that have nothing to do
with vwWhereUsed, into a new clean database (MyDBName_Test) I got the
same error message (Invalid object name 'dbo.vwWhereUsed').
Interestingly enough, if I UNcheck the "Drop Destination Objects First"
option before moving those tables, the error does not occur. This does
not make sense, because it was a NEW db.. there was nothing to DROP.
Is there something I'm not seeing here? or..
Is there techniques to help me discover exactly whats happening.. or
any tips on making copies of databases using the Copy SQL Server Object
Task that may help correct this issue?
TIA
Lindsey,
Seems like a lot of unnecessary work. Why not use a BACKUP/RESTORE
approach? Or if the DB can be offline (say afterhours)
sp_detach_db/sp_attach_db?
HTH
Jerry
"lindseyhansen" <lindsey.hansen@.fmc-na.com> wrote in message
news:1128614409.695658.177570@.o13g2000cwo.googlegr oups.com...
> SQL Server 2000. I have a production database, of which, I want to
> make a copy. I created a DTS with the Copy SQL Server Obj Task to copy
> all objects from MyDbName to MyDbName_Test (on the same instance of SQL
> Server). I've used this method on other databases many times and it
> completes just fine. On this db, however, I get "Invalid object name
> 'dbo.vwWhereUsed'" when trying to complete the task. vwWhereUsed is, of
> course, one of my views. This view functions properly when ran. I
> later found that the error seemed to be happening when the DTS attempts
> to copy another view that calls vwWhereUsed. This other view does not
> get copied to MyDbName_Test before the DTS fails, but vwWhereUsed is
> copied.
> My thought was that the other view is being copied to the new db before
> vwWhereUsed and blowing up because vwWhereUsed is not there yet... but
> from what I just explained, that doesn't seem to be the case.
> On another DTS attempt to move a few tables,that have nothing to do
> with vwWhereUsed, into a new clean database (MyDBName_Test) I got the
> same error message (Invalid object name 'dbo.vwWhereUsed').
> Interestingly enough, if I UNcheck the "Drop Destination Objects First"
> option before moving those tables, the error does not occur. This does
> not make sense, because it was a NEW db.. there was nothing to DROP.
>
> Is there something I'm not seeing here? or..
> Is there techniques to help me discover exactly whats happening.. or
> any tips on making copies of databases using the Copy SQL Server Object
> Task that may help correct this issue?
> TIA
>
|||Thanks Jerry.. I haven't tried that before.. I'll give it a shot. It
still makes me nervous, however, that I can't get the dts to complete
successfully. I've run the dbcc check on the database and everything
is fine. I'm not sure what else to look at.
Thanks, though.

"Invalid Object.." error when using Copy SQL Server Objects task

SQL Server 2000. I have a production database, of which, I want to
make a copy. I created a DTS with the Copy SQL Server Obj Task to copy
all objects from MyDbName to MyDbName_Test (on the same instance of SQL
Server). I've used this method on other databases many times and it
completes just fine. On this db, however, I get "Invalid object name
'dbo.vwWhereUsed'" when trying to complete the task. vwWhereUsed is, of
course, one of my views. This view functions properly when ran. I
later found that the error seemed to be happening when the DTS attempts
to copy another view that calls vwWhereUsed. This other view does not
get copied to MyDbName_Test before the DTS fails, but vwWhereUsed is
copied.
My thought was that the other view is being copied to the new db before
vwWhereUsed and blowing up because vwWhereUsed is not there yet... but
from what I just explained, that doesn't seem to be the case.
On another DTS attempt to move a few tables,that have nothing to do
with vwWhereUsed, into a new clean database (MyDBName_Test) I got the
same error message (Invalid object name 'dbo.vwWhereUsed').
Interestingly enough, if I UNcheck the "Drop Destination Objects First"
option before moving those tables, the error does not occur. This does
not make sense, because it was a NEW db.. there was nothing to DROP.
Is there something I'm not seeing here? or..
Is there techniques to help me discover exactly whats happening.. or
any tips on making copies of databases using the Copy SQL Server Object
Task that may help correct this issue?
TIALindsey,
Seems like a lot of unnecessary work. Why not use a BACKUP/RESTORE
approach? Or if the DB can be offline (say afterhours)
sp_detach_db/sp_attach_db?
HTH
Jerry
"lindseyhansen" <lindsey.hansen@.fmc-na.com> wrote in message
news:1128614409.695658.177570@.o13g2000cwo.googlegroups.com...
> SQL Server 2000. I have a production database, of which, I want to
> make a copy. I created a DTS with the Copy SQL Server Obj Task to copy
> all objects from MyDbName to MyDbName_Test (on the same instance of SQL
> Server). I've used this method on other databases many times and it
> completes just fine. On this db, however, I get "Invalid object name
> 'dbo.vwWhereUsed'" when trying to complete the task. vwWhereUsed is, of
> course, one of my views. This view functions properly when ran. I
> later found that the error seemed to be happening when the DTS attempts
> to copy another view that calls vwWhereUsed. This other view does not
> get copied to MyDbName_Test before the DTS fails, but vwWhereUsed is
> copied.
> My thought was that the other view is being copied to the new db before
> vwWhereUsed and blowing up because vwWhereUsed is not there yet... but
> from what I just explained, that doesn't seem to be the case.
> On another DTS attempt to move a few tables,that have nothing to do
> with vwWhereUsed, into a new clean database (MyDBName_Test) I got the
> same error message (Invalid object name 'dbo.vwWhereUsed').
> Interestingly enough, if I UNcheck the "Drop Destination Objects First"
> option before moving those tables, the error does not occur. This does
> not make sense, because it was a NEW db.. there was nothing to DROP.
>
> Is there something I'm not seeing here? or..
> Is there techniques to help me discover exactly whats happening.. or
> any tips on making copies of databases using the Copy SQL Server Object
> Task that may help correct this issue?
> TIA
>|||Thanks Jerry.. I haven't tried that before.. I'll give it a shot. It
still makes me nervous, however, that I can't get the dts to complete
successfully. I've run the dbcc check on the database and everything
is fine. I'm not sure what else to look at.
Thanks, though.

"Drop User" statement does not seem to work

I restored a copy of the production database onto the staging db server. Som
e
of the production database users which need to be removed did not seem to
work when I issued "drop user [username]" statement. I also tried
"sp_dropuser [username]" and that did not work either. Has anyone encoun
tered
this issue? Thanks.Check out sp_change_users_login in the BOL.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"Andrew" <Andrew@.discussions.microsoft.com> wrote in message
news:FF46C63C-56E8-41F7-B238-2E0DA602E209@.microsoft.com...
I restored a copy of the production database onto the staging db server.
Some
of the production database users which need to be removed did not seem to
work when I issued "drop user [username]" statement. I also tried
"sp_dropuser [username]" and that did not work either. Has anyone
encountered
this issue? Thanks.