SQL tool for MSDE: restoring

Showing posts with label restoring. Show all posts

Sunday, February 19, 2012

After restoring the Database getting this message "Cannot Modify record"

Good Morning Friends
I am in real soup. I am new to SQL server 7.0 and Visual basic 6.0. I
have got one application developed by some software agency using VB 6.0
and sql server 7.0. Since last 6 years everything worked
Three days my SQLserver machine crashed because of hard disk failure.
After much effort of two days I restored all the data from the
backup.In our Application primarily there are two sections Members and
Agency. Everything working fine in the Members section i.e browsing,
modification, deletion of records etc. But in the agency section only
browsing of record is working if I want to Edit the record and then
press the save button it gives the error message " Cannot Modify
Record, Please close the screen and reopen. All changes will be lost."
Actions Taken till now:
1. Change the deafult db to "ABC" for the user "CFC" Logging into the
SQLserver. This was the arrangement before crashing.
2. Granted the server role "db owner", "db creator" to the user "CFC".
3. Checked the tables permission of Members section (Where Modify is
working) as well as agency section (Where Modify is not working), both
the tables have same kind of permission.
4. Tried to get answer on google but of no help.
Please help me urgently.
Thanks
Deepak SinhaSo the application is not reporting the actual SQL Server error message?
Without that information, you are shooting in the dark. I suggest you run a
SQL Profiler trace and also include Errors/Exceptions. This will hopefully
help identify the cause of the error.
You mention that you restored from backup. Was this a SQL Server backup?
Did you reinstall SQL Server?
--
Hope this helps.
Dan Guzman
SQL Server MVP
"microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in message
news:1154755197.215422.79810@.75g2000cwc.googlegroups.com...
> Good Morning Friends
> I am in real soup. I am new to SQL server 7.0 and Visual basic 6.0. I
> have got one application developed by some software agency using VB 6.0
> and sql server 7.0. Since last 6 years everything worked
> Three days my SQLserver machine crashed because of hard disk failure.
> After much effort of two days I restored all the data from the
> backup.In our Application primarily there are two sections Members and
> Agency. Everything working fine in the Members section i.e browsing,
> modification, deletion of records etc. But in the agency section only
> browsing of record is working if I want to Edit the record and then
> press the save button it gives the error message " Cannot Modify
> Record, Please close the screen and reopen. All changes will be lost."
> Actions Taken till now:
> 1. Change the deafult db to "ABC" for the user "CFC" Logging into the
> SQLserver. This was the arrangement before crashing.
> 2. Granted the server role "db owner", "db creator" to the user "CFC".
> 3. Checked the tables permission of Members section (Where Modify is
> working) as well as agency section (Where Modify is not working), both
> the tables have same kind of permission.
> 4. Tried to get answer on google but of no help.
> Please help me urgently.
> Thanks
> Deepak Sinha
>|||Thanks for ur reply Guzman.
1. Yes It was a SQL server backup
2. I did not reinstall SQL server .
I will run a SQL profiler trace and get back.
Thanks again.
Deepak
Dan Guzman wrote:
> So the application is not reporting the actual SQL Server error message?
> Without that information, you are shooting in the dark. I suggest you run a
> SQL Profiler trace and also include Errors/Exceptions. This will hopefully
> help identify the cause of the error.
> You mention that you restored from backup. Was this a SQL Server backup?
> Did you reinstall SQL Server?
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in message
> news:1154755197.215422.79810@.75g2000cwc.googlegroups.com...
> > Good Morning Friends
> >
> > I am in real soup. I am new to SQL server 7.0 and Visual basic 6.0. I
> > have got one application developed by some software agency using VB 6.0
> > and sql server 7.0. Since last 6 years everything worked
> > Three days my SQLserver machine crashed because of hard disk failure.
> > After much effort of two days I restored all the data from the
> > backup.In our Application primarily there are two sections Members and
> > Agency. Everything working fine in the Members section i.e browsing,
> > modification, deletion of records etc. But in the agency section only
> > browsing of record is working if I want to Edit the record and then
> > press the save button it gives the error message " Cannot Modify
> > Record, Please close the screen and reopen. All changes will be lost."
> > Actions Taken till now:
> > 1. Change the deafult db to "ABC" for the user "CFC" Logging into the
> > SQLserver. This was the arrangement before crashing.
> > 2. Granted the server role "db owner", "db creator" to the user "CFC".
> > 3. Checked the tables permission of Members section (Where Modify is
> > working) as well as agency section (Where Modify is not working), both
> > the tables have same kind of permission.
> > 4. Tried to get answer on google but of no help.
> >
> > Please help me urgently.
> >
> > Thanks
> >
> > Deepak Sinha
> >|||How do I run SQL profiler with Errors/Exceptions included? By "Errors"
do you mean those Errors which I am getting in the application i.e
"Cannot Modify..." ! If yes How do I include this message in the
profiler, becse I do not see there any option for inclusion of my error
message. Please guide.
Deepak
microsoft . public . sqlserver wrote:
> Thanks for ur reply Guzman.
> 1. Yes It was a SQL server backup
> 2. I did not reinstall SQL server .
> I will run a SQL profiler trace and get back.
> Thanks again.
> Deepak
> Dan Guzman wrote:
> > So the application is not reporting the actual SQL Server error message?
> > Without that information, you are shooting in the dark. I suggest you run a
> > SQL Profiler trace and also include Errors/Exceptions. This will hopefully
> > help identify the cause of the error.
> >
> > You mention that you restored from backup. Was this a SQL Server backup?
> > Did you reinstall SQL Server?
> >
> > --
> > Hope this helps.
> >
> > Dan Guzman
> > SQL Server MVP
> >
> > "microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in message
> > news:1154755197.215422.79810@.75g2000cwc.googlegroups.com...
> > > Good Morning Friends
> > >
> > > I am in real soup. I am new to SQL server 7.0 and Visual basic 6.0. I
> > > have got one application developed by some software agency using VB 6.0
> > > and sql server 7.0. Since last 6 years everything worked
> > > Three days my SQLserver machine crashed because of hard disk failure.
> > > After much effort of two days I restored all the data from the
> > > backup.In our Application primarily there are two sections Members and
> > > Agency. Everything working fine in the Members section i.e browsing,
> > > modification, deletion of records etc. But in the agency section only
> > > browsing of record is working if I want to Edit the record and then
> > > press the save button it gives the error message " Cannot Modify
> > > Record, Please close the screen and reopen. All changes will be lost."
> > > Actions Taken till now:
> > > 1. Change the deafult db to "ABC" for the user "CFC" Logging into the
> > > SQLserver. This was the arrangement before crashing.
> > > 2. Granted the server role "db owner", "db creator" to the user "CFC".
> > > 3. Checked the tables permission of Members section (Where Modify is
> > > working) as well as agency section (Where Modify is not working), both
> > > the tables have same kind of permission.
> > > 4. Tried to get answer on google but of no help.
> > >
> > > Please help me urgently.
> > >
> > > Thanks
> > >
> > > Deepak Sinha
> > >|||> How do I run SQL profiler with Errors/Exceptions included? By "Errors"
> do you mean those Errors which I am getting in the application i.e
> "Cannot Modify..." !
The 'Cannot Modify' message is not a SQL Server error message; it is a
generic message generated by the VB6 application, probably in response to a
SQL Server error. Hopefully, the trace will allow you to identify the
actual SQL Server error so that you can take corrective action.
I don't have SQL 7 Profiler available but I believe the steps are similar to
SQL 2000 Profiler. There should be an Errors and Warnings event class.
Include all those events.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in message
news:1154777520.843807.294740@.i3g2000cwc.googlegroups.com...
> How do I run SQL profiler with Errors/Exceptions included? By "Errors"
> do you mean those Errors which I am getting in the application i.e
> "Cannot Modify..." ! If yes How do I include this message in the
> profiler, becse I do not see there any option for inclusion of my error
> message. Please guide.
> Deepak
> microsoft . public . sqlserver wrote:
>> Thanks for ur reply Guzman.
>> 1. Yes It was a SQL server backup
>> 2. I did not reinstall SQL server .
>> I will run a SQL profiler trace and get back.
>> Thanks again.
>> Deepak
>> Dan Guzman wrote:
>> > So the application is not reporting the actual SQL Server error
>> > message?
>> > Without that information, you are shooting in the dark. I suggest you
>> > run a
>> > SQL Profiler trace and also include Errors/Exceptions. This will
>> > hopefully
>> > help identify the cause of the error.
>> >
>> > You mention that you restored from backup. Was this a SQL Server
>> > backup?
>> > Did you reinstall SQL Server?
>> >
>> > --
>> > Hope this helps.
>> >
>> > Dan Guzman
>> > SQL Server MVP
>> >
>> > "microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in message
>> > news:1154755197.215422.79810@.75g2000cwc.googlegroups.com...
>> > > Good Morning Friends
>> > >
>> > > I am in real soup. I am new to SQL server 7.0 and Visual basic 6.0. I
>> > > have got one application developed by some software agency using VB
>> > > 6.0
>> > > and sql server 7.0. Since last 6 years everything worked
>> > > Three days my SQLserver machine crashed because of hard disk failure.
>> > > After much effort of two days I restored all the data from the
>> > > backup.In our Application primarily there are two sections Members
>> > > and
>> > > Agency. Everything working fine in the Members section i.e browsing,
>> > > modification, deletion of records etc. But in the agency section only
>> > > browsing of record is working if I want to Edit the record and then
>> > > press the save button it gives the error message " Cannot Modify
>> > > Record, Please close the screen and reopen. All changes will be
>> > > lost."
>> > > Actions Taken till now:
>> > > 1. Change the deafult db to "ABC" for the user "CFC" Logging into the
>> > > SQLserver. This was the arrangement before crashing.
>> > > 2. Granted the server role "db owner", "db creator" to the user
>> > > "CFC".
>> > > 3. Checked the tables permission of Members section (Where Modify is
>> > > working) as well as agency section (Where Modify is not working),
>> > > both
>> > > the tables have same kind of permission.
>> > > 4. Tried to get answer on google but of no help.
>> > >
>> > > Please help me urgently.
>> > >
>> > > Thanks
>> > >
>> > > Deepak Sinha
>> > >
>|||Sir,
On running SQL profiler with Error/Exceptions included It is showing
"Error: 16821, Severity: 16, State: 1" it is also giving another error
message
"Operating system Error 87., The Parameter is incorrect"
All these error messages in front of the database ID master while my
application is running on the database "ABC"
When I
Dan Guzman wrote:
> > How do I run SQL profiler with Errors/Exceptions included? By "Errors"
> > do you mean those Errors which I am getting in the application i.e
> > "Cannot Modify..." !
> The 'Cannot Modify' message is not a SQL Server error message; it is a
> generic message generated by the VB6 application, probably in response to a
> SQL Server error. Hopefully, the trace will allow you to identify the
> actual SQL Server error so that you can take corrective action.
> I don't have SQL 7 Profiler available but I believe the steps are similar to
> SQL 2000 Profiler. There should be an Errors and Warnings event class.
> Include all those events.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in message
> news:1154777520.843807.294740@.i3g2000cwc.googlegroups.com...
> > How do I run SQL profiler with Errors/Exceptions included? By "Errors"
> > do you mean those Errors which I am getting in the application i.e
> > "Cannot Modify..." ! If yes How do I include this message in the
> > profiler, becse I do not see there any option for inclusion of my error
> > message. Please guide.
> >
> > Deepak
> >
> > microsoft . public . sqlserver wrote:
> >> Thanks for ur reply Guzman.
> >> 1. Yes It was a SQL server backup
> >> 2. I did not reinstall SQL server .
> >>
> >> I will run a SQL profiler trace and get back.
> >> Thanks again.
> >>
> >> Deepak
> >> Dan Guzman wrote:
> >> > So the application is not reporting the actual SQL Server error
> >> > message?
> >> > Without that information, you are shooting in the dark. I suggest you
> >> > run a
> >> > SQL Profiler trace and also include Errors/Exceptions. This will
> >> > hopefully
> >> > help identify the cause of the error.
> >> >
> >> > You mention that you restored from backup. Was this a SQL Server
> >> > backup?
> >> > Did you reinstall SQL Server?
> >> >
> >> > --
> >> > Hope this helps.
> >> >
> >> > Dan Guzman
> >> > SQL Server MVP
> >> >
> >> > "microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in message
> >> > news:1154755197.215422.79810@.75g2000cwc.googlegroups.com...
> >> > > Good Morning Friends
> >> > >
> >> > > I am in real soup. I am new to SQL server 7.0 and Visual basic 6.0. I
> >> > > have got one application developed by some software agency using VB
> >> > > 6.0
> >> > > and sql server 7.0. Since last 6 years everything worked
> >> > > Three days my SQLserver machine crashed because of hard disk failure.
> >> > > After much effort of two days I restored all the data from the
> >> > > backup.In our Application primarily there are two sections Members
> >> > > and
> >> > > Agency. Everything working fine in the Members section i.e browsing,
> >> > > modification, deletion of records etc. But in the agency section only
> >> > > browsing of record is working if I want to Edit the record and then
> >> > > press the save button it gives the error message " Cannot Modify
> >> > > Record, Please close the screen and reopen. All changes will be
> >> > > lost."
> >> > > Actions Taken till now:
> >> > > 1. Change the deafult db to "ABC" for the user "CFC" Logging into the
> >> > > SQLserver. This was the arrangement before crashing.
> >> > > 2. Granted the server role "db owner", "db creator" to the user
> >> > > "CFC".
> >> > > 3. Checked the tables permission of Members section (Where Modify is
> >> > > working) as well as agency section (Where Modify is not working),
> >> > > both
> >> > > the tables have same kind of permission.
> >> > > 4. Tried to get answer on google but of no help.
> >> > >
> >> > > Please help me urgently.
> >> > >
> >> > > Thanks
> >> > >
> >> > > Deepak Sinha
> >> > >
> >|||Dear Sir
I ran the SQL profiler and I got these error messages
1. Error 16821, Severity: 16, state: 1
2. Operating system Error 87., The parameter is incorrect
3. sp_executesql N'UPDATE "INSDB".."INS_M_agency" SET
"reg_code"=@.P1,"agen_name"=@.P2,"agen_place"=@.P3,"estb_date"=@.P4,'', ''
go
When I ran the above SQL statement in the Query Analyzer It is giving
Error message "Server: Msg 170, Level 15, State 1, Line 1"
" Line 1: Incorrect syntax near 'INSDB'."
4. UPDATE "INSDB".."INS_M_agency" SET
"reg_code"=@.P1,"agen_name"=@.P2,"agen_place"=@.P3,"estb_date"=@.P4
g0
5. After the hard disk crash at the time of restoration I got this
Error message "[SQL-DMO] You must be logged in as 'sa' or a member of
sysadmin, or a member of dbcreator" to get rid of this problem I
downloaded SQL server Service pack 2 from microsoft site and installed
it. After the restoration every other part of the application working
except this. I doubt is it because of the service pack 2 ? Can I
upgrade it to service pack 3 or 4 or I can uninstall service pack 2.
Please guide
Thanks
Deepak Sinha
microsoft . public . sqlserver wrote:
> Sir,
> On running SQL profiler with Error/Exceptions included It is showing
> "Error: 16821, Severity: 16, State: 1" it is also giving another error
> message
> "Operating system Error 87., The Parameter is incorrect"
> All these error messages in front of the database ID master while my
> application is running on the database "ABC"
> When I
> Dan Guzman wrote:
> > > How do I run SQL profiler with Errors/Exceptions included? By "Errors"
> > > do you mean those Errors which I am getting in the application i.e
> > > "Cannot Modify..." !
> >
> > The 'Cannot Modify' message is not a SQL Server error message; it is a
> > generic message generated by the VB6 application, probably in response to a
> > SQL Server error. Hopefully, the trace will allow you to identify the
> > actual SQL Server error so that you can take corrective action.
> >
> > I don't have SQL 7 Profiler available but I believe the steps are similar to
> > SQL 2000 Profiler. There should be an Errors and Warnings event class.
> > Include all those events.
> >
> > --
> > Hope this helps.
> >
> > Dan Guzman
> > SQL Server MVP
> >
> > "microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in message
> > news:1154777520.843807.294740@.i3g2000cwc.googlegroups.com...
> > > How do I run SQL profiler with Errors/Exceptions included? By "Errors"
> > > do you mean those Errors which I am getting in the application i.e
> > > "Cannot Modify..." ! If yes How do I include this message in the
> > > profiler, becse I do not see there any option for inclusion of my error
> > > message. Please guide.
> > >
> > > Deepak
> > >
> > > microsoft . public . sqlserver wrote:
> > >> Thanks for ur reply Guzman.
> > >> 1. Yes It was a SQL server backup
> > >> 2. I did not reinstall SQL server .
> > >>
> > >> I will run a SQL profiler trace and get back.
> > >> Thanks again.
> > >>
> > >> Deepak
> > >> Dan Guzman wrote:
> > >> > So the application is not reporting the actual SQL Server error
> > >> > message?
> > >> > Without that information, you are shooting in the dark. I suggest you
> > >> > run a
> > >> > SQL Profiler trace and also include Errors/Exceptions. This will
> > >> > hopefully
> > >> > help identify the cause of the error.
> > >> >
> > >> > You mention that you restored from backup. Was this a SQL Server
> > >> > backup?
> > >> > Did you reinstall SQL Server?
> > >> >
> > >> > --
> > >> > Hope this helps.
> > >> >
> > >> > Dan Guzman
> > >> > SQL Server MVP
> > >> >
> > >> > "microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in message
> > >> > news:1154755197.215422.79810@.75g2000cwc.googlegroups.com...
> > >> > > Good Morning Friends
> > >> > >
> > >> > > I am in real soup. I am new to SQL server 7.0 and Visual basic 6.0. I
> > >> > > have got one application developed by some software agency using VB
> > >> > > 6.0
> > >> > > and sql server 7.0. Since last 6 years everything worked
> > >> > > Three days my SQLserver machine crashed because of hard disk failure.
> > >> > > After much effort of two days I restored all the data from the
> > >> > > backup.In our Application primarily there are two sections Members
> > >> > > and
> > >> > > Agency. Everything working fine in the Members section i.e browsing,
> > >> > > modification, deletion of records etc. But in the agency section only
> > >> > > browsing of record is working if I want to Edit the record and then
> > >> > > press the save button it gives the error message " Cannot Modify
> > >> > > Record, Please close the screen and reopen. All changes will be
> > >> > > lost."
> > >> > > Actions Taken till now:
> > >> > > 1. Change the deafult db to "ABC" for the user "CFC" Logging into the
> > >> > > SQLserver. This was the arrangement before crashing.
> > >> > > 2. Granted the server role "db owner", "db creator" to the user
> > >> > > "CFC".
> > >> > > 3. Checked the tables permission of Members section (Where Modify is
> > >> > > working) as well as agency section (Where Modify is not working),
> > >> > > both
> > >> > > the tables have same kind of permission.
> > >> > > 4. Tried to get answer on google but of no help.
> > >> > >
> > >> > > Please help me urgently.
> > >> > >
> > >> > > Thanks
> > >> > >
> > >> > > Deepak Sinha
> > >> > >
> > >|||> except this. I doubt is it because of the service pack 2 ? Can I
> upgrade it to service pack 3 or 4 or I can uninstall service pack 2.
I suggest you install SP4 since that's the final service pack for SQL 7.
Otherwise, you should run the same service pack as the original system.
That may be the underlying cause of these errors.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in message
news:1154857843.655253.136200@.m73g2000cwd.googlegroups.com...
> Dear Sir
> I ran the SQL profiler and I got these error messages
> 1. Error 16821, Severity: 16, state: 1
> 2. Operating system Error 87., The parameter is incorrect
> 3. sp_executesql N'UPDATE "INSDB".."INS_M_agency" SET
> "reg_code"=@.P1,"agen_name"=@.P2,"agen_place"=@.P3,"estb_date"=@.P4,'', ''
> go
> When I ran the above SQL statement in the Query Analyzer It is giving
> Error message "Server: Msg 170, Level 15, State 1, Line 1"
> " Line 1: Incorrect syntax near 'INSDB'."
>
> 4. UPDATE "INSDB".."INS_M_agency" SET
> "reg_code"=@.P1,"agen_name"=@.P2,"agen_place"=@.P3,"estb_date"=@.P4
> g0
> 5. After the hard disk crash at the time of restoration I got this
> Error message "[SQL-DMO] You must be logged in as 'sa' or a member of
> sysadmin, or a member of dbcreator" to get rid of this problem I
> downloaded SQL server Service pack 2 from microsoft site and installed
> it. After the restoration every other part of the application working
> except this. I doubt is it because of the service pack 2 ? Can I
> upgrade it to service pack 3 or 4 or I can uninstall service pack 2.
> Please guide
> Thanks
> Deepak Sinha
> microsoft . public . sqlserver wrote:
>> Sir,
>> On running SQL profiler with Error/Exceptions included It is showing
>> "Error: 16821, Severity: 16, State: 1" it is also giving another error
>> message
>> "Operating system Error 87., The Parameter is incorrect"
>> All these error messages in front of the database ID master while my
>> application is running on the database "ABC"
>> When I
>> Dan Guzman wrote:
>> > > How do I run SQL profiler with Errors/Exceptions included? By
>> > > "Errors"
>> > > do you mean those Errors which I am getting in the application i.e
>> > > "Cannot Modify..." !
>> >
>> > The 'Cannot Modify' message is not a SQL Server error message; it is a
>> > generic message generated by the VB6 application, probably in response
>> > to a
>> > SQL Server error. Hopefully, the trace will allow you to identify the
>> > actual SQL Server error so that you can take corrective action.
>> >
>> > I don't have SQL 7 Profiler available but I believe the steps are
>> > similar to
>> > SQL 2000 Profiler. There should be an Errors and Warnings event class.
>> > Include all those events.
>> >
>> > --
>> > Hope this helps.
>> >
>> > Dan Guzman
>> > SQL Server MVP
>> >
>> > "microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in message
>> > news:1154777520.843807.294740@.i3g2000cwc.googlegroups.com...
>> > > How do I run SQL profiler with Errors/Exceptions included? By
>> > > "Errors"
>> > > do you mean those Errors which I am getting in the application i.e
>> > > "Cannot Modify..." ! If yes How do I include this message in the
>> > > profiler, becse I do not see there any option for inclusion of my
>> > > error
>> > > message. Please guide.
>> > >
>> > > Deepak
>> > >
>> > > microsoft . public . sqlserver wrote:
>> > >> Thanks for ur reply Guzman.
>> > >> 1. Yes It was a SQL server backup
>> > >> 2. I did not reinstall SQL server .
>> > >>
>> > >> I will run a SQL profiler trace and get back.
>> > >> Thanks again.
>> > >>
>> > >> Deepak
>> > >> Dan Guzman wrote:
>> > >> > So the application is not reporting the actual SQL Server error
>> > >> > message?
>> > >> > Without that information, you are shooting in the dark. I suggest
>> > >> > you
>> > >> > run a
>> > >> > SQL Profiler trace and also include Errors/Exceptions. This will
>> > >> > hopefully
>> > >> > help identify the cause of the error.
>> > >> >
>> > >> > You mention that you restored from backup. Was this a SQL Server
>> > >> > backup?
>> > >> > Did you reinstall SQL Server?
>> > >> >
>> > >> > --
>> > >> > Hope this helps.
>> > >> >
>> > >> > Dan Guzman
>> > >> > SQL Server MVP
>> > >> >
>> > >> > "microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in
>> > >> > message
>> > >> > news:1154755197.215422.79810@.75g2000cwc.googlegroups.com...
>> > >> > > Good Morning Friends
>> > >> > >
>> > >> > > I am in real soup. I am new to SQL server 7.0 and Visual basic
>> > >> > > 6.0. I
>> > >> > > have got one application developed by some software agency using
>> > >> > > VB
>> > >> > > 6.0
>> > >> > > and sql server 7.0. Since last 6 years everything worked
>> > >> > > Three days my SQLserver machine crashed because of hard disk
>> > >> > > failure.
>> > >> > > After much effort of two days I restored all the data from the
>> > >> > > backup.In our Application primarily there are two sections
>> > >> > > Members
>> > >> > > and
>> > >> > > Agency. Everything working fine in the Members section i.e
>> > >> > > browsing,
>> > >> > > modification, deletion of records etc. But in the agency section
>> > >> > > only
>> > >> > > browsing of record is working if I want to Edit the record and
>> > >> > > then
>> > >> > > press the save button it gives the error message " Cannot Modify
>> > >> > > Record, Please close the screen and reopen. All changes will be
>> > >> > > lost."
>> > >> > > Actions Taken till now:
>> > >> > > 1. Change the deafult db to "ABC" for the user "CFC" Logging
>> > >> > > into the
>> > >> > > SQLserver. This was the arrangement before crashing.
>> > >> > > 2. Granted the server role "db owner", "db creator" to the user
>> > >> > > "CFC".
>> > >> > > 3. Checked the tables permission of Members section (Where
>> > >> > > Modify is
>> > >> > > working) as well as agency section (Where Modify is not
>> > >> > > working),
>> > >> > > both
>> > >> > > the tables have same kind of permission.
>> > >> > > 4. Tried to get answer on google but of no help.
>> > >> > >
>> > >> > > Please help me urgently.
>> > >> > >
>> > >> > > Thanks
>> > >> > >
>> > >> > > Deepak Sinha
>> > >> > >
>> > >
>|||I downloaded and installed the service pack 3 now my Enterprise Manager
is not starting after giving the previous user name(tre) and
password(****). It is saying "Connection failed check SQL server
registration properties" When I edit the reg. properties by giving
previous user-id and pwd it is saying "cannot open default database
'<ID>' . using master database instead". I tried changing default
database at the command prompt
C:\mssql7\binn>isql -E -d
1>use master
2>go
1>sp_defaultdb tre, insdb
2>go
Default database changed
1>exit
When I go back to Enterprise Manager it is still same. I am in a real
mess.
Pl. Guide.
Deepka
Dan Guzman wrote:
> > except this. I doubt is it because of the service pack 2 ? Can I
> > upgrade it to service pack 3 or 4 or I can uninstall service pack 2.
> I suggest you install SP4 since that's the final service pack for SQL 7.
> Otherwise, you should run the same service pack as the original system.
> That may be the underlying cause of these errors.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in message
> news:1154857843.655253.136200@.m73g2000cwd.googlegroups.com...
> > Dear Sir
> > I ran the SQL profiler and I got these error messages
> > 1. Error 16821, Severity: 16, state: 1
> > 2. Operating system Error 87., The parameter is incorrect
> > 3. sp_executesql N'UPDATE "INSDB".."INS_M_agency" SET
> > "reg_code"=@.P1,"agen_name"=@.P2,"agen_place"=@.P3,"estb_date"=@.P4,'', ''
> > go
> >
> > When I ran the above SQL statement in the Query Analyzer It is giving
> > Error message "Server: Msg 170, Level 15, State 1, Line 1"
> > " Line 1: Incorrect syntax near 'INSDB'."
> >
> >
> > 4. UPDATE "INSDB".."INS_M_agency" SET
> > "reg_code"=@.P1,"agen_name"=@.P2,"agen_place"=@.P3,"estb_date"=@.P4
> > g0
> >
> > 5. After the hard disk crash at the time of restoration I got this
> > Error message "[SQL-DMO] You must be logged in as 'sa' or a member of
> > sysadmin, or a member of dbcreator" to get rid of this problem I
> > downloaded SQL server Service pack 2 from microsoft site and installed
> > it. After the restoration every other part of the application working
> > except this. I doubt is it because of the service pack 2 ? Can I
> > upgrade it to service pack 3 or 4 or I can uninstall service pack 2.
> >
> > Please guide
> >
> > Thanks
> > Deepak Sinha
> >
> > microsoft . public . sqlserver wrote:
> >> Sir,
> >>
> >> On running SQL profiler with Error/Exceptions included It is showing
> >> "Error: 16821, Severity: 16, State: 1" it is also giving another error
> >> message
> >> "Operating system Error 87., The Parameter is incorrect"
> >> All these error messages in front of the database ID master while my
> >> application is running on the database "ABC"
> >> When I
> >> Dan Guzman wrote:
> >> > > How do I run SQL profiler with Errors/Exceptions included? By
> >> > > "Errors"
> >> > > do you mean those Errors which I am getting in the application i.e
> >> > > "Cannot Modify..." !
> >> >
> >> > The 'Cannot Modify' message is not a SQL Server error message; it is a
> >> > generic message generated by the VB6 application, probably in response
> >> > to a
> >> > SQL Server error. Hopefully, the trace will allow you to identify the
> >> > actual SQL Server error so that you can take corrective action.
> >> >
> >> > I don't have SQL 7 Profiler available but I believe the steps are
> >> > similar to
> >> > SQL 2000 Profiler. There should be an Errors and Warnings event class.
> >> > Include all those events.
> >> >
> >> > --
> >> > Hope this helps.
> >> >
> >> > Dan Guzman
> >> > SQL Server MVP
> >> >
> >> > "microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in message
> >> > news:1154777520.843807.294740@.i3g2000cwc.googlegroups.com...
> >> > > How do I run SQL profiler with Errors/Exceptions included? By
> >> > > "Errors"
> >> > > do you mean those Errors which I am getting in the application i.e
> >> > > "Cannot Modify..." ! If yes How do I include this message in the
> >> > > profiler, becse I do not see there any option for inclusion of my
> >> > > error
> >> > > message. Please guide.
> >> > >
> >> > > Deepak
> >> > >
> >> > > microsoft . public . sqlserver wrote:
> >> > >> Thanks for ur reply Guzman.
> >> > >> 1. Yes It was a SQL server backup
> >> > >> 2. I did not reinstall SQL server .
> >> > >>
> >> > >> I will run a SQL profiler trace and get back.
> >> > >> Thanks again.
> >> > >>
> >> > >> Deepak
> >> > >> Dan Guzman wrote:
> >> > >> > So the application is not reporting the actual SQL Server error
> >> > >> > message?
> >> > >> > Without that information, you are shooting in the dark. I suggest
> >> > >> > you
> >> > >> > run a
> >> > >> > SQL Profiler trace and also include Errors/Exceptions. This will
> >> > >> > hopefully
> >> > >> > help identify the cause of the error.
> >> > >> >
> >> > >> > You mention that you restored from backup. Was this a SQL Server
> >> > >> > backup?
> >> > >> > Did you reinstall SQL Server?
> >> > >> >
> >> > >> > --
> >> > >> > Hope this helps.
> >> > >> >
> >> > >> > Dan Guzman
> >> > >> > SQL Server MVP
> >> > >> >
> >> > >> > "microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in
> >> > >> > message
> >> > >> > news:1154755197.215422.79810@.75g2000cwc.googlegroups.com...
> >> > >> > > Good Morning Friends
> >> > >> > >
> >> > >> > > I am in real soup. I am new to SQL server 7.0 and Visual basic
> >> > >> > > 6.0. I
> >> > >> > > have got one application developed by some software agency using
> >> > >> > > VB
> >> > >> > > 6.0
> >> > >> > > and sql server 7.0. Since last 6 years everything worked
> >> > >> > > Three days my SQLserver machine crashed because of hard disk
> >> > >> > > failure.
> >> > >> > > After much effort of two days I restored all the data from the
> >> > >> > > backup.In our Application primarily there are two sections
> >> > >> > > Members
> >> > >> > > and
> >> > >> > > Agency. Everything working fine in the Members section i.e
> >> > >> > > browsing,
> >> > >> > > modification, deletion of records etc. But in the agency section
> >> > >> > > only
> >> > >> > > browsing of record is working if I want to Edit the record and
> >> > >> > > then
> >> > >> > > press the save button it gives the error message " Cannot Modify
> >> > >> > > Record, Please close the screen and reopen. All changes will be
> >> > >> > > lost."
> >> > >> > > Actions Taken till now:
> >> > >> > > 1. Change the deafult db to "ABC" for the user "CFC" Logging
> >> > >> > > into the
> >> > >> > > SQLserver. This was the arrangement before crashing.
> >> > >> > > 2. Granted the server role "db owner", "db creator" to the user
> >> > >> > > "CFC".
> >> > >> > > 3. Checked the tables permission of Members section (Where
> >> > >> > > Modify is
> >> > >> > > working) as well as agency section (Where Modify is not
> >> > >> > > working),
> >> > >> > > both
> >> > >> > > the tables have same kind of permission.
> >> > >> > > 4. Tried to get answer on google but of no help.
> >> > >> > >
> >> > >> > > Please help me urgently.
> >> > >> > >
> >> > >> > > Thanks
> >> > >> > >
> >> > >> > > Deepak Sinha
> >> > >> > >
> >> > >
> >|||Do you get any messages when you access the database?
>isql -E -d
>USE insdb
>GO
>exit
--
Hope this helps.
Dan Guzman
SQL Server MVP
"microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in message
news:1154869759.625272.196410@.m73g2000cwd.googlegroups.com...
>I downloaded and installed the service pack 3 now my Enterprise Manager
> is not starting after giving the previous user name(tre) and
> password(****). It is saying "Connection failed check SQL server
> registration properties" When I edit the reg. properties by giving
> previous user-id and pwd it is saying "cannot open default database
> '<ID>' . using master database instead". I tried changing default
> database at the command prompt
> C:\mssql7\binn>isql -E -d
> 1>use master
> 2>go
> 1>sp_defaultdb tre, insdb
> 2>go
> Default database changed
> 1>exit
> When I go back to Enterprise Manager it is still same. I am in a real
> mess.
> Pl. Guide.
> Deepka
> Dan Guzman wrote:
>> > except this. I doubt is it because of the service pack 2 ? Can I
>> > upgrade it to service pack 3 or 4 or I can uninstall service pack 2.
>> I suggest you install SP4 since that's the final service pack for SQL 7.
>> Otherwise, you should run the same service pack as the original system.
>> That may be the underlying cause of these errors.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in message
>> news:1154857843.655253.136200@.m73g2000cwd.googlegroups.com...
>> > Dear Sir
>> > I ran the SQL profiler and I got these error messages
>> > 1. Error 16821, Severity: 16, state: 1
>> > 2. Operating system Error 87., The parameter is incorrect
>> > 3. sp_executesql N'UPDATE "INSDB".."INS_M_agency" SET
>> > "reg_code"=@.P1,"agen_name"=@.P2,"agen_place"=@.P3,"estb_date"=@.P4,'', ''
>> > go
>> >
>> > When I ran the above SQL statement in the Query Analyzer It is giving
>> > Error message "Server: Msg 170, Level 15, State 1, Line 1"
>> > " Line 1: Incorrect syntax near 'INSDB'."
>> >
>> >
>> > 4. UPDATE "INSDB".."INS_M_agency" SET
>> > "reg_code"=@.P1,"agen_name"=@.P2,"agen_place"=@.P3,"estb_date"=@.P4
>> > g0
>> >
>> > 5. After the hard disk crash at the time of restoration I got this
>> > Error message "[SQL-DMO] You must be logged in as 'sa' or a member of
>> > sysadmin, or a member of dbcreator" to get rid of this problem I
>> > downloaded SQL server Service pack 2 from microsoft site and installed
>> > it. After the restoration every other part of the application working
>> > except this. I doubt is it because of the service pack 2 ? Can I
>> > upgrade it to service pack 3 or 4 or I can uninstall service pack 2.
>> >
>> > Please guide
>> >
>> > Thanks
>> > Deepak Sinha
>> >
>> > microsoft . public . sqlserver wrote:
>> >> Sir,
>> >>
>> >> On running SQL profiler with Error/Exceptions included It is showing
>> >> "Error: 16821, Severity: 16, State: 1" it is also giving another error
>> >> message
>> >> "Operating system Error 87., The Parameter is incorrect"
>> >> All these error messages in front of the database ID master while my
>> >> application is running on the database "ABC"
>> >> When I
>> >> Dan Guzman wrote:
>> >> > > How do I run SQL profiler with Errors/Exceptions included? By
>> >> > > "Errors"
>> >> > > do you mean those Errors which I am getting in the application i.e
>> >> > > "Cannot Modify..." !
>> >> >
>> >> > The 'Cannot Modify' message is not a SQL Server error message; it is
>> >> > a
>> >> > generic message generated by the VB6 application, probably in
>> >> > response
>> >> > to a
>> >> > SQL Server error. Hopefully, the trace will allow you to identify
>> >> > the
>> >> > actual SQL Server error so that you can take corrective action.
>> >> >
>> >> > I don't have SQL 7 Profiler available but I believe the steps are
>> >> > similar to
>> >> > SQL 2000 Profiler. There should be an Errors and Warnings event
>> >> > class.
>> >> > Include all those events.
>> >> >
>> >> > --
>> >> > Hope this helps.
>> >> >
>> >> > Dan Guzman
>> >> > SQL Server MVP
>> >> >
>> >> > "microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in
>> >> > message
>> >> > news:1154777520.843807.294740@.i3g2000cwc.googlegroups.com...
>> >> > > How do I run SQL profiler with Errors/Exceptions included? By
>> >> > > "Errors"
>> >> > > do you mean those Errors which I am getting in the application i.e
>> >> > > "Cannot Modify..." ! If yes How do I include this message in the
>> >> > > profiler, becse I do not see there any option for inclusion of my
>> >> > > error
>> >> > > message. Please guide.
>> >> > >
>> >> > > Deepak
>> >> > >
>> >> > > microsoft . public . sqlserver wrote:
>> >> > >> Thanks for ur reply Guzman.
>> >> > >> 1. Yes It was a SQL server backup
>> >> > >> 2. I did not reinstall SQL server .
>> >> > >>
>> >> > >> I will run a SQL profiler trace and get back.
>> >> > >> Thanks again.
>> >> > >>
>> >> > >> Deepak
>> >> > >> Dan Guzman wrote:
>> >> > >> > So the application is not reporting the actual SQL Server error
>> >> > >> > message?
>> >> > >> > Without that information, you are shooting in the dark. I
>> >> > >> > suggest
>> >> > >> > you
>> >> > >> > run a
>> >> > >> > SQL Profiler trace and also include Errors/Exceptions. This
>> >> > >> > will
>> >> > >> > hopefully
>> >> > >> > help identify the cause of the error.
>> >> > >> >
>> >> > >> > You mention that you restored from backup. Was this a SQL
>> >> > >> > Server
>> >> > >> > backup?
>> >> > >> > Did you reinstall SQL Server?
>> >> > >> >
>> >> > >> > --
>> >> > >> > Hope this helps.
>> >> > >> >
>> >> > >> > Dan Guzman
>> >> > >> > SQL Server MVP
>> >> > >> >
>> >> > >> > "microsoft . public . sqlserver" <dpk.sinha@.gmail.com> wrote in
>> >> > >> > message
>> >> > >> > news:1154755197.215422.79810@.75g2000cwc.googlegroups.com...
>> >> > >> > > Good Morning Friends
>> >> > >> > >
>> >> > >> > > I am in real soup. I am new to SQL server 7.0 and Visual
>> >> > >> > > basic
>> >> > >> > > 6.0. I
>> >> > >> > > have got one application developed by some software agency
>> >> > >> > > using
>> >> > >> > > VB
>> >> > >> > > 6.0
>> >> > >> > > and sql server 7.0. Since last 6 years everything worked
>> >> > >> > > Three days my SQLserver machine crashed because of hard disk
>> >> > >> > > failure.
>> >> > >> > > After much effort of two days I restored all the data from
>> >> > >> > > the
>> >> > >> > > backup.In our Application primarily there are two sections
>> >> > >> > > Members
>> >> > >> > > and
>> >> > >> > > Agency. Everything working fine in the Members section i.e
>> >> > >> > > browsing,
>> >> > >> > > modification, deletion of records etc. But in the agency
>> >> > >> > > section
>> >> > >> > > only
>> >> > >> > > browsing of record is working if I want to Edit the record
>> >> > >> > > and
>> >> > >> > > then
>> >> > >> > > press the save button it gives the error message " Cannot
>> >> > >> > > Modify
>> >> > >> > > Record, Please close the screen and reopen. All changes will
>> >> > >> > > be
>> >> > >> > > lost."
>> >> > >> > > Actions Taken till now:
>> >> > >> > > 1. Change the deafult db to "ABC" for the user "CFC" Logging
>> >> > >> > > into the
>> >> > >> > > SQLserver. This was the arrangement before crashing.
>> >> > >> > > 2. Granted the server role "db owner", "db creator" to the
>> >> > >> > > user
>> >> > >> > > "CFC".
>> >> > >> > > 3. Checked the tables permission of Members section (Where
>> >> > >> > > Modify is
>> >> > >> > > working) as well as agency section (Where Modify is not
>> >> > >> > > working),
>> >> > >> > > both
>> >> > >> > > the tables have same kind of permission.
>> >> > >> > > 4. Tried to get answer on google but of no help.
>> >> > >> > >
>> >> > >> > > Please help me urgently.
>> >> > >> > >
>> >> > >> > > Thanks
>> >> > >> > >
>> >> > >> > > Deepak Sinha
>> >> > >> > >
>> >> > >
>> >
>

