Maintenance Job log incomplete

I have created a maintenance plan and specified a detailed job log. The log
only contains the entries down to the "Details" line and noting after.
This is on a SQL Server 2005 SP1 server.
Any ideas?This is happening to me too. This is all I get in the report text file and
yet the job has run for 4hrs and ends in a failed status.
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.2047
Report was generated on "DBSERVER".
Maintenance Plan: Weekly All DB Maintenance Plan
Duration: 00:00:00
Status: Succeeded.
Details:

Maintenance Job log incomplete

I have created a maintenance plan and specified a detailed job log. The log
only contains the entries down to the "Details" line and noting after.
This is on a SQL Server 2005 SP1 server.
Any ideas?
This is happening to me too. This is all I get in the report text file and
yet the job has run for 4hrs and ends in a failed status.
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.2047
Report was generated on "DBSERVER".
Maintenance Plan: Weekly All DB Maintenance Plan
Duration: 00:00:00
Status: Succeeded.
Details:

Maintain History

Hi All
I have a table that contains details regarding branch offices and as these
offices regularly change details such as the branch name and address I need
to always have the current details and also maintain a history of historical
details for each branch office. Initially I was think of having a duplicate
table with a datetime column to store when the last change was made and also
a column that contained the details of who changed the branch office details.
I was going to control this through the application but have identified that
there is any additional vendor application that also change details in this
table and the application can not be modified.
Is the best way to maintain a history of branch office details in this
scenario to create a trigger on the table and populate a duplicate table with
the details of the branch office as they where before being modified or is
there a better way to do this?
Thanks
- DavidHi David
There is a simple auditing example (E) in the Create Trigger topic in books
online. There may be an impact on the system if you implement these on all
your tables, in both the amount of storage used and time taken to make
changes. To reduce the performance degredation it is best to keep the trigger
as simple as you can , if any reconciliation is necessary then you can do
that during a quiet period of possibly offline.
Alternatively you can purchase a log reading program, you may want to log at
LogExplorer from Lumigent www.lumigent.com or LogPI which has been aquired
by Goldengate see www.logpi.com
John
"David" wrote:
> Hi All
> I have a table that contains details regarding branch offices and as these
> offices regularly change details such as the branch name and address I need
> to always have the current details and also maintain a history of historical
> details for each branch office. Initially I was think of having a duplicate
> table with a datetime column to store when the last change was made and also
> a column that contained the details of who changed the branch office details.
> I was going to control this through the application but have identified that
> there is any additional vendor application that also change details in this
> table and the application can not be modified.
> Is the best way to maintain a history of branch office details in this
> scenario to create a trigger on the table and populate a duplicate table with
> the details of the branch office as they where before being modified or is
> there a better way to do this?
> Thanks
> - David

Maintain History

Hi All
I have a table that contains details regarding branch offices and as these
offices regularly change details such as the branch name and address I need
to always have the current details and also maintain a history of historical
details for each branch office. Initially I was think of having a duplicate
table with a datetime column to store when the last change was made and also
a column that contained the details of who changed the branch office details
.
I was going to control this through the application but have identified that
there is any additional vendor application that also change details in this
table and the application can not be modified.
Is the best way to maintain a history of branch office details in this
scenario to create a trigger on the table and populate a duplicate table wit
h
the details of the branch office as they where before being modified or is
there a better way to do this?
Thanks
- DavidHi David
There is a simple auditing example (E) in the Create Trigger topic in books
online. There may be an impact on the system if you implement these on all
your tables, in both the amount of storage used and time taken to make
changes. To reduce the performance degredation it is best to keep the trigge
r
as simple as you can , if any reconciliation is necessary then you can do
that during a quiet period of possibly offline.
Alternatively you can purchase a log reading program, you may want to log at
LogExplorer from Lumigent www.lumigent.com or LogPI which has been aquired
by Goldengate see www.logpi.com
John
"David" wrote:

> Hi All
> I have a table that contains details regarding branch offices and as these
> offices regularly change details such as the branch name and address I nee
d
> to always have the current details and also maintain a history of historic
al
> details for each branch office. Initially I was think of having a duplica
te
> table with a datetime column to store when the last change was made and al
so
> a column that contained the details of who changed the branch office detai
ls.
> I was going to control this through the application but have identified t
hat
> there is any additional vendor application that also change details in thi
s
> table and the application can not be modified.
> Is the best way to maintain a history of branch office details in this
> scenario to create a trigger on the table and populate a duplicate table w
ith
> the details of the branch office as they where before being modified or is
> there a better way to do this?
> Thanks
> - David

Mailing Lists

Hi All

We are running SQL Server & Outlook with an exchange server. We are
looking for a way to import the address book & email details into a
database table.

We have managed to do this with MS Access by using the import option
exchange(). Is there a similar way this can be done in SQLServer 2000"Mick Kehoe" <mick@.kehoe.demon.co.uk> wrote in message
news:86917a0f.0409220431.21399510@.posting.google.c om...
> Hi All
> We are running SQL Server & Outlook with an exchange server. We are
> looking for a way to import the address book & email details into a
> database table.
> We have managed to do this with MS Access by using the import option
> exchange(). Is there a similar way this can be done in SQLServer 2000

I'm not familiar with Exchange, however if you can export the addresses to a
CSV file, then DTS or bcp.exe can import the data. Alternatively, if you
already have them in Access, then you could use DTS or a linked server to
pull them into MSSQL.

Simon|||From MS SQL 2k Books On Line ...

The Microsoft OLE DB Provider for Exchange exposes data stored in a
Microsoft Exchange 2000 Web Store in tabular form. This data can be queried
using an SQL-like language that is very similar to the SQL subset supported
by the OLE DB Provider for Microsoft Indexing Service.

Microsoft SQL ServerT 2000 distributed queries can be used to query data
from the Exchange Web Store through this OLE DB Provider and can be joined
with tables in SQL Server. The Exchange Web Store should be located in the
same computer as SQL Server. Web Stores located in other computers cannot be
accessed using the OLE DB Provider for Exchange.

"Simon Hayes" <sql@.hayes.ch> wrote in message
news:41517712$1_1@.news.bluewin.ch...
> "Mick Kehoe" <mick@.kehoe.demon.co.uk> wrote in message
> news:86917a0f.0409220431.21399510@.posting.google.c om...
> > Hi All
> > We are running SQL Server & Outlook with an exchange server. We are
> > looking for a way to import the address book & email details into a
> > database table.
> > We have managed to do this with MS Access by using the import option
> > exchange(). Is there a similar way this can be done in SQLServer 2000
> I'm not familiar with Exchange, however if you can export the addresses to
a
> CSV file, then DTS or bcp.exe can import the data. Alternatively, if you
> already have them in Access, then you could use DTS or a linked server to
> pull them into MSSQL.
> Simon