Explanation to The database shrink || 2019

Good JOB :)

Quote:

Originally Posted by NESTA3!! [Only registered and activated users can see links. Click Here To Register...]

if you have a DB using ex: Have server running and this DB Example Name: SRO_VT_SHARD.log its = 100GB + me can shrink database, without harming anything from online players? or that are offline too, I say about missing something, item etc ...

Quote:

Originally Posted by ryaneichner if you have a DB using ex: Have server running and this DB Example Name: SRO_VT_SHARD.log its = 100GB + me can shrink database, without harming anything from online players? or that are offline too, I say about missing something, item etc ...

Quote:

Originally Posted by Xitons Good JOB :)

Quote:

Originally Posted by NESTA3!! [Only registered and activated users can see links. Click Here To Register...]

Since shrink process increasing the fragmentation on some tables, your query performance will f*cked up. Never recommended database shrink.

Its not important how you do that, its important why do you need to shrink.

Quote:

Originally Posted by senua Since shrink process increasing the fragmentation on some tables, your query performance will f*cked up. Never recommended database shrink. Its not important how you do that, its important why do you need to shrink.

Quote:

Originally Posted by NESTA3!! I have tried it more than once but I thought after improvement in database And you can try it yourself On database test You'll notice lot of difference ;)

You can check fragmentations on table after the shrink process. Also, before doing anything i recommended to review microsoft documentation about SQL.

In the case of using vsro database in simple recovery, it won't take much gigabayts. So, shrink process is not needed. But, if you use vsro database in full recovery mode(never recomended since it's going to log whole transation logs). It's really need to shrink vsro database. Also, don't forget to rebuild & reorganize your indexes after the shrink.

Quote:

Originally Posted by senua You can check fragmentations on table after the shrink process. Also, before doing anything i recommended to review microsoft documentation about SQL. In the case of using vsro database in simple recovery, it won't take much gigabayts. So, shrink process is not needed. But, if you use vsro database in full recovery mode(never recomended since it's going to log whole transation logs). It's really need to shrink vsro database. Also, don't forget to rebuild & reorganize your indexes after the shrink.