Hi,

To take log backup you need to give this command:

BACKUP DATABASE DB_NAME TO DISK='PATH\BACKUP_NAME' WITH  NOTRUNCATE_ONLY

On Thu, Jul 22, 2010 at 7:24 PM, Santhosh <san_spy@...> wrote:

>
>
> Tail log backup is nothing but transaction log backup. Basically in case of
>
> database failure the last transaction log backup taken before recovering
> the
> database is called tail log backup. Check below
>
> http://msdn.microsoft.com/en-us/library/ms179314.aspx
>
>
> With :))s
> Santhosh Kumar S.J - MCITP
> ReadMe @ sqlspy.blogspot.com
> ReadMe @ santhoshpakkangal.blogspot.com
>
> ________________________________
> From: SARADADEVI <sv_39@... <sv_39%40yahoo.co.in>>
> To: sqlcon@yahoogroups.com <sqlcon%40yahoogroups.com>
> Sent: Thu, 22 July, 2010 6:45:31 PM
> Subject: MUGH-SQLCON How to take tail log backup in SQLServer.
>
>
> How to take tail log backup in SQLServer.
>
> [Non-text portions of this message have been removed]
>
> [Non-text portions of this message have been removed]
>
>
>



--

Thanks & Regards

Shashi Kumar Singh
Senior System Engineer
IBM India (P)Ltd.
Email:singh.shashikumar2@... <Email%3Asingh.shashikumar2@...>,
shashi_120@...


[Non-text portions of this message have been removed]

Hello ,

							 The Concept is great, We Learn, Earn and have Fun same time & Its FREE.
No buying/selling, the website earns from advertisers and sharing profit with
us, Tested and Proven Concept. Check and if convinced; TRY, you don’t loose
anything at all.

							 Just Click here & Judge Yourself PleaseIf you have received this mail
from a unknown source and want to unsubscribe due to personal reasons, please
click below link as we also have 0% tolerance for SPAMTo unsubscribe and no
longer receive emails from viewbestads.com, click here.If you received this
email in Spam then Click Here



[Non-text portions of this message have been removed]

Hi
 
We requires that unsuccessful and successful login attempts be logged
With the excessive log files now being created is it recommended/approved to
only capture unsuccessful logins for Microsoft SQL Servers ?
 
For one month  141,316 entries have been added to the SQL log file on our server
Is this large number normal ?
Will the log file become unmanageable ?
 
There is also a significant number of logins for USA\sqlsvc - Why?



[Non-text portions of this message have been removed]

It all depends upon your requirement. If your audit requirement requires for
both successful & unsuccessful logins, you have to record it. Put a script to
recycle the error logs daily.

  With :))s
Santhosh Kumar S.J - MCTS
ReadMe @ sqlspy.blogspot.com
ReadMe @ santhoshpakkangal.blogspot.com




________________________________
From: SARADADEVI <sv_39@...>
To: sqlcon@yahoogroups.com
Sent: Thu, 9 September, 2010 7:44:28 PM
Subject: MUGH-SQLCON SQL Logfile Size on our SQLServer


Hi

We requires that unsuccessful and successful login attempts be logged
With the excessive log files now being created is it recommended/approved to
only capture unsuccessful logins for Microsoft SQL Servers ?

For one month  141,316 entries have been added to the SQL log file on our server
Is this large number normal ?
Will the log file become unmanageable ?

There is also a significant number of logins for USA\sqlsvc - Why?

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]

Also increase the error log count to 100 or 200 as per ur audit requirements.

  With :))s
Santhosh Kumar S.J - MCTS
ReadMe @ sqlspy.blogspot.com
ReadMe @ santhoshpakkangal.blogspot.com




________________________________
From: SARADADEVI <sv_39@...>
To: sqlcon@yahoogroups.com
Sent: Thu, 9 September, 2010 7:44:28 PM
Subject: MUGH-SQLCON SQL Logfile Size on our SQLServer


Hi

We requires that unsuccessful and successful login attempts be logged
With the excessive log files now being created is it recommended/approved to
only capture unsuccessful logins for Microsoft SQL Servers ?

For one month  141,316 entries have been added to the SQL log file on our server
Is this large number normal ?
Will the log file become unmanageable ?

There is also a significant number of logins for USA\sqlsvc - Why?

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]

Friends,
 
Adobe Systems (www.adobe.com ) has an open position for SQL DBA.
Location - NOIDA
Experience: 5+ years
 
If interested, send resume to bhavesh@...
 
Regards,
Bhavesh



[Non-text portions of this message have been removed]

Hi Bhavesh,

Here is my updated cv and hope it will match with your requirement.

On Sun, Sep 19, 2010 at 4:10 PM, bhavesh prajapati <
bhavesh2984groups@...> wrote:

>
>
> Friends,
>
> Adobe Systems (www.adobe.com ) has an open position for SQL DBA.
> Location - NOIDA
> Experience: 5+ years
>
> If interested, send resume to bhavesh@... <bhavesh%40adobe.com>
>
> Regards,
> Bhavesh
>
> [Non-text portions of this message have been removed]
>
>
>



--

Thanks & Regards

Shashi Kumar Singh
Senior System Engineer
IBM India (P)Ltd.
Email:singh.shashikumar2@... <Email%3Asingh.shashikumar2@...>,
shashi_120@...


[Non-text portions of this message have been removed]

Hi Friends,

I am new to SQL Server Administration.

I have created the Daily Maintenance plan as below and the Rebuild Index task
fails once in a week.

Backup Database Task - All Databases --> Maintenance Cleanup Task - Older than 1
weeks --> Check Database Integrity Task - Include Indexes --> Shrink Database
Task - All Databases --> Rebuild Index Task - Object Tables and Views --> Update
Statistics Full Scan

Now once or twice in a week the Rebuild Index Task is fails as below

Failed:(-1073548784) Executing the query "ALTER INDEX [PK_TestSet_Now] ON
[dbo].[TestSet_Now] REBUILD WITH ( PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  =
OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON, SORT_IN_TEMPDB = OFF, ONLINE
= OFF )
" failed with the following error: "Transaction (Process ID 66) was deadlocked
on lock resources with another process and has been chosen as the deadlock
victim. Rerun the transaction.". Possible failure reasons: Problems with the
query, "ResultSet" property not set correctly, parameters not set correctly, or
connection not established correctly.