After restoring MASTER database, can't start SQLServer Service: Configuration block version 0 i

Now, I checked and verified that my backup version of SQL Server is the same as the version installed on the computer I'm restoring too.

I have SQL Server on a production machine that I backed up and want to test a full restore on a dev machine to make sure it will work when I need it to.

Now that I've run the restore command on my tape backup and go to restart the SQL server service I receive:

Configuration block version 0 is not a valid version number. SQL Server is exiting. Restore the master database or reinstall.

I'm afraid I don't understand why this is happening. If the builds are the same, then shouldn't restoring the MASTER database have worked normally and I'd be able to restart the service now?

Any thoughts or suggestions?

If the service cannot be started, you must rebuild the

system databases, adding information that has been lost by attaching existing tables and recreating

objects.

After this, Restoring the master database when SQL Server is accessible

With master database accessible, you should start SQL Server in single-user mode and then restore your copy of the

master database from your most recent full database backup in the usual way, as described in the

following steps.

#1 - Start SQL Server in single-user mode.

with command:

sqlservr.exe -c –m

#2 - Restore the master database from the most recent backup:

RESTORE DATABASE master

FROM masterbackup

If Master isn′t accessible:

To rebuild the master database, you should run the SQL Server setup program with the following

options:

? The /qn switch to suppress the user interface.

