Thursday, July 18, 2013

[MS SQL Server] Avamar Transaction Log Backup Issue

[MS SQL Server] Avamar Transaction Log Backup Issue

Avamar Transaction Log Backup Issue

Posted: 04 Feb 2013 01:34 AM PST

Hi,We just recently started using Avamar to backup everything including an hourly SQL server transaction log backup. The issue we're having is that since we started using Avamar, the transaction file (LDF) file keeps growing very large. Has anyone experienced this issue before? If not, any idea?Thanks,

about servers.

Posted: 18 Jul 2013 03:52 AM PDT

can anyone please explain in simple terms what are physical servers and virtual servers?

Can’t use connect using (local) or localhost as a server name

Posted: 18 Jul 2013 02:59 AM PDT

Hello everyoneI have a laptop with SQL Server 2008 installed locally. I can only connect to the server by specifying the instance name (this is true of connection attempts using SSMS, datasources in SSRS, etc.) It would greatly simplify things if I could connect using (local) instead of the instance name.When I try using (local), it tells me the "server was not found or is inaccessible".Can anyone please tell me what I should do to configure this?Thanks in advance for your help.

litespeed restore

Posted: 02 Jul 2013 02:35 AM PDT

we have db backup file(litespeed backup file).Litespeed is not installed in the server.we need a command to restore the litespeed backup file.

Transaction Log growth out of control

Posted: 18 Jul 2013 12:19 AM PDT

Last weekend I re-indexed some Databases.Before doing so I backed up the Databases and Set them to simple recovery mode.After the rebuild of the Indexes was complete I Set the Database back to Full recovery and performed another backup.Ever since the Transaction log growth and size on one of the Databases is huge.The Database is 259 GB but the Log File has been quite large.I'm backing up the log and shrinking it.This morning the log file was 108 GB.I tried backing up and shrinking several times but the size remained the same.I checked for Open Transactions and there were none.So I put the Database in Simple Recovery and then I shrank the log file.I want the Database to be in Full Recovery mode.I never experienced anything like this, and ideas?Thanks.

Backup strategies and scheduling

Posted: 17 Jul 2013 11:48 PM PDT

Our DBA has left the company and I have just inherited the daily job of reviewing backup jobs to ensure that they have completed successfully.I created a list of databases and their corresponding backup jobs/schedules in order to check them off and document completion.During this exercise I have noted two schedules that appear odd to me:DatabaseW scheduled for Full daily, Diff every 4 hours, Logs every 6 hours. DatabaseR scheduled for Full daily, Logs weekly.I have always scheduled logs most frequently and in between diffs and/or fulls...am I missing something or should these schedules be changed?

Server crash during load testing

Posted: 18 Jul 2013 12:02 AM PDT

After a peak load test carried out for an application for two consecutive days, the DB server got automatically bounced the next day with following event logged.Does a deadlock situation/lot of concurrent connections bring down the server? What should be taken care of in order to address this issue?The following is the error message from the logs:[sqsrvres] printODBCError: sqlstate = 08S01; native error = 0; message = [Microsoft][SQL Server Native Client 10.0]The connection is no longer usable because the server failed to respond to a command cancellation for a previously executed statement in a timely manner. Possible causes include application deadlocks or the server being overloaded. Open a new connection and re-try the operation.Cluster resource 'SQL Server' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.Cluster Agent: The cluster resource SQL Server has failed. [SNMP TRAP: 15006 in CPQCLUS.MIB]Cluster Agent: The cluster resource SQL Server Agent has failed. [SNMP TRAP: 15006 in CPQCLUS.MIB]The SQL Server Agent (MSSQLSERVER) service terminated unexpectedly. It has done this 2 time(s).Cluster Agent: The cluster resource SQL Server Agent has become degraded. [SNMP TRAP: 15005 in CPQCLUS.MIB][sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed[sqsrvres] printODBCError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Server Native Client 10.0]Query timeout expired[sqsrvres] OnlineThread: QP is not online.

SQL Server available memory during load test

Posted: 18 Jul 2013 12:00 AM PDT

On a Database server, Buffer pool is configured to utilize 80% of RAM and remaining 20% is for OS.At the end of Normal load test on the application, database server shows available memory of around 50% on the server. However, when application Peak load test is carried out, it starts with available memory of less than 10% on the DB server and then goes down till 7%. And no connections are made to SQL server during this time apart from the peak load test.Is this acceptable behavior? Can we have available memory going down until 7% when memory allocated to OS is 20%?

Cannot access tempdb properties

Posted: 04 Apr 2012 11:45 AM PDT

Immediately after a reboot we can access the properties of the tempdb. However, a few minutes later when you try to examine those properties you get:TITLE: Microsoft SQL Server Management Studio------------------------------Cannot show requested dialog.------------------------------ADDITIONAL INFORMATION:Cannot show requested dialog. (SqlMgmt)------------------------------Property Size is not available for Database '[tempdb]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Smo)For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600.1+((KJ_RTM).100402-1540+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.PropertyCannotBeRetrievedExceptionText&EvtID=Size&LinkId=20476==============I'm not sure if this is a symptom or the problem but this server and db are experiencing timeouts for inserts and updates. The vendor is working on it but I'm hoping we could lend some assistance. None of our other servers that do much higher volumes have this issue. We've been over and over network, memory etc. Any ideas or thoughts are appreciated.
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Search This Blog