Kindly  help me on this to get it resolved.

Regards
Senthil






[Non-text portions of this message have been removed]

HI Sentil,
 
Error itself telling that your process has been killed as a Dead Lock victim. It
means at the same time you are running some other process or jobs also, that is
creating dead lock. You can check those...or if you want to catch dead lock
information....enable the trace flag 1222 by DBCC TRACEON command. This trace
will log all dead lock information in your sql server error log.



Thanks & Regards,
Mohd Rizwan
(¨`·.·´¨) Always
`·.¸(¨`·.·´¨) Keep
(¨`·.·´¨)¸.·´ Smiling!
`·.¸.·´

--- On Thu, 23/9/10, Senthil Kumar K <mail.ksenthil@...> wrote:


From: Senthil Kumar K <mail.ksenthil@...>
Subject: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Cc: mail.ksenthil@...
Date: Thursday, 23 September, 2010, 1:08 PM


 



Hi Friends,

I am new to SQL Server Administration.

I have created the Daily Maintenance plan as below and the Rebuild Index task
fails once in a week.

Backup Database Task - All Databases --> Maintenance Cleanup Task - Older than 1
weeks --> Check Database Integrity Task - Include Indexes --> Shrink Database
Task - All Databases --> Rebuild Index Task - Object Tables and Views --> Update
Statistics Full Scan

Now once or twice in a week the Rebuild Index Task is fails as below

Failed:(-1073548784) Executing the query "ALTER INDEX [PK_TestSet_Now] ON
[dbo].[TestSet_Now] REBUILD WITH ( PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  =
OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON, SORT_IN_TEMPDB = OFF,
ONLINE = OFF )
" failed with the following error: "Transaction (Process ID 66) was deadlocked
on lock resources with another process and has been chosen as the deadlock
victim. Rerun the transaction.". Possible failure reasons: Problems with the
query, "ResultSet" property not set correctly, parameters not set correctly, or
connection not established correctly.

Kindly  help me on this to get it resolved.

Regards
Senthil

[Non-text portions of this message have been removed]










[Non-text portions of this message have been removed]

Hi Mohd,

Thanks for the reply and making me to understand. Could you please tell me how
enable the trace flag 1222 by DBCC TRACEON command and in detail.

Regards
Senthil



--- On Fri, 24/9/10, mohd rizwan <mo2riz@...> wrote:

From: mohd rizwan <mo2riz@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, 24 September, 2010, 1:46 AM







 









       HI Sentil,

 

Error itself telling that your process has been killed as a Dead Lock victim. It
means at the same time you are running some other process or jobs also, that is
creating dead lock. You can check those...or if you want to catch dead lock
information....enable the trace flag 1222 by DBCC TRACEON command. This trace
will log all dead lock information in your sql server error log.



Thanks & Regards,

Mohd Rizwan

(¨`·.·´¨) Always

`·.¸(¨`·.·´¨) Keep

(¨`·.·´¨)¸.·´ Smiling!

`·.¸.·´



--- On Thu, 23/9/10, Senthil Kumar K <mail.ksenthil@...> wrote:



From: Senthil Kumar K <mail.ksenthil@...>

Subject: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan

To: sqlcon@yahoogroups.com

Cc: mail.ksenthil@...

Date: Thursday, 23 September, 2010, 1:08 PM



 



Hi Friends,



I am new to SQL Server Administration.



I have created the Daily Maintenance plan as below and the Rebuild Index task
fails once in a week.



Backup Database Task - All Databases --> Maintenance Cleanup Task - Older than 1
weeks --> Check Database Integrity Task - Include Indexes --> Shrink Database
Task - All Databases --> Rebuild Index Task - Object Tables and Views --> Update
Statistics Full Scan



Now once or twice in a week the Rebuild Index Task is fails as below



Failed:(-1073548784) Executing the query "ALTER INDEX [PK_TestSet_Now] ON
[dbo].[TestSet_Now] REBUILD WITH ( PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  =
OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON, SORT_IN_TEMPDB = OFF,
ONLINE = OFF )

" failed with the following error: "Transaction (Process ID 66) was deadlocked
on lock resources with another process and has been chosen as the deadlock
victim. Rerun the transaction.". Possible failure reasons: Problems with the
query, "ResultSet" property not set correctly, parameters not set correctly, or
connection not established correctly.



Kindly  help me on this to get it resolved.



Regards

Senthil



[Non-text portions of this message have been removed]



[Non-text portions of this message have been removed]
























[Non-text portions of this message have been removed]

HI ,
 
  You can enable the trace flag by running this command
 
   dbcc traceon (1222,-1)
 
 or add it start up parameter in SQL Server
 
Thanks,
Muthu

--- On Fri, 24/9/10, Senthil Kumar K <mail.ksenthil@...> wrote:


From: Senthil Kumar K <mail.ksenthil@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, 24 September, 2010, 11:39 AM


 



Hi Mohd,

Thanks for the reply and making me to understand. Could you please tell me how
enable the trace flag 1222 by DBCC TRACEON command and in detail.

Regards
Senthil

--- On Fri, 24/9/10, mohd rizwan <mo2riz@...> wrote:

From: mohd rizwan <mo2riz@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, 24 September, 2010, 1:46 AM

 

HI Sentil,

 

Error itself telling that your process has been killed as a Dead Lock victim. It
means at the same time you are running some other process or jobs also, that is
creating dead lock. You can check those...or if you want to catch dead lock
information....enable the trace flag 1222 by DBCC TRACEON command. This trace
will log all dead lock information in your sql server error log.

Thanks & Regards,

Mohd Rizwan

(¨`·.·´¨) Always

`·.¸(¨`·.·´¨) Keep

(¨`·.·´¨)¸.·´ Smiling!

`·.¸.·´

--- On Thu, 23/9/10, Senthil Kumar K <mail.ksenthil@...> wrote:

From: Senthil Kumar K <mail.ksenthil@...>

Subject: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan

To: sqlcon@yahoogroups.com

Cc: mail.ksenthil@...

Date: Thursday, 23 September, 2010, 1:08 PM

 

Hi Friends,

I am new to SQL Server Administration.

I have created the Daily Maintenance plan as below and the Rebuild Index task
fails once in a week.

Backup Database Task - All Databases --> Maintenance Cleanup Task - Older than 1
weeks --> Check Database Integrity Task - Include Indexes --> Shrink Database
Task - All Databases --> Rebuild Index Task - Object Tables and Views --> Update
Statistics Full Scan

Now once or twice in a week the Rebuild Index Task is fails as below

Failed:(-1073548784) Executing the query "ALTER INDEX [PK_TestSet_Now] ON
[dbo].[TestSet_Now] REBUILD WITH ( PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  =
OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON, SORT_IN_TEMPDB = OFF,
ONLINE = OFF )

" failed with the following error: "Transaction (Process ID 66) was deadlocked
on lock resources with another process and has been chosen as the deadlock
victim. Rerun the transaction.". Possible failure reasons: Problems with the
query, "ResultSet" property not set correctly, parameters not set correctly, or
connection not established correctly.

Kindly  help me on this to get it resolved.

Regards

Senthil

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]










[Non-text portions of this message have been removed]

This error comes when other process run or other user trying to run or execute
command when index rebuild is going to start or on the activation time.Also when
you start the index already the process doing something in the same database /
table and hold the page ...
 

Take the database into the single user mode run the index rebuild and then agin
back to the multi user mode
This is the standard procedure to rebuild index in the production
 
Radhye..


--- On Fri, 9/24/10, muthu narayanan <avm_narayanan@...> wrote:


From: muthu narayanan <avm_narayanan@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, September 24, 2010, 2:21 PM


 



HI ,
 
  You can enable the trace flag by running this command
 
   dbcc traceon (1222,-1)
 
 or add it start up parameter in SQL Server
 
Thanks,
Muthu

--- On Fri, 24/9/10, Senthil Kumar K <mail.ksenthil@...> wrote:

From: Senthil Kumar K <mail.ksenthil@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, 24 September, 2010, 11:39 AM

 

Hi Mohd,

Thanks for the reply and making me to understand. Could you please tell me how
enable the trace flag 1222 by DBCC TRACEON command and in detail.

Regards
Senthil

--- On Fri, 24/9/10, mohd rizwan <mo2riz@...> wrote:

From: mohd rizwan <mo2riz@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, 24 September, 2010, 1:46 AM

 

HI Sentil,

 

Error itself telling that your process has been killed as a Dead Lock victim. It
means at the same time you are running some other process or jobs also, that is
creating dead lock. You can check those...or if you want to catch dead lock
information....enable the trace flag 1222 by DBCC TRACEON command. This trace
will log all dead lock information in your sql server error log.

Thanks & Regards,

Mohd Rizwan

(¨`·.·´¨) Always

`·.¸(¨`·.·´¨) Keep

