Viewing 15 posts - 2,191 through 2,205 (of 2,463 total)
thanks . it worked for me 🙂
February 10, 2010 at 2:26 am
yes i was restoring MSDB for login and jobs perspective.
February 8, 2010 at 11:07 pm
i didnt try to restore the MSDB instead i transfered jobs with SSIS package.
February 7, 2010 at 10:57 pm
Grant
, isnt it different objected creating whenevr we create a index on view. bcoz i read some where that whever we create any indexed view, sql server will...
February 7, 2010 at 10:49 pm
Vyas, i was telling the same thing as grant Frithcey mentioned in his first reply.
February 7, 2010 at 10:47 pm
version are different , as mentioned in prior post
February 5, 2010 at 6:19 am
i guess , destination drive will have enough space
February 5, 2010 at 3:56 am
vyas (2/5/2010)
We had a table with 11 million records which is highly transactional.
As above line depicts , this is transactional table, i guess
February 5, 2010 at 3:27 am
Sure, whenever you create index on any transactional table , it will degrade the performance.
because whenever DML operation performed on this table , index will get updated.
February 5, 2010 at 3:02 am
no that cant be done , just for a one delete operation .
on every run, creating indexes is not at all possible and recommended.
February 4, 2010 at 5:15 am
this table contains around 20 millions of records.
the statistics are being updated on daily basis
February 4, 2010 at 5:13 am
can u post different indexes associated with tables?
. i guess someone had asked for the same earlier.
February 3, 2010 at 10:08 pm
Does it mean that if space available and for temporary storing purpose, we can store milions of record in table variable? (this is just hypothentical scenario )
and second ques, whenever...
February 3, 2010 at 12:03 am
No it doesn't. The reason that table variables perform poorly on large row counts is because they have no statistics and hence the optimiser comes up with really, really bad...
February 2, 2010 at 9:51 pm
Viewing 15 posts - 2,191 through 2,205 (of 2,463 total)