? The REINSTALLMODE = AMUS property to rebuild system databases.

? The REINSTALL = ALL property to set up the server with the previously installed features.

This must be used when specifying the REINSTALLMODE property.

|||

I tried rebuilding using this command:

start /wait d:\setup.exe /qb INSTANCENAME=MSSQLSERVER REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD=YourPassword

However, you are saying those were not the proper commands and switches to use during the reinstallation?

(Also I didn't want to specify an SA account and password, I wanted to use windows authentication but didn't see an option for that).

|||

To use Windows authentication, you need use this parameters:

start /wait d:\setup.exe /qb INSTANCENAME=MSSQLSERVER REINSTALL=SQL_Engine REBUILDDATABASE=1

SQLACCOUNT=<domain\user> SQLPASSWORD=<DomainUserPassword>

|||

Thanks.

Anyway, I tried rebuilding and that DID work.

But when I restored the master database, I was back where I started.

I KNOW the database installations are the same version as I did SELECT @.@.VERSION on both and they match.

So I don't understand why restoring a tape from one server to the other causes the other server to throw this error when the versions of the server do appear to be the same.

Thursday, February 16, 2012

After Recovery...

Is it required/best practice to run any job/commands after restoring the SQL
database server? SQL2K.
Thank you for the answers.
Austin
Hi,
You can execute a DBCC CHECKDB('dbname') to confirm the database is in good
shape. As well as you can schedule
a UPDATE STATISTICS weekly once or daily (depends on the data size).
Thanks
Hari
SQL Server MVP
"JohnSmith" <JJSmith_Austin@.hotmail.com> wrote in message
news:e7npwNPrFHA.2996@.tk2msftngp13.phx.gbl...
> Is it required/best practice to run any job/commands after restoring the
> SQL
> database server? SQL2K.
> Thank you for the answers.
> Austin
>
>
|||Thank you,
Austin
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%239dgfUPrFHA.1172@.TK2MSFTNGP11.phx.gbl...
> Hi,
> You can execute a DBCC CHECKDB('dbname') to confirm the database is in
good
> shape. As well as you can schedule
> a UPDATE STATISTICS weekly once or daily (depends on the data size).
> Thanks
> Hari
> SQL Server MVP
>
> "JohnSmith" <JJSmith_Austin@.hotmail.com> wrote in message
> news:e7npwNPrFHA.2996@.tk2msftngp13.phx.gbl...
>