(¨`·.·´¨)¸.·´ Smiling!

`·.¸.·´

--- On Thu, 23/9/10, Senthil Kumar K <mail.ksenthil@...> wrote:

From: Senthil Kumar K <mail.ksenthil@...>

Subject: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan

To: sqlcon@yahoogroups.com

Cc: mail.ksenthil@...

Date: Thursday, 23 September, 2010, 1:08 PM

 

Hi Friends,

I am new to SQL Server Administration.

I have created the Daily Maintenance plan as below and the Rebuild Index task
fails once in a week.

Backup Database Task - All Databases --> Maintenance Cleanup Task - Older than 1
weeks --> Check Database Integrity Task - Include Indexes --> Shrink Database
Task - All Databases --> Rebuild Index Task - Object Tables and Views --> Update
Statistics Full Scan

Now once or twice in a week the Rebuild Index Task is fails as below

Failed:(-1073548784) Executing the query "ALTER INDEX [PK_TestSet_Now] ON
[dbo].[TestSet_Now] REBUILD WITH ( PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  =
OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON, SORT_IN_TEMPDB = OFF,
ONLINE = OFF )

" failed with the following error: "Transaction (Process ID 66) was deadlocked
on lock resources with another process and has been chosen as the deadlock
victim. Rerun the transaction.". Possible failure reasons: Problems with the
query, "ResultSet" property not set correctly, parameters not set correctly, or
connection not established correctly.

Kindly  help me on this to get it resolved.

Regards

Senthil

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]











[Non-text portions of this message have been removed]

Radhey,

//Take the database into the single user mode run the index rebuild and then
agin back to the multi user mode
This is the standard procedure to rebuild index in the production//

This approach will not work in OLTP systems which requires 24/7 availability. If
you put in single user mode it will be a complete down time for the application.
The better approach would be to run the reindex during which the system is used
minimally.

  With :))s
Santhosh Kumar S.J - MCITP
ReadMe @ sqlspy.blogspot.com
ReadMe @ santhoshpakkangal.blogspot.com




________________________________
From: Radhye <radhye@...>
To: sqlcon@yahoogroups.com
Sent: Fri, 24 September, 2010 3:34:42 PM
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan


This error comes when other process run or other user trying to run or execute
command when index rebuild is going to start or on the activation time.Also when
you start the index already the process doing something in the same database /
table and hold the page ...


Take the database into the single user mode run the index rebuild and then agin
back to the multi user mode
This is the standard procedure to rebuild index in the production

Radhye..

--- On Fri, 9/24/10, muthu narayanan <avm_narayanan@...> wrote:

From: muthu narayanan <avm_narayanan@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, September 24, 2010, 2:21 PM



HI ,

   You can enable the trace flag by running this command

    dbcc traceon (1222,-1)

  or add it start up parameter in SQL Server

Thanks,
Muthu

--- On Fri, 24/9/10, Senthil Kumar K <mail.ksenthil@...> wrote:

From: Senthil Kumar K <mail.ksenthil@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, 24 September, 2010, 11:39 AM



Hi Mohd,

Thanks for the reply and making me to understand. Could you please tell me how
enable the trace flag 1222 by DBCC TRACEON command and in detail.

Regards
Senthil

--- On Fri, 24/9/10, mohd rizwan <mo2riz@...> wrote:

From: mohd rizwan <mo2riz@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, 24 September, 2010, 1:46 AM



HI Sentil,



Error itself telling that your process has been killed as a Dead Lock victim. It
means at the same time you are running some other process or jobs also, that is
creating dead lock. You can check those...or if you want to catch dead lock
information....enable the trace flag 1222 by DBCC TRACEON command. This trace
will log all dead lock information in your sql server error log.

