Forum Replies Created

Viewing 15 posts - 16 through 30 (of 335 total)

  • Reply To: Index rebuild / stats update taking lot of disk space.

    Dear All,

    Firstly , Thank you to all of you sharing your knowledge..The issue was with an Agent Jjob for Index Rebuild , done for all the Indexes irrespective of the...

    • This reply was modified 1 year, 9 months ago by  Arsh.
  • Reply To: Agent Job History is missing

    @Ant-green

    The setting is 1000 and 100 respectively. Interestingly a newly instance I recently setup on the same server , (with both having identical settings above ),writes the history. More interesting...

  • Reply To: SQL Agent Job doesn't write output

    Hi All,

    It was a permissions issue of the SQL server agent account on the directory . It couldn't write even being an administrator..I added specifically and it worked. However, though...

  • Reply To: SQL Agent Job doesn't write output

    Here is the full error from the error log

     

    "

    Date 13/01/2023 11:45:04 AM

    Log SQL Server Agent (Current - 13/01/2023 11:37:00 AM)

    Message

    [136] Job CheckDBIntegrity reported: The process could not be created for...

  • Reply To: SQL Agent Job doesn't write output

    Grant , its a DBCC CheckDB that I am calling from an agent job. It runs well but has error message at the end saying it cannot see the output...

    Attachments:
    You must be logged in to view attached files.
  • Reply To: SQL Agent Job doesn't write output

    Grant , its a DBCC CheckDB that I am calling from an agent job. It runs well but has error message at the end saying it cannot see the output...

    Attachments:
    You must be logged in to view attached files.
  • Reply To: Log Size is too high

    @ant-green, these are the answers:

    Firstly do you know what caused the log file to grow that large?    - I inherited just a week ago , and no documentation or...

  • Reply To: Log Size is too high

    Hi Grant,

    No , there is Log a shipping setup that backs up log every 1 Hr.thanks

  • Reply To: Log Size is too high

     

    Well, I guess the log files have not been actually growing fast given a nominal size-increase I noticed last few days.So , as you said, they might just be normal...

  • Reply To: Log Size is too high

     

    Well, I guess the log files have not been actually growing fast given a nominal size-increase I noticed last few days.So , as you said, they might just be normal...

  • Reply To: Log Size is too high

    Hi @Ant-green,

    I actually acquired this newly. I am sure there was no analysis ever done. But yes , there is log shipping enabled and the Log backup setup within the...

  • Reply To: Log Size is too high

    Log contents only have 214 rows . Majority of the operations are for LOP_MOFIFY_ROW etc . I have seen for LOP_SHRINK_NOOP.

     

    Thanks...Arshad

  • Reply To: Maintenance Plan excludes the AlwaysON database

    It backups the other databases. I asked it not to ignore any , but still leaves out the one in the Availability Group?  thank you

  • Reply To: Maintenance Plan excludes the AlwaysON database

    @michael-2 , No its not backing the Primary Up...It ignores it (Though I unchecked the option 'Ignore Databases that are  Not Online')..I get the warming you mentioned above...

    • This reply was modified 3 years, 1 month ago by  Arsh.
  • Reply To: Sudden Increase in DB Size

    @Ant-Green Yes ,  Log backups are helping to have a control on the file size. Also, I had found some default trace was running , so stopped that too...Looks fine...

Viewing 15 posts - 16 through 30 (of 335 total)