After Recovery...

Is it required/best practice to run any job/commands after restoring the SQL
database server? SQL2K.
Thank you for the answers.
AustinHi,
You can execute a DBCC CHECKDB('dbname') to confirm the database is in good
shape. As well as you can schedule
a UPDATE STATISTICS weekly once or daily (depends on the data size).
Thanks
Hari
SQL Server MVP
"JohnSmith" <JJSmith_Austin@.hotmail.com> wrote in message
news:e7npwNPrFHA.2996@.tk2msftngp13.phx.gbl...
> Is it required/best practice to run any job/commands after restoring the
> SQL
> database server? SQL2K.
> Thank you for the answers.
> Austin
>
>|||Thank you,
Austin
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%239dgfUPrFHA.1172@.TK2MSFTNGP11.phx.gbl...
> Hi,
> You can execute a DBCC CHECKDB('dbname') to confirm the database is in
good
> shape. As well as you can schedule
> a UPDATE STATISTICS weekly once or daily (depends on the data size).
> Thanks
> Hari
> SQL Server MVP
>
> "JohnSmith" <JJSmith_Austin@.hotmail.com> wrote in message
> news:e7npwNPrFHA.2996@.tk2msftngp13.phx.gbl...
>

After Recovery...

Is it required/best practice to run any job/commands after restoring the SQL
database server? SQL2K.
Thank you for the answers.
AustinHi,
You can execute a DBCC CHECKDB('dbname') to confirm the database is in good
shape. As well as you can schedule
a UPDATE STATISTICS weekly once or daily (depends on the data size).
Thanks
Hari
SQL Server MVP
"JohnSmith" <JJSmith_Austin@.hotmail.com> wrote in message
news:e7npwNPrFHA.2996@.tk2msftngp13.phx.gbl...
> Is it required/best practice to run any job/commands after restoring the
> SQL
> database server? SQL2K.
> Thank you for the answers.
> Austin
>
>|||Thank you,
Austin
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%239dgfUPrFHA.1172@.TK2MSFTNGP11.phx.gbl...
> Hi,
> You can execute a DBCC CHECKDB('dbname') to confirm the database is in
good
> shape. As well as you can schedule
> a UPDATE STATISTICS weekly once or daily (depends on the data size).
> Thanks
> Hari
> SQL Server MVP
>
> "JohnSmith" <JJSmith_Austin@.hotmail.com> wrote in message
> news:e7npwNPrFHA.2996@.tk2msftngp13.phx.gbl...
> > Is it required/best practice to run any job/commands after restoring the
> > SQL
> > database server? SQL2K.
> >
> > Thank you for the answers.
> >
> > Austin
> >
> >
> >
> >
>

