Sybase db refresh
I have sybase db which need to be refresh.
In production it has db size of 200GB, 132 data and 68 log
But in test where I will do refresh, it has old size which 89GB, with 80GB data and 9 GB of log
In production it has db size of 200GB, 132 data and 68 log
But in test where I will do refresh, it has old size which 89GB, with 80GB data and 9 GB of log
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The fragment definitely are not the same, that too much to create same set of fragment again. But if only fragment are not the same but we have same segment, will it still mix data and log ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
hmmm,
How could I proceed with drop and recreate ? I already have db in test which u suggested me to drop this all then recreate it ? anyway how can I generate a db script which identical with our production db ?
Then I'm not so sure how "for load" works , I could google it to find answer / sybase web for better understands
How could I proceed with drop and recreate ? I already have db in test which u suggested me to drop this all then recreate it ? anyway how can I generate a db script which identical with our production db ?
Then I'm not so sure how "for load" works , I could google it to find answer / sybase web for better understands
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm running on ASE 15
ASKER
Hi,
One thing I'm not sure if this db have been created previously using for load or not, is there a way to check this now ? and I'm using ASE 15.0 for both ( prod and test )
One thing I'm not sure if this db have been created previously using for load or not, is there a way to check this now ? and I'm using ASE 15.0 for both ( prod and test )
Actually you should be able to see the data and log segments (with their respective sizes) by using sp_helpdb <db_name>
You can also check sysusages system table in master db to see segments and their size in right sequence.
You can also check sysusages system table in master db to see segments and their size in right sequence.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi Joe,
As of ASE 15 sp_helpdb lists fragments in the right order. Motioneye is running ASE 15. So sp_helpdb should show devices as needed to recreate.
From ASE 15 reference manual:
sp_helpdb
Description
Reports information about a particular database or about all databases.
Syntax
sp_helpdb [dbname [, order]]
Parameters
dbname
is the name of the database on which to report information. Without this optional parameter, sp_helpdb reports on all databases. dbname can include wildcard characters to return all databases that match the specified pattern.
order
The default order of the output is by lstart, which is the order in which the databases were created or altered. Use device_name along with dbname to display the output of sp_helpdb ordered by device_name.
As of ASE 15 sp_helpdb lists fragments in the right order. Motioneye is running ASE 15. So sp_helpdb should show devices as needed to recreate.
From ASE 15 reference manual:
sp_helpdb
Description
Reports information about a particular database or about all databases.
Syntax
sp_helpdb [dbname [, order]]
Parameters
dbname
is the name of the database on which to report information. Without this optional parameter, sp_helpdb reports on all databases. dbname can include wildcard characters to return all databases that match the specified pattern.
order
The default order of the output is by lstart, which is the order in which the databases were created or altered. Use device_name along with dbname to display the output of sp_helpdb ordered by device_name.
Ah, I hadn't noticed that! Good to know, and yes that makes things much easier.
ASKER
I'm copying production to test for a refresh , however in test we have lesser device compare we have in production, but I have added one big chunk ( few disk with 32GB ), will diff number of device cane become a concern for a refresh to complete ?
One question, if I have bigger db size in test will the refresh failed ? do I have to make test have exactly same size with production ? data and log segment ?