Thanks & Regards,

Mohd Rizwan

(¨`·.·´¨) Always

`·.¸(¨`·.·´¨) Keep

(¨`·.·´¨)¸.·´ Smiling!

`·.¸.·´

--- On Thu, 23/9/10, Senthil Kumar K <mail.ksenthil@...> wrote:

From: Senthil Kumar K <mail.ksenthil@...>

Subject: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan

To: sqlcon@yahoogroups.com

Cc: mail.ksenthil@...

Date: Thursday, 23 September, 2010, 1:08 PM



Hi Friends,

I am new to SQL Server Administration.

I have created the Daily Maintenance plan as below and the Rebuild Index task
fails once in a week.

Backup Database Task - All Databases --> Maintenance Cleanup Task - Older than 1
weeks --> Check Database Integrity Task - Include Indexes --> Shrink Database
Task - All Databases --> Rebuild Index Task - Object Tables and Views --> Update
Statistics Full Scan

Now once or twice in a week the Rebuild Index Task is fails as below

Failed:(-1073548784) Executing the query "ALTER INDEX [PK_TestSet_Now] ON
[dbo].[TestSet_Now] REBUILD WITH ( PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  =
OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON, SORT_IN_TEMPDB = OFF, ONLINE
= OFF )

" failed with the following error: "Transaction (Process ID 66) was deadlocked
on lock resources with another process and has been chosen as the deadlock
victim. Rerun the transaction.". Possible failure reasons: Problems with the
query, "ResultSet" property not set correctly, parameters not set correctly, or
connection not established correctly.

Kindly  help me on this to get it resolved.

Regards

Senthil

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]

If there is no down time in production for rebuild index and other maintaince
work , then what can I say :)
 


--- On Fri, 9/24/10, Santhosh <san_spy@...> wrote:


From: Santhosh <san_spy@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, September 24, 2010, 3:50 PM


 



Radhey,

//Take the database into the single user mode run the index rebuild and then
agin back to the multi user mode
This is the standard procedure to rebuild index in the production//

This approach will not work in OLTP systems which requires 24/7 availability. If
you put in single user mode it will be a complete down time for the application.
The better approach would be to run the reindex during which the system is used
minimally.

With :))s
Santhosh Kumar S.J - MCITP
ReadMe @ sqlspy.blogspot.com
ReadMe @ santhoshpakkangal.blogspot.com

________________________________
From: Radhye <radhye@...>
To: sqlcon@yahoogroups.com
Sent: Fri, 24 September, 2010 3:34:42 PM
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan

This error comes when other process run or other user trying to run or execute
command when index rebuild is going to start or on the activation time.Also when
you start the index already the process doing something in the same database /
table and hold the page ...


Take the database into the single user mode run the index rebuild and then agin
back to the multi user mode
This is the standard procedure to rebuild index in the production

Radhye..

--- On Fri, 9/24/10, muthu narayanan <avm_narayanan@...> wrote:

From: muthu narayanan <avm_narayanan@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, September 24, 2010, 2:21 PM

HI ,

You can enable the trace flag by running this command

dbcc traceon (1222,-1)

or add it start up parameter in SQL Server

Thanks,
Muthu

--- On Fri, 24/9/10, Senthil Kumar K <mail.ksenthil@...> wrote:

From: Senthil Kumar K <mail.ksenthil@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, 24 September, 2010, 11:39 AM

Hi Mohd,

Thanks for the reply and making me to understand. Could you please tell me how
enable the trace flag 1222 by DBCC TRACEON command and in detail.

Regards
Senthil

--- On Fri, 24/9/10, mohd rizwan <mo2riz@...> wrote:

From: mohd rizwan <mo2riz@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, 24 September, 2010, 1:46 AM

HI Sentil,

Error itself telling that your process has been killed as a Dead Lock victim. It
means at the same time you are running some other process or jobs also, that is
creating dead lock. You can check those...or if you want to catch dead lock
information....enable the trace flag 1222 by DBCC TRACEON command. This trace
will log all dead lock information in your sql server error log.

Thanks & Regards,

Mohd Rizwan

(¨`·.·´¨) Always

`·.¸(¨`·.·´¨) Keep

(¨`·.·´¨)¸.·´ Smiling!

`·.¸.·´

--- On Thu, 23/9/10, Senthil Kumar K <mail.ksenthil@...> wrote:

From: Senthil Kumar K <mail.ksenthil@...>

Subject: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan

To: sqlcon@yahoogroups.com

Cc: mail.ksenthil@...

Date: Thursday, 23 September, 2010, 1:08 PM

Hi Friends,

I am new to SQL Server Administration.

I have created the Daily Maintenance plan as below and the Rebuild Index task
fails once in a week.

Backup Database Task - All Databases --> Maintenance Cleanup Task - Older than 1
weeks --> Check Database Integrity Task - Include Indexes --> Shrink Database
Task - All Databases --> Rebuild Index Task - Object Tables and Views --> Update
Statistics Full Scan

Now once or twice in a week the Rebuild Index Task is fails as below

Failed:(-1073548784) Executing the query "ALTER INDEX [PK_TestSet_Now] ON
[dbo].[TestSet_Now] REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE =
OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE
= OFF )

" failed with the following error: "Transaction (Process ID 66) was deadlocked
on lock resources with another process and has been chosen as the deadlock
victim. Rerun the transaction.". Possible failure reasons: Problems with the
query, "ResultSet" property not set correctly, parameters not set correctly, or
connection not established correctly.

Kindly help me on this to get it resolved.

Regards

Senthil

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]











[Non-text portions of this message have been removed]

Thanks to all

--- On Fri, 24/9/10, Santhosh <san_spy@...> wrote:

From: Santhosh <san_spy@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, 24 September, 2010, 3:50 PM







 









       Radhey,



//Take the database into the single user mode run the index rebuild and then

agin back to the multi user mode

This is the standard procedure to rebuild index in the production//



This approach will not work in OLTP systems which requires 24/7 availability. If

you put in single user mode it will be a complete down time for the application.

The better approach would be to run the reindex during which the system is used

minimally.



With :))s

Santhosh Kumar S.J - MCITP

ReadMe @ sqlspy.blogspot.com

ReadMe @ santhoshpakkangal.blogspot.com



________________________________

From: Radhye <radhye@...>