After Master is restored...

After restoring Master, is it necessary to retore Model and MSDB?MSDB will bring your Jobs, DTS Packages, etc. No on Model.
"rerichards" <cbrichards@.comcast.net> wrote in message
news:1106595295.357042.246450@.f14g2000cwb.googlegroups.com...
> After restoring Master, is it necessary to retore Model and MSDB?
>

After Master is restored...

After restoring Master, is it necessary to retore Model and MSDB?
MSDB will bring your Jobs, DTS Packages, etc. No on Model.
"rerichards" <cbrichards@.comcast.net> wrote in message
news:1106595295.357042.246450@.f14g2000cwb.googlegr oups.com...
> After restoring Master, is it necessary to retore Model and MSDB?
>

After Master is restored

After restoring Master, is it ALWAYS necessary to also restore MSDB?
Message posted via http://www.sqlmonster.com
Robert
No it is not always necessary, it depends on what you are doing. If for
instance you had a corrupt master database for some reason, but your other
databases were fine then there would be no need.
On the other hand if you were moving all your databases from one server to
another, you would want to restore msdb, as long as you were using it. (had
some Jobs, alerts or operators on it).
I would say only restore what you need to.
Hope this helps
John
"Robert Richards via SQLMonster.com" wrote:

> After restoring Master, is it ALWAYS necessary to also restore MSDB?
> --
> Message posted via http://www.sqlmonster.com
>

