@ homebrew

The job 1 is SSIS package

The log size increases considerably.

but the databases (on which iam performing shrink operation ) are all in simple recovery mode.

Regards,

Sushant

@ ovonelmonk...

You just need to take full backups daily night....

The transaction logs are already there from log shipping, on the primary server ..(the LSbackup jobs on primary server)..

I dont think...

@ TST1...

this article describes a good way to do that.

http://www.mssqltips.com/tip.asp?tip=1018

Regards,

Sushant

@ gail

"It'll just give you a convenient column to Order By"

Does that mean identity column??

I heard that indexing on an ORDER BY can help in maintaing the order in...

@ gail

Thanks for letting me know.

Regards,

Sushant

@ jeff

Using select * in first attempt.....good catch...

but acutally there were many more columns also ,which i didnt disclose here, so that way had to mention just the required columns.

Regards,

Sushant

@ jeff

in first table i had approx 7 columns, and the develoepr wanted only few imp colums in a table (around 4-5), so I had to delete the 2-3...

The best practices for system databases is that it is not necessary to backup the tempdb database as it is rebuilt each time SQL Server starts.

The model database should be...

@ gail

Ya, i noticed that there was no use, as the rows were not according to that..(order by) in the new table..

I had to delete 1-2 columns( as per req.)...

@ gail

You asked me why you want to do it , any logical sense

So, i replied that the new table should look nice, similiar to the output from the previous...

@ gail

Just to look good another table without an order by clause..

But ya, the order was random when it copied the data from 1 table to another.

Regards,

Sushant

And also,

How to make a new table from the output of this query?

Regards,

Sushant

@ gail & lowell

Ya,

That was correct, I guess I didnt needed GROUP BY ....

Order by category,price was enough for me...

Thanks.

Regards,

Sushant

@ joie

Msg 2508, Level 16, State 1, Line 2

The In-row data USED page count for object "rtw_count_variance", index ID 0, partition ID 42277782945792, alloc unit ID 42277782945792 (type In-row data)...

on error log i got :"-

DBCC CHECKDB (db name) WITH no_infomsgs executed by domain name \gpsqlagent found 1 errors and repaired 0 errors. Elapsed time: 0 hours 1 minutes 52...