To: sqlcon@yahoogroups.com

Sent: Fri, 24 September, 2010 3:34:42 PM

Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan



This error comes when other process run or other user trying to run or execute

command when index rebuild is going to start or on the activation time.Also when

you start the index already the process doing something in the same database /

table and hold the page ...





Take the database into the single user mode run the index rebuild and then agin

back to the multi user mode

This is the standard procedure to rebuild index in the production



Radhye..



--- On Fri, 9/24/10, muthu narayanan <avm_narayanan@...> wrote:



From: muthu narayanan <avm_narayanan@...>

Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan

To: sqlcon@yahoogroups.com

Date: Friday, September 24, 2010, 2:21 PM



HI ,



   You can enable the trace flag by running this command



    dbcc traceon (1222,-1)



  or add it start up parameter in SQL Server



Thanks,

Muthu



--- On Fri, 24/9/10, Senthil Kumar K <mail.ksenthil@...> wrote:



From: Senthil Kumar K <mail.ksenthil@...>

Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan

To: sqlcon@yahoogroups.com

Date: Friday, 24 September, 2010, 11:39 AM



Hi Mohd,



Thanks for the reply and making me to understand. Could you please tell me how

enable the trace flag 1222 by DBCC TRACEON command and in detail.



Regards

Senthil



--- On Fri, 24/9/10, mohd rizwan <mo2riz@...> wrote:



From: mohd rizwan <mo2riz@...>

Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan

To: sqlcon@yahoogroups.com

Date: Friday, 24 September, 2010, 1:46 AM



HI Sentil,



Error itself telling that your process has been killed as a Dead Lock victim. It

means at the same time you are running some other process or jobs also, that is

creating dead lock. You can check those...or if you want to catch dead lock

information....enable the trace flag 1222 by DBCC TRACEON command. This trace

will log all dead lock information in your sql server error log.



Thanks & Regards,



Mohd Rizwan



(¨`·.·´¨) Always



`·.¸(¨`·.·´¨) Keep



(¨`·.·´¨)¸.·´ Smiling!



`·.¸.·´



--- On Thu, 23/9/10, Senthil Kumar K <mail.ksenthil@...> wrote:



From: Senthil Kumar K <mail.ksenthil@...>



Subject: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan



To: sqlcon@yahoogroups.com



Cc: mail.ksenthil@...



Date: Thursday, 23 September, 2010, 1:08 PM



Hi Friends,



I am new to SQL Server Administration.



I have created the Daily Maintenance plan as below and the Rebuild Index task

fails once in a week.



Backup Database Task - All Databases --> Maintenance Cleanup Task - Older than 1

weeks --> Check Database Integrity Task - Include Indexes --> Shrink Database

Task - All Databases --> Rebuild Index Task - Object Tables and Views --> Update

Statistics Full Scan



Now once or twice in a week the Rebuild Index Task is fails as below



Failed:(-1073548784) Executing the query "ALTER INDEX [PK_TestSet_Now] ON

[dbo].[TestSet_Now] REBUILD WITH ( PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  =

OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON, SORT_IN_TEMPDB = OFF, ONLINE

= OFF )



" failed with the following error: "Transaction (Process ID 66) was deadlocked

on lock resources with another process and has been chosen as the deadlock

victim. Rerun the transaction.". Possible failure reasons: Problems with the

query, "ResultSet" property not set correctly, parameters not set correctly, or

connection not established correctly.



Kindly  help me on this to get it resolved.



Regards



Senthil



[Non-text portions of this message have been removed]



[Non-text portions of this message have been removed]



[Non-text portions of this message have been removed]



[Non-text portions of this message have been removed]



[Non-text portions of this message have been removed]



[Non-text portions of this message have been removed]
























[Non-text portions of this message have been removed]

Noticed
  that everyday my Maintenance Plan log is empty as below even all the tasks
Succeeded. The Maintenance Plan has the following tasks

Backup
Database Task  --> Maintenance Cleanup Task  --> Check Database
Integrity Task --> Shrink Database Task --> Rebuild Index Task
--> Update Statistics Full Scan

Log:
===
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.1399
Report was generated on "SERVERNAME".
Maintenance Plan: BackupMaintenancePlan
Duration: 00:00:00
Status: Succeeded.
Details:

When the rebuild index task fails the complete log is available, otherwise the
log will be empty.

Please let me know what could be the issue and how to solve this.

Regards
Senthil




[Non-text portions of this message have been removed]

Thats how most of the systems in the world work :).. we cant have a real down
time but will have times where there will be minimal activity in the DB..

  With :))s
Santhosh Kumar S.J - MCTS
ReadMe @ sqlspy.blogspot.com
ReadMe @ santhoshpakkangal.blogspot.com




________________________________
From: Radhye <radhye@...>
To: sqlcon@yahoogroups.com
Sent: Fri, 24 September, 2010 4:22:34 PM
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan


If there is no down time in production for rebuild index and other maintaince
work , then what can I say :)


--- On Fri, 9/24/10, Santhosh <san_spy@...> wrote:

From: Santhosh <san_spy@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, September 24, 2010, 3:50 PM



Radhey,

//Take the database into the single user mode run the index rebuild and then
agin back to the multi user mode
This is the standard procedure to rebuild index in the production//

This approach will not work in OLTP systems which requires 24/7 availability. If

you put in single user mode it will be a complete down time for the application.

The better approach would be to run the reindex during which the system is used
minimally.

With :))s
Santhosh Kumar S.J - MCITP
ReadMe @ sqlspy.blogspot.com
ReadMe @ santhoshpakkangal.blogspot.com

________________________________
From: Radhye <radhye@...>
To: sqlcon@yahoogroups.com
Sent: Fri, 24 September, 2010 3:34:42 PM
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan

This error comes when other process run or other user trying to run or execute
command when index rebuild is going to start or on the activation time.Also when

you start the index already the process doing something in the same database /
table and hold the page ...

Take the database into the single user mode run the index rebuild and then agin
back to the multi user mode
This is the standard procedure to rebuild index in the production

Radhye..

--- On Fri, 9/24/10, muthu narayanan <avm_narayanan@...> wrote:

From: muthu narayanan <avm_narayanan@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, September 24, 2010, 2:21 PM

HI ,

You can enable the trace flag by running this command

dbcc traceon (1222,-1)

or add it start up parameter in SQL Server

Thanks,
Muthu

--- On Fri, 24/9/10, Senthil Kumar K <mail.ksenthil@...> wrote:

From: Senthil Kumar K <mail.ksenthil@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, 24 September, 2010, 11:39 AM

Hi Mohd,

Thanks for the reply and making me to understand. Could you please tell me how
enable the trace flag 1222 by DBCC TRACEON command and in detail.

Regards
Senthil

--- On Fri, 24/9/10, mohd rizwan <mo2riz@...> wrote:

From: mohd rizwan <mo2riz@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, 24 September, 2010, 1:46 AM

HI Sentil,

Error itself telling that your process has been killed as a Dead Lock victim. It

means at the same time you are running some other process or jobs also, that is
creating dead lock. You can check those...or if you want to catch dead lock
information....enable the trace flag 1222 by DBCC TRACEON command. This trace
will log all dead lock information in your sql server error log.

Thanks & Regards,

Mohd Rizwan

(¨`·.·´¨) Always

