Hi
I have created a database maintenance plan which includes rebuilding indexes
and checkdb. For one of the databases I get the following error:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options have
incorrect settings: 'QUOTED_IDENTIFIER'.
Does anyone know how I can resolve this?
TIA!
Hi
Have a look at the following:
http://support.microsoft.com/default...b;en-us;301292
http://support.microsoft.com/default...b;en-us;902388
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"N" wrote:
> Hi
> I have created a database maintenance plan which includes rebuilding indexes
> and checkdb. For one of the databases I get the following error:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
> Server Driver][SQL Server]DBCC failed because the following SET options have
> incorrect settings: 'QUOTED_IDENTIFIER'.
> Does anyone know how I can resolve this?
> TIA!
>
sql
Showing posts with label databases. Show all posts
Showing posts with label databases. Show all posts
Monday, March 26, 2012
Error when rebuilding indexes
Hi
I have created a database maintenance plan which includes rebuilding indexes
and checkdb. For one of the databases I get the following error:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]&#
91;ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options
have
incorrect settings: 'QUOTED_IDENTIFIER'.
Does anyone know how I can resolve this?
TIA!Hi
Have a look at the following:
http://support.microsoft.com/defaul...kb;en-us;301292
http://support.microsoft.com/defaul...kb;en-us;902388
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"N" wrote:
> Hi
> I have created a database maintenance plan which includes rebuilding index
es
> and checkdb. For one of the databases I get the following error:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]
[ODBC SQL
> Server Driver][SQL Server]DBCC failed because the following SET option
s have
> incorrect settings: 'QUOTED_IDENTIFIER'.
> Does anyone know how I can resolve this?
> TIA!
>
I have created a database maintenance plan which includes rebuilding indexes
and checkdb. For one of the databases I get the following error:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]&#
91;ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options
have
incorrect settings: 'QUOTED_IDENTIFIER'.
Does anyone know how I can resolve this?
TIA!Hi
Have a look at the following:
http://support.microsoft.com/defaul...kb;en-us;301292
http://support.microsoft.com/defaul...kb;en-us;902388
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"N" wrote:
> Hi
> I have created a database maintenance plan which includes rebuilding index
es
> and checkdb. For one of the databases I get the following error:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]
[ODBC SQL
> Server Driver][SQL Server]DBCC failed because the following SET option
s have
> incorrect settings: 'QUOTED_IDENTIFIER'.
> Does anyone know how I can resolve this?
> TIA!
>
Error when rebuilding indexes
Hi
I have created a database maintenance plan which includes rebuilding indexes
and checkdb. For one of the databases I get the following error:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options have
incorrect settings: 'QUOTED_IDENTIFIER'.
Does anyone know how I can resolve this?
TIA!Hi
Have a look at the following:
http://support.microsoft.com/default.aspx?scid=kb;en-us;301292
http://support.microsoft.com/default.aspx?scid=kb;en-us;902388
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"N" wrote:
> Hi
> I have created a database maintenance plan which includes rebuilding indexes
> and checkdb. For one of the databases I get the following error:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
> Server Driver][SQL Server]DBCC failed because the following SET options have
> incorrect settings: 'QUOTED_IDENTIFIER'.
> Does anyone know how I can resolve this?
> TIA!
>
I have created a database maintenance plan which includes rebuilding indexes
and checkdb. For one of the databases I get the following error:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options have
incorrect settings: 'QUOTED_IDENTIFIER'.
Does anyone know how I can resolve this?
TIA!Hi
Have a look at the following:
http://support.microsoft.com/default.aspx?scid=kb;en-us;301292
http://support.microsoft.com/default.aspx?scid=kb;en-us;902388
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"N" wrote:
> Hi
> I have created a database maintenance plan which includes rebuilding indexes
> and checkdb. For one of the databases I get the following error:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
> Server Driver][SQL Server]DBCC failed because the following SET options have
> incorrect settings: 'QUOTED_IDENTIFIER'.
> Does anyone know how I can resolve this?
> TIA!
>
Error when opening Maintenance Plan in SQL 2000
I've recently installed SQL 2000 on a new server. Migrated production
databases and data from old SQL 6.5.
Everything checks out OK applications work fine, all data
came over no problem. However... when I try to open or create a
database maintenance plan I get is error:
Microsoft SQL-DMO (ODBC SQLState: 42S22)
Error 207: Invalid column name 'category_id'.
Invalid column name 'netsend_address'.
Invalid column name 'last_netsend_date'.
Invalid column name 'last_netsend_time'.
these colune names do not exist, do I need to create them and if so,
which table do they need to be in? Any help is greatly appreciated. ThanksHI;
Columns mentioned below are in the sysoperators table in msdb database
netsend_address nvarchar 100 NOT NULL
last_netsend_date int 4 NULL
last_netsend_time int 4 NULL
category_id int 4 NULL
IT Looks to me that something happend to your msdb database.
Do you have a backup to restore it from before migration?
--
Danijel Novak
"Lisa Hoffman" <LisaHoffman@.reish.com> wrote in message
news:OH0vej2BGHA.3584@.TK2MSFTNGP11.phx.gbl...
> I've recently installed SQL 2000 on a new server. Migrated production
> databases and data from old SQL 6.5.
> Everything checks out OK applications work fine, all data
> came over no problem. However... when I try to open or create a
> database maintenance plan I get is error:
> Microsoft SQL-DMO (ODBC SQLState: 42S22)
> Error 207: Invalid column name 'category_id'.
> Invalid column name 'netsend_address'.
> Invalid column name 'last_netsend_date'.
> Invalid column name 'last_netsend_time'.
> these colune names do not exist, do I need to create them and if so, which
> table do they need to be in? Any help is greatly appreciated. Thanks
>|||Hi Lisa
You may want to run a DBCC CHECKCATALOG or DBCC CHECKDB on your MSDB database.
If you need to restore MSDB check out
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_bkprst_2w1f.asp
John
"Lisa Hoffman" wrote:
> I've recently installed SQL 2000 on a new server. Migrated production
> databases and data from old SQL 6.5.
> Everything checks out OK applications work fine, all data
> came over no problem. However... when I try to open or create a
> database maintenance plan I get is error:
> Microsoft SQL-DMO (ODBC SQLState: 42S22)
> Error 207: Invalid column name 'category_id'.
> Invalid column name 'netsend_address'.
> Invalid column name 'last_netsend_date'.
> Invalid column name 'last_netsend_time'.
> these colune names do not exist, do I need to create them and if so,
> which table do they need to be in? Any help is greatly appreciated. Thanks
>
>|||The MS article states "The model and msdb databases can only be restored
from backups created on a Microsoft® SQL Server� 2000 server. Restore of
backups of these databases made on SQL Server version 7.0 or earlier is
not supported."
This was a migration from 6.5 (and I do not have access to this db
anymore). Any other suggestions?
John Bell wrote:
> Hi Lisa
> You may want to run a DBCC CHECKCATALOG or DBCC CHECKDB on your MSDB database.
> If you need to restore MSDB check out
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_bkprst_2w1f.asp
> John
> "Lisa Hoffman" wrote:
>
>>I've recently installed SQL 2000 on a new server. Migrated production
>>databases and data from old SQL 6.5.
>>Everything checks out OK applications work fine, all data
>>came over no problem. However... when I try to open or create a
>>database maintenance plan I get is error:
>>Microsoft SQL-DMO (ODBC SQLState: 42S22)
>>Error 207: Invalid column name 'category_id'.
>>Invalid column name 'netsend_address'.
>>Invalid column name 'last_netsend_date'.
>>Invalid column name 'last_netsend_time'.
>>these colune names do not exist, do I need to create them and if so,
>>which table do they need to be in? Any help is greatly appreciated. Thanks
>>|||Hi
I would assume that MSDB was backed up after your installation and therefore
it could be resumed to it's previous state? Any jobs etc should be reviewed
and manually re-created.
John
"Lisa Hoffman" wrote:
> The MS article states "The model and msdb databases can only be restored
> from backups created on a Microsoft® SQL Server� 2000 server. Restore of
> backups of these databases made on SQL Server version 7.0 or earlier is
> not supported."
> This was a migration from 6.5 (and I do not have access to this db
> anymore). Any other suggestions?
> John Bell wrote:
> > Hi Lisa
> >
> > You may want to run a DBCC CHECKCATALOG or DBCC CHECKDB on your MSDB database.
> >
> > If you need to restore MSDB check out
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_bkprst_2w1f.asp
> >
> > John
> >
> > "Lisa Hoffman" wrote:
> >
> >
> >>I've recently installed SQL 2000 on a new server. Migrated production
> >>databases and data from old SQL 6.5.
> >>Everything checks out OK applications work fine, all data
> >>came over no problem. However... when I try to open or create a
> >>database maintenance plan I get is error:
> >>
> >>Microsoft SQL-DMO (ODBC SQLState: 42S22)
> >>Error 207: Invalid column name 'category_id'.
> >>Invalid column name 'netsend_address'.
> >>Invalid column name 'last_netsend_date'.
> >>Invalid column name 'last_netsend_time'.
> >>
> >>these colune names do not exist, do I need to create them and if so,
> >>which table do they need to be in? Any help is greatly appreciated. Thanks
> >>
> >>
> >>
>
databases and data from old SQL 6.5.
Everything checks out OK applications work fine, all data
came over no problem. However... when I try to open or create a
database maintenance plan I get is error:
Microsoft SQL-DMO (ODBC SQLState: 42S22)
Error 207: Invalid column name 'category_id'.
Invalid column name 'netsend_address'.
Invalid column name 'last_netsend_date'.
Invalid column name 'last_netsend_time'.
these colune names do not exist, do I need to create them and if so,
which table do they need to be in? Any help is greatly appreciated. ThanksHI;
Columns mentioned below are in the sysoperators table in msdb database
netsend_address nvarchar 100 NOT NULL
last_netsend_date int 4 NULL
last_netsend_time int 4 NULL
category_id int 4 NULL
IT Looks to me that something happend to your msdb database.
Do you have a backup to restore it from before migration?
--
Danijel Novak
"Lisa Hoffman" <LisaHoffman@.reish.com> wrote in message
news:OH0vej2BGHA.3584@.TK2MSFTNGP11.phx.gbl...
> I've recently installed SQL 2000 on a new server. Migrated production
> databases and data from old SQL 6.5.
> Everything checks out OK applications work fine, all data
> came over no problem. However... when I try to open or create a
> database maintenance plan I get is error:
> Microsoft SQL-DMO (ODBC SQLState: 42S22)
> Error 207: Invalid column name 'category_id'.
> Invalid column name 'netsend_address'.
> Invalid column name 'last_netsend_date'.
> Invalid column name 'last_netsend_time'.
> these colune names do not exist, do I need to create them and if so, which
> table do they need to be in? Any help is greatly appreciated. Thanks
>|||Hi Lisa
You may want to run a DBCC CHECKCATALOG or DBCC CHECKDB on your MSDB database.
If you need to restore MSDB check out
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_bkprst_2w1f.asp
John
"Lisa Hoffman" wrote:
> I've recently installed SQL 2000 on a new server. Migrated production
> databases and data from old SQL 6.5.
> Everything checks out OK applications work fine, all data
> came over no problem. However... when I try to open or create a
> database maintenance plan I get is error:
> Microsoft SQL-DMO (ODBC SQLState: 42S22)
> Error 207: Invalid column name 'category_id'.
> Invalid column name 'netsend_address'.
> Invalid column name 'last_netsend_date'.
> Invalid column name 'last_netsend_time'.
> these colune names do not exist, do I need to create them and if so,
> which table do they need to be in? Any help is greatly appreciated. Thanks
>
>|||The MS article states "The model and msdb databases can only be restored
from backups created on a Microsoft® SQL Server� 2000 server. Restore of
backups of these databases made on SQL Server version 7.0 or earlier is
not supported."
This was a migration from 6.5 (and I do not have access to this db
anymore). Any other suggestions?
John Bell wrote:
> Hi Lisa
> You may want to run a DBCC CHECKCATALOG or DBCC CHECKDB on your MSDB database.
> If you need to restore MSDB check out
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_bkprst_2w1f.asp
> John
> "Lisa Hoffman" wrote:
>
>>I've recently installed SQL 2000 on a new server. Migrated production
>>databases and data from old SQL 6.5.
>>Everything checks out OK applications work fine, all data
>>came over no problem. However... when I try to open or create a
>>database maintenance plan I get is error:
>>Microsoft SQL-DMO (ODBC SQLState: 42S22)
>>Error 207: Invalid column name 'category_id'.
>>Invalid column name 'netsend_address'.
>>Invalid column name 'last_netsend_date'.
>>Invalid column name 'last_netsend_time'.
>>these colune names do not exist, do I need to create them and if so,
>>which table do they need to be in? Any help is greatly appreciated. Thanks
>>|||Hi
I would assume that MSDB was backed up after your installation and therefore
it could be resumed to it's previous state? Any jobs etc should be reviewed
and manually re-created.
John
"Lisa Hoffman" wrote:
> The MS article states "The model and msdb databases can only be restored
> from backups created on a Microsoft® SQL Server� 2000 server. Restore of
> backups of these databases made on SQL Server version 7.0 or earlier is
> not supported."
> This was a migration from 6.5 (and I do not have access to this db
> anymore). Any other suggestions?
> John Bell wrote:
> > Hi Lisa
> >
> > You may want to run a DBCC CHECKCATALOG or DBCC CHECKDB on your MSDB database.
> >
> > If you need to restore MSDB check out
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_bkprst_2w1f.asp
> >
> > John
> >
> > "Lisa Hoffman" wrote:
> >
> >
> >>I've recently installed SQL 2000 on a new server. Migrated production
> >>databases and data from old SQL 6.5.
> >>Everything checks out OK applications work fine, all data
> >>came over no problem. However... when I try to open or create a
> >>database maintenance plan I get is error:
> >>
> >>Microsoft SQL-DMO (ODBC SQLState: 42S22)
> >>Error 207: Invalid column name 'category_id'.
> >>Invalid column name 'netsend_address'.
> >>Invalid column name 'last_netsend_date'.
> >>Invalid column name 'last_netsend_time'.
> >>
> >>these colune names do not exist, do I need to create them and if so,
> >>which table do they need to be in? Any help is greatly appreciated. Thanks
> >>
> >>
> >>
>
Friday, March 9, 2012
Error when accessing sample databases
Hey, Everyone - I have downloaded two of the sample databases and get the following error when I attempt to open them:
Unable to open the physical file "c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\Assets_Maintenance_log.ldf". Operating system error 2: "2(The system cannot find the file specified.)". (Microsoft SQL Server, Error: 5120)
So what am I doing wrong? The install of these sample databases is simple and straight-forward.
Thansk!
Regards,
Bob Mitchell
Hi,
The database file won't open this way, you have to go through the SQL Server Management studio, the file you are trying to open is ldf (Transaction Log file).
If you have just copied/extracted .mdf and .ldf files then you need to attach them using your SQL Server Management Studio, to do this
Open your SQL Server Management Studio -> Login to your Server -> Expand your server-> Expand Database Folder -> right click on Database folder -> click on attach-> select the .mdf file from the location you copied/extracted database files-> ok
this will attach database to your server, then you need to query it through query analyzer window or you may browse/open table from management studio.
Feel free to ask if you have more doubts
HTH
|||refer this link
Running Setup to Install AdventureWorks Sample Databases and Samples :
http://msdn2.microsoft.com/en-us/library/ms143804.aspx
Madhu
|||Thanks for the quick replies! Unfortunately, I'm still having the same problem.
I download the database executable, sse-dm_01.EXE and run it. I select my H drive for the install. The executable extracts 5 files to the folder I have chosen. None of them is a *.ldf file.
When I go to attach the database, I get the error that file c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\Assets_Maintenance_log.ldf cannot be found.
What I find confusing is that no *.ldf file is even extracted so even if I were able to point the attach to the H drive for the ldf file, it still would not find it.
Still need some help!!!
Thanks!
Regards,
Bob Mitchell
|||
Bob,
Have you found a solution to this problem?
I have been struggling with this same problem for a long time tonight, but I finally found the solution.
On the list of files at the bottom of the Attach Database screen delete the reference to the xxxxxxxx-log.ldf file that is listed as "Not Found." You can delete the reference to the file by selecting it and then pressing the Remove button. Once you have deleted the file then go ahead and click OK to complete the attachment to the database.
Hope this helps. It worked on the couple of samples I downloaded.
-eric
Error when accessing sample databases
Hey, Everyone - I have downloaded two of the sample databases and get the following error when I attempt to open them:
Unable to open the physical file "c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\Assets_Maintenance_log.ldf". Operating system error 2: "2(The system cannot find the file specified.)". (Microsoft SQL Server, Error: 5120)
So what am I doing wrong? The install of these sample databases is simple and straight-forward.
Thansk!
Regards,
Bob Mitchell
Hi,
The database file won't open this way, you have to go through the SQL Server Management studio, the file you are trying to open is ldf (Transaction Log file).
If you have just copied/extracted .mdf and .ldf files then you need to attach them using your SQL Server Management Studio, to do this
Open your SQL Server Management Studio -> Login to your Server -> Expand your server-> Expand Database Folder -> right click on Database folder -> click on attach-> select the .mdf file from the location you copied/extracted database files-> ok
this will attach database to your server, then you need to query it through query analyzer window or you may browse/open table from management studio.
Feel free to ask if you have more doubts
HTH
|||refer this link
Running Setup to Install AdventureWorks Sample Databases and Samples :
http://msdn2.microsoft.com/en-us/library/ms143804.aspx
Madhu
|||Thanks for the quick replies! Unfortunately, I'm still having the same problem.
I download the database executable, sse-dm_01.EXE and run it. I select my H drive for the install. The executable extracts 5 files to the folder I have chosen. None of them is a *.ldf file.
When I go to attach the database, I get the error that file c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\Assets_Maintenance_log.ldf cannot be found.
What I find confusing is that no *.ldf file is even extracted so even if I were able to point the attach to the H drive for the ldf file, it still would not find it.
Still need some help!!!
Thanks!
Regards,
Bob Mitchell
|||
Bob,
Have you found a solution to this problem?
I have been struggling with this same problem for a long time tonight, but I finally found the solution.
On the list of files at the bottom of the Attach Database screen delete the reference to the xxxxxxxx-log.ldf file that is listed as "Not Found." You can delete the reference to the file by selecting it and then pressing the Remove button. Once you have deleted the file then go ahead and click OK to complete the attachment to the database.
Hope this helps. It worked on the couple of samples I downloaded.
-eric
Friday, February 24, 2012
Error trying to create cube partition
I've converted 4 AS2000 databases to AS2005. In just one of these databases, I am not able to add any partitions to any of the cubes. As soon as I click the "New Partition" link, get the following error:
The wizard will close because of the following error: An item with the same key has already been added (mscorlib).
I get this error if I try to create a parition from either Visual Studio 2005 or SQL Server Management Studio. AS2005 version is 9.00.2047.00. I can add paritions to cubes in other databases on the same server.
I've been all over looking for help on this, with no luck at all.
If anyone can help me, I'd sure appreciate it.
Most likely something went wrong with the database during migration.
It is possible your database had some problems even before migrated and then migration wizard created AS2005 database with the wrong structure.
It is hard to say what exactly you are having. First go through your AS2000 database structure and make sure it is all valid. Make sure you got the latest AS2000 service pack.
Then migrate your database again and try creating a new AS2005 project based on migrated database. You do that by going through new project wizard and selecting "Import Analysis Ser...."
Go through your new database, open every object in editor and make sure there are no errors and all the object relationships are set right. One area is to pay attention is Dimensions Usage tab in cube editor.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
I've checked the AS2000 datbase structures and it's all valid: cubes, dimenions, security roles, partitions, data. Everything there checks out from Analysis Manager as well as from our front-end application that uses OWC to connect to these cubes. The latest service pack is installed.
I have checked all of the objects in the AS2005 databases. There are no errors, and the cubes function properly.
I could migrate the database again, but it's got over 150 cubes, and over 400 seucirty roles. I really hate to do it unless I absolutely have to. Thanks for your suggestion...it may be my last resort.
Sunday, February 19, 2012
Error starting the SQL service after renaming one of the log files..
Is there anyone out there who can help me ? Please ? ?
The log file for one of the MSSQL 2000 databases ha grown really big.
(15 GB)
After setting a limit on the size to grow, the log file date did not
modifie.
After a few weaks I stopped the SQL service, and renamed the log file.
When I was trying to start the SQL again, it would not start. Even
not when I gave the log file back its old name.
Is there any way to restart / restore the SQL service / database
without a backup ? ?
Regards,
ØivindWhen you try to start the service, what message do you get?
"oeej" <oeej@.netpower.no> wrote in message
news:ca674822.0309071518.24feabb9@.posting.google.com...
> Is there anyone out there who can help me ? Please ? ?
> The log file for one of the MSSQL 2000 databases ha grown really big.
> (15 GB)
> After setting a limit on the size to grow, the log file date did not
> modifie.
> After a few weaks I stopped the SQL service, and renamed the log file.
> When I was trying to start the SQL again, it would not start. Even
> not when I gave the log file back its old name.
> Is there any way to restart / restore the SQL service / database
> without a backup ? ?
> Regards,
> Øivind|||If the error messages are correct... simply
Restore database model with recovery
Restore database axdb with recovery
the error messages say you have started a recovery that was not completed..
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"oeej" <oeej@.netpower.no> wrote in message
news:ca674822.0309071518.24feabb9@.posting.google.com...
> Is there anyone out there who can help me ? Please ? ?
> The log file for one of the MSSQL 2000 databases ha grown really big.
> (15 GB)
> After setting a limit on the size to grow, the log file date did not
> modifie.
> After a few weaks I stopped the SQL service, and renamed the log file.
> When I was trying to start the SQL again, it would not start. Even
> not when I gave the log file back its old name.
> Is there any way to restart / restore the SQL service / database
> without a backup ? ?
> Regards,
> Øivind
The log file for one of the MSSQL 2000 databases ha grown really big.
(15 GB)
After setting a limit on the size to grow, the log file date did not
modifie.
After a few weaks I stopped the SQL service, and renamed the log file.
When I was trying to start the SQL again, it would not start. Even
not when I gave the log file back its old name.
Is there any way to restart / restore the SQL service / database
without a backup ? ?
Regards,
ØivindWhen you try to start the service, what message do you get?
"oeej" <oeej@.netpower.no> wrote in message
news:ca674822.0309071518.24feabb9@.posting.google.com...
> Is there anyone out there who can help me ? Please ? ?
> The log file for one of the MSSQL 2000 databases ha grown really big.
> (15 GB)
> After setting a limit on the size to grow, the log file date did not
> modifie.
> After a few weaks I stopped the SQL service, and renamed the log file.
> When I was trying to start the SQL again, it would not start. Even
> not when I gave the log file back its old name.
> Is there any way to restart / restore the SQL service / database
> without a backup ? ?
> Regards,
> Øivind|||If the error messages are correct... simply
Restore database model with recovery
Restore database axdb with recovery
the error messages say you have started a recovery that was not completed..
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"oeej" <oeej@.netpower.no> wrote in message
news:ca674822.0309071518.24feabb9@.posting.google.com...
> Is there anyone out there who can help me ? Please ? ?
> The log file for one of the MSSQL 2000 databases ha grown really big.
> (15 GB)
> After setting a limit on the size to grow, the log file date did not
> modifie.
> After a few weaks I stopped the SQL service, and renamed the log file.
> When I was trying to start the SQL again, it would not start. Even
> not when I gave the log file back its old name.
> Is there any way to restart / restore the SQL service / database
> without a backup ? ?
> Regards,
> Øivind
Wednesday, February 15, 2012
error running ssis package
Hello.
I run a ssis package of transferring data between sql2005 databases.
I get this error:
Code Snippet
Error: 0xC002F325 at CopyTables2, Transfer SQL Server Objects Task: Execution failed with the following error:
"ERROR : errorCode=-1071636471 description=An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description:
"Could not continue scan with NOLOCK due to data movement.".
helpFile=dtsmsg.rll helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}".
Task failed: CopyTables2
i run the package currently with right click on the package on the BIDS.
what is the reason for this error? how can I check it?
Thanks.
Check if it works y removing the WITH (NOLOCK) hint.
Virendra
|||where or how can i remove it (remove the with nolock hint)?
|||In the adapter where you have selected the tables as source and destination try setting the property Table Lock to true (check the check box - Table Lock).
Virendra
|||thanks for your answer.
i'm sorry, i dont find it. i configured the transfer sql server object from the Bids.
i didnt see there Table Lock property.
where is it exactly?
Thanks.
|||You are using the OLE DB Source and Destination adapter right? There when you select the table - fast load option you have the Table Lock check box. Check this.
Virendra
|||
Virendra Wadekar wrote:
You are using the OLE DB Source and Destination adapter right?
No, the OP is using the Transfer SQL Server Objects task. I don't see a way to set the table lock options on this task. You might have to use data flows to do this, or schedule the package to run at a time when data isn't being updated.
Subscribe to:
Posts (Atom)