corrupt log file?

can someone please help with this? i have a store whose log file (.ldf file) which has grown out of control. the database size is 1.2gb and the log file is 560mb. i am trying to switch to a new pc but this seems to be causing issues and i can not create the database on the new machine from the backup as recommended. does anyone have an idea of how to fix this log growth problem?

Thanks,

Jim

Reply to
WallOfFame
Loading thread data ...

Jim,

The log growth problem is most probably coz of the "Recovery Model", please right click on the DB then Properties|Options then change the recovery model from "Full" to "Simple"

The next step is to shrink the log file, right click on the DB then Tasks|Shrink|Files and shrink the log file to the minimum

Reply to
Ahmed Nashat

Ahmed,

when i right click on the DB (in the MSDE folders for data and go to properties i do not get "options" and can not find "revocery model". am i looking in the wrong location?

thanks for any help you can provide!

Jim

"Ahmed Nashat" wrote:

Reply to
WallOfFame

you should do it in SQL Server Management Studio (Express) if u have SQL Server 2005, or Enterprise Manager for SQL Server 2000.

Would u plz tell me what version of RMS/SQL u r running?

Reply to
Ahmed Nashat

i am currently running RMS version 1.2 SP3 with sql 2000 (msde version, the free version). can i do what you are telling me to with the version of SQL i am using? if so, could you give me directions? otherwise, can i use a SQL query in Store Operations Administrator?

i really appreciate your help - microsoft can not help with this since my version is no longer supported and we are not at a place where we can upgrade yet.

Thanks again!

Jim

"Ahmed Nashat" wrote:

Reply to
WallOfFame

Reply to
Ahmed Nashat

Ahmed, thanks for your help. this worked on my test machine but something really odd is preventing it from working on my store computer. when i checked the sp_helpfile to find the log file name it does not match to what is in the SQL folder with the database. Inside the sql file folder it shows the log as being gfanc03 but the query returned a log name of gfanc02. i tried to shrink gfanc02 and it says that it can't find the file. i then tried what shows in the sql file folder (gfanc03) and it says that it can not find the file again. this system did apparently crash last year and they hired someone to repair it. i'm think the repair was not done properly and this is part of the problem. can you think of any other way to possibly fix this?

thanks again for all the help!

Jim

"Ahmed Nashat" wrote:

version, u should use the following statements from SO Administrator: -

shrink it: -

Reply to
WallOfFame

i don't know any other way, plz double check what u r doing, i believe u should use the name returned from sp_helpfile regardless to physical file now, i suggest that u use the SQL server newgroup to get better support in this matter

Reply to
Ahmed Nashat

ok, that sounds good. thanks again for all the help you were aboe to provide.

Thanks!

"Ahmed Nashat" wrote:

Reply to
WallOfFame

Reply to
convoluted

Is there a rule of thumb as to how large your Log file should be? Craig

Reply to
Craig

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.