Monday, February 13, 2012

After Master is restored

After restoring Master, is it ALWAYS necessary to also restore MSDB?
Message posted via http://www.droptable.comRobert
No it is not always necessary, it depends on what you are doing. If for
instance you had a corrupt master database for some reason, but your other
databases were fine then there would be no need.
On the other hand if you were moving all your databases from one server to
another, you would want to restore msdb, as long as you were using it. (had
some Jobs, alerts or operators on it).
I would say only restore what you need to.
Hope this helps
John
"Robert Richards via droptable.com" wrote:

> After restoring Master, is it ALWAYS necessary to also restore MSDB?
> --
> Message posted via http://www.droptable.com
>

After Master is restored

After restoring Master, is it ALWAYS necessary to also restore MSDB?
--
Message posted via http://www.sqlmonster.comRobert
No it is not always necessary, it depends on what you are doing. If for
instance you had a corrupt master database for some reason, but your other
databases were fine then there would be no need.
On the other hand if you were moving all your databases from one server to
another, you would want to restore msdb, as long as you were using it. (had
some Jobs, alerts or operators on it).
I would say only restore what you need to.
Hope this helps
John
"Robert Richards via SQLMonster.com" wrote:
> After restoring Master, is it ALWAYS necessary to also restore MSDB?
> --
> Message posted via http://www.sqlmonster.com
>

Sunday, February 19, 2012

After restoring the Database getting this message "Cannot Modify record"

After restoring the Database getting this message "Cannot Modify record"

After restoring MASTER database, can't start SQLServer Service: Configuration block version 0 i

Thursday, February 16, 2012

After Recovery...

After Recovery...

After Recovery...

After Master is restored...

After Master is restored...

After Master is restored...

After Master is restored

Monday, February 13, 2012

After Master is restored

After Master is restored

SQL tool for MSDE

Blog Archive

About Me