`·.¸(¨`·.·´¨) Keep

(¨`·.·´¨)¸.·´ Smiling!

`·.¸.·´

--- On Thu, 23/9/10, Senthil Kumar K <mail.ksenthil@...> wrote:

From: Senthil Kumar K <mail.ksenthil@...>

Subject: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan

To: sqlcon@yahoogroups.com

Cc: mail.ksenthil@...

Date: Thursday, 23 September, 2010, 1:08 PM

Hi Friends,

I am new to SQL Server Administration.

I have created the Daily Maintenance plan as below and the Rebuild Index task
fails once in a week.

Backup Database Task - All Databases --> Maintenance Cleanup Task - Older than 1

weeks --> Check Database Integrity Task - Include Indexes --> Shrink Database
Task - All Databases --> Rebuild Index Task - Object Tables and Views --> Update

Statistics Full Scan

Now once or twice in a week the Rebuild Index Task is fails as below

Failed:(-1073548784) Executing the query "ALTER INDEX [PK_TestSet_Now] ON
[dbo].[TestSet_Now] REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE =
OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE
= OFF )

" failed with the following error: "Transaction (Process ID 66) was deadlocked
on lock resources with another process and has been chosen as the deadlock
victim. Rerun the transaction.". Possible failure reasons: Problems with the
query, "ResultSet" property not set correctly, parameters not set correctly, or
connection not established correctly.

Kindly help me on this to get it resolved.

Regards

Senthil

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]

What kind of information u r looking for  if the job get succeeded.
 
Thanks,
Muthu
--- On Fri, 24/9/10, Senthil Kumar K <mail.ksenthil@...> wrote:


From: Senthil Kumar K <mail.ksenthil@...>
Subject: MUGH-SQLCON Maintenance Plan log is empty
To: sqlcon@yahoogroups.com
Date: Friday, 24 September, 2010, 4:26 PM


 



Noticed
that everyday my Maintenance Plan log is empty as below even all the tasks
Succeeded. The Maintenance Plan has the following tasks

Backup
Database Task --> Maintenance Cleanup Task --> Check Database
Integrity Task --> Shrink Database Task --> Rebuild Index Task
--> Update Statistics Full Scan

Log:
===
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.1399
Report was generated on "SERVERNAME".
Maintenance Plan: BackupMaintenancePlan
Duration: 00:00:00
Status: Succeeded.
Details:

When the rebuild index task fails the complete log is available, otherwise the
log will be empty.

Please let me know what could be the issue and how to solve this.

Regards
Senthil

[Non-text portions of this message have been removed]










[Non-text portions of this message have been removed]

if issue is because of deadlock, the reindex job gets fail, then solution is,we
have to think which contending sql statement creating deadlock victim.
 
if  the server has sql server 2008.
then link will help you out in finding deadlock contending sql statement. 
http://www.sqlservercentral.com/articles/deadlock/65658/
 
rest you can do later on..
 
with regards
Rakesh.
 


--- On Fri, 24/9/10, Santhosh <san_spy@...> wrote:


From: Santhosh <san_spy@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, 24 September, 2010, 4:26 PM


 



Thats how most of the systems in the world work :).. we cant have a real down
time but will have times where there will be minimal activity in the DB..

With :))s
Santhosh Kumar S.J - MCTS
ReadMe @ sqlspy.blogspot.com
ReadMe @ santhoshpakkangal.blogspot.com

________________________________
From: Radhye <radhye@...>
To: sqlcon@yahoogroups.com
Sent: Fri, 24 September, 2010 4:22:34 PM
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan

If there is no down time in production for rebuild index and other maintaince
work , then what can I say :)


--- On Fri, 9/24/10, Santhosh <san_spy@...> wrote:

From: Santhosh <san_spy@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, September 24, 2010, 3:50 PM

Radhey,

//Take the database into the single user mode run the index rebuild and then
agin back to the multi user mode
This is the standard procedure to rebuild index in the production//

This approach will not work in OLTP systems which requires 24/7 availability. If

you put in single user mode it will be a complete down time for the application.

The better approach would be to run the reindex during which the system is used
minimally.

With :))s
Santhosh Kumar S.J - MCITP
ReadMe @ sqlspy.blogspot.com
ReadMe @ santhoshpakkangal.blogspot.com

________________________________
From: Radhye <radhye@...>
To: sqlcon@yahoogroups.com
Sent: Fri, 24 September, 2010 3:34:42 PM
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan

This error comes when other process run or other user trying to run or execute
command when index rebuild is going to start or on the activation time.Also when

you start the index already the process doing something in the same database /
table and hold the page ...

Take the database into the single user mode run the index rebuild and then agin
back to the multi user mode
This is the standard procedure to rebuild index in the production

Radhye..

--- On Fri, 9/24/10, muthu narayanan <avm_narayanan@...> wrote:

From: muthu narayanan <avm_narayanan@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, September 24, 2010, 2:21 PM

HI ,

You can enable the trace flag by running this command

dbcc traceon (1222,-1)

or add it start up parameter in SQL Server

Thanks,
Muthu

--- On Fri, 24/9/10, Senthil Kumar K <mail.ksenthil@...> wrote:

From: Senthil Kumar K <mail.ksenthil@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, 24 September, 2010, 11:39 AM

Hi Mohd,

Thanks for the reply and making me to understand. Could you please tell me how
enable the trace flag 1222 by DBCC TRACEON command and in detail.

Regards
Senthil

--- On Fri, 24/9/10, mohd rizwan <mo2riz@...> wrote:

From: mohd rizwan <mo2riz@...>
Subject: Re: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan
To: sqlcon@yahoogroups.com
Date: Friday, 24 September, 2010, 1:46 AM

HI Sentil,

Error itself telling that your process has been killed as a Dead Lock victim. It

means at the same time you are running some other process or jobs also, that is
creating dead lock. You can check those...or if you want to catch dead lock
information....enable the trace flag 1222 by DBCC TRACEON command. This trace
will log all dead lock information in your sql server error log.

Thanks & Regards,

Mohd Rizwan

(¨`·.·´¨) Always

`·.¸(¨`·.·´¨) Keep

(¨`·.·´¨)¸.·´ Smiling!

`·.¸.·´

--- On Thu, 23/9/10, Senthil Kumar K <mail.ksenthil@...> wrote:

From: Senthil Kumar K <mail.ksenthil@...>

Subject: MUGH-SQLCON Rebuild index Task fails in Maintenance Plan

To: sqlcon@yahoogroups.com

Cc: mail.ksenthil@...

Date: Thursday, 23 September, 2010, 1:08 PM

Hi Friends,

I am new to SQL Server Administration.

I have created the Daily Maintenance plan as below and the Rebuild Index task
fails once in a week.

Backup Database Task - All Databases --> Maintenance Cleanup Task - Older than 1

weeks --> Check Database Integrity Task - Include Indexes --> Shrink Database
Task - All Databases --> Rebuild Index Task - Object Tables and Views --> Update

Statistics Full Scan

Now once or twice in a week the Rebuild Index Task is fails as below

Failed:(-1073548784) Executing the query "ALTER INDEX [PK_TestSet_Now] ON
[dbo].[TestSet_Now] REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE =
OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE
= OFF )

" failed with the following error: "Transaction (Process ID 66) was deadlocked
on lock resources with another process and has been chosen as the deadlock
victim. Rerun the transaction.". Possible failure reasons: Problems with the
query, "ResultSet" property not set correctly, parameters not set correctly, or
connection not established correctly.

Kindly help me on this to get it resolved.

Regards

Senthil

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]










[Non-text portions of this message have been removed]

attachment plz

--- On Thu, 23/9/10, Shashi Kumar Singh <singh.shashikumar2@...> wrote:

From: Shashi Kumar Singh <singh.shashikumar2@...>
Subject: Re: MUGH-SQLCON SQL DBA Requirement: Adobe Systems, Noida
To: sqlcon@yahoogroups.com
Date: Thursday, 23 September, 2010, 12:16 PM

Hi Bhavesh,

Here is my updated cv and hope it will match with your requirement.

On Sun, Sep 19, 2010 at 4:10 PM, bhavesh prajapati <
bhavesh2984groups@...> wrote:

>
>
> Friends,
>
> Adobe Systems (www.adobe.com ) has an open position for SQL DBA.
> Location - NOIDA
> Experience: 5+ years
>
> If interested, send resume to bhavesh@... <bhavesh%40adobe.com>
>
> Regards,
> Bhavesh
>
> [Non-text portions of this message have been removed]
>
> 
>



--

Thanks & Regards

Shashi Kumar Singh
Senior System Engineer
IBM India (P)Ltd.
Email:singh.shashikumar2@... <Email%3Asingh.shashikumar2@...>,
shashi_120@...


[Non-text portions of this message have been removed]



------------------------------------

SqlCon is a special interests group run under the aegis of MUGH -
http://www.mugh.net:http://www.mugh.net/sql

Visit www.sqlindia.com :: The first Countrywide initiative on SQL technologies.
Get recognised and be a part of it.


Yahoo! Groups Links







[Non-text portions of this message have been removed]

Hi Guys,
 
  I need your help to fix the logshipping issue in my setup.
 
 We have configured the logshipping in our evn.Database size is 6TB. 
 
 Backup,copy,restore jobs are running every 10 mins. Yesterday we deleted one of
the
 
Tlog backup file in the primary which is not copied to secondry. It caused the
logshipping out of sync till now.
 
Pls throw ur recommendations.Thanks in Advance
 
Thanks,
Muthu



[Non-text portions of this message have been removed]

Hi,

      Are the backups going into tape from the shared location. If you have
then you can ask your backup team to restore the file and you can make them
in sync. If you dont then you need to take the full backup and start it
again.

Thanks
Mohan




On Wed, Oct 6, 2010 at 8:22 AM, muthu narayanan
<avm_narayanan@...>wrote:

>
>
> Hi Guys,
>
>   I need your help to fix the logshipping issue in my setup.
>
>  We have configured the logshipping in our evn.Database size is 6TB.
>
>  Backup,copy,restore jobs are running every 10 mins. Yesterday we deleted
> one of the
>
> Tlog backup file in the primary which is not copied to secondry. It caused
> the logshipping out of sync till now.
>
> Pls throw ur recommendations.Thanks in Advance
>
> Thanks,
> Muthu
>
> [Non-text portions of this message have been removed]
>
>
>


[Non-text portions of this message have been removed]

Hi Mohan,
 
Tlog backup is going to share folder and it  had been working fine till
yesterday. We deleted  one log backup file is not copied from  primary to
secondry.
 
 
Thanks,
Muthu 

--- On Wed, 6/10/10, Chandra Mohan <chandramohannvc@...> wrote:


From: Chandra Mohan <chandramohannvc@...>
Subject: Re: MUGH-SQLCON Need a help
To: sqlcon@yahoogroups.com
Date: Wednesday, 6 October, 2010, 11:49 AM


Hi,

     Are the backups going into tape from the shared location. If you have
then you can ask your backup team to restore the file and you can make them
in sync. If you dont then you need to take the full backup and start it
again.

Thanks
Mohan




On Wed, Oct 6, 2010 at 8:22 AM, muthu narayanan
<avm_narayanan@...>wrote:

>
>
> Hi Guys,
>
>   I need your help to fix the logshipping issue in my setup.
>
>  We have configured the logshipping in our evn.Database size is 6TB.
>
>  Backup,copy,restore jobs are running every 10 mins. Yesterday we deleted
> one of the
>
> Tlog backup file in the primary which is not copied to secondry. It caused
> the logshipping out of sync till now.
>
> Pls throw ur recommendations.Thanks in Advance
>
> Thanks,
> Muthu
>
> [Non-text portions of this message have been removed]
>
>
>


[Non-text portions of this message have been removed]



------------------------------------

SqlCon is a special interests group run under the aegis of MUGH -
http://www.mugh.net:http://www.mugh.net/sql

Visit www.sqlindia.com :: The first Countrywide initiative on SQL technologies.
Get recognised and be a part of it.


Yahoo! Groups Links







[Non-text portions of this message have been removed]

If you have lost the transaction log backup file then you dont have any option
other than, taking a full backup and restoring and recreating the logshipping.

  With :))s
Santhosh Kumar S.J - MCITP
ReadMe @ sqlspy.blogspot.com
ReadMe @ santhoshpakkangal.blogspot.com




________________________________
From: muthu narayanan <avm_narayanan@...>
To: sqlcon@yahoogroups.com
Sent: Wed, 6 October, 2010 12:48:56 PM
Subject: Re: MUGH-SQLCON Need a help


Hi Mohan,

Tlog backup is going to share folder and it  had been working fine till
yesterday. We deleted  one log backup file is not copied from  primary to
secondry.


Thanks,
Muthu

--- On Wed, 6/10/10, Chandra Mohan <chandramohannvc@...> wrote:

From: Chandra Mohan <chandramohannvc@...>
Subject: Re: MUGH-SQLCON Need a help
To: sqlcon@yahoogroups.com
Date: Wednesday, 6 October, 2010, 11:49 AM

Hi,

      Are the backups going into tape from the shared location. If you have
then you can ask your backup team to restore the file and you can make them
in sync. If you dont then you need to take the full backup and start it
again.

Thanks
Mohan

On Wed, Oct 6, 2010 at 8:22 AM, muthu narayanan
<avm_narayanan@...>wrote:

>
>
> Hi Guys,
>
>   I need your help to fix the logshipping issue in my setup.
>
>  We have configured the logshipping in our evn.Database size is 6TB.
>
>  Backup,copy,restore jobs are running every 10 mins. Yesterday we deleted
> one of the
>
> Tlog backup file in the primary which is not copied to secondry. It caused
> the logshipping out of sync till now.
>
> Pls throw ur recommendations.Thanks in Advance
>
> Thanks,
> Muthu
>
> [Non-text portions of this message have been removed]
>
>
>

[Non-text portions of this message have been removed]

------------------------------------

SqlCon is a special interests group run under the aegis of MUGH -
http://www.mugh.net:http://www.mugh.net/sql

Visit www.sqlindia.com :: The first Countrywide initiative on SQL technologies.
Get recognised and be a part of it.

Yahoo! Groups Links

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]

Thanks for your information . I have found that one . sinc it is 6 TB database 
,it is very difficult to do that
 
Thanks,
Muthu

--- On Wed, 6/10/10, Santhosh <san_spy@...> wrote:


From: Santhosh <san_spy@...>
Subject: Re: MUGH-SQLCON Need a help
To: sqlcon@yahoogroups.com
Date: Wednesday, 6 October, 2010, 1:07 PM


 



If you have lost the transaction log backup file then you dont have any option
other than, taking a full backup and restoring and recreating the logshipping.

With :))s
Santhosh Kumar S.J - MCITP
ReadMe @ sqlspy.blogspot.com
ReadMe @ santhoshpakkangal.blogspot.com

________________________________
From: muthu narayanan <avm_narayanan@...>
To: sqlcon@yahoogroups.com
Sent: Wed, 6 October, 2010 12:48:56 PM
Subject: Re: MUGH-SQLCON Need a help

Hi Mohan,

Tlog backup is going to share folder and it had been working fine till
yesterday. We deleted one log backup file is not copied from primary to
secondry.


Thanks,
Muthu

--- On Wed, 6/10/10, Chandra Mohan <chandramohannvc@...> wrote:

From: Chandra Mohan <chandramohannvc@...>
Subject: Re: MUGH-SQLCON Need a help
To: sqlcon@yahoogroups.com
Date: Wednesday, 6 October, 2010, 11:49 AM

Hi,

Are the backups going into tape from the shared location. If you have
then you can ask your backup team to restore the file and you can make them
in sync. If you dont then you need to take the full backup and start it
again.

Thanks
Mohan

On Wed, Oct 6, 2010 at 8:22 AM, muthu narayanan
<avm_narayanan@...>wrote:

>
>
> Hi Guys,
>
> I need your help to fix the logshipping issue in my setup.
>
> We have configured the logshipping in our evn.Database size is 6TB.
>
> Backup,copy,restore jobs are running every 10 mins. Yesterday we deleted
> one of the
>
> Tlog backup file in the primary which is not copied to secondry. It caused
> the logshipping out of sync till now.
>
> Pls throw ur recommendations.Thanks in Advance
>
> Thanks,
> Muthu
>
> [Non-text portions of this message have been removed]
>
>
>

[Non-text portions of this message have been removed]

------------------------------------

SqlCon is a special interests group run under the aegis of MUGH -
http://www.mugh.net:http://www.mugh.net/sql

Visit www.sqlindia.com :: The first Countrywide initiative on SQL technologies.
Get recognised and be a part of it.

Yahoo! Groups Links

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]










[Non-text portions of this message have been removed]

http://zyrevota.tripod.com/zanudo.html You WontBe liv eYourN ewIn come

Hi

Please tell if u know
How many instances sqlserver 2008 supports exactly?



thanks®ards
kishore

For stand-alone server, it's 50 instances for all editions. Pls refer the below
link for details:
http://msdn.microsoft.com/en-us/library/ms143432.aspx
  Regards,
Vijay
MCDBA, MCTS

________________________________
From: Krishna_ <sv_39@...>
To: sqlcon@yahoogroups.com
Sent: Wed, October 6, 2010 7:27:27 PM
Subject: MUGH-SQLCON number of instances in sqlserver2008


Hi

Please tell if u know
How many instances sqlserver 2008 supports exactly?

thanks®ards
kishore







[Non-text portions of this message have been removed]

http://migre.me/1wGLg

http://qotosune.t35.com/




[Non-text portions of this message have been removed]