HQ Database at size limit

Alarmingly, I just hit the 2GB limit for HQ Server. I am going to upgrade to SQL Express, but I have not even been using HQ for a year with 4 stores. I can't believe my database is so large already. What happens in companies with dozens of stores? It seems like the HQ database would be over the size limit in a matter of weeks.

How can I quickly and immediately decrease size without losing too much?

Reply to
Jason
Loading thread data ...

I guess I can forget about anything to immediately reduce the database size. I can't even run a SQL statement/query on the database because it is at the limit. HQ Admin just gives an error that the file can't be open.

So... first step is to upgrade to SQL Express 2005. Then I get the terrifying task to see if the database will work or if it will be corrupted. Anyone have any good news for me on this?

My partner sure didn't warn me about this fiasco that I would have to deal with in less than a year. They claim to have sold more copies of RMS than anyone. Surely they should have advised me of this serious limitation.

Reply to
Jason

Update: My worst nightmare has been averted.

After upgrading to SQL Express I had a scare when the database would not open. After a reboot it opened normally. I am validating the data, but it seems to be fine so far.

However, 401's from all of my stores are still failing due to "Error

2147217900: Could not allocate space for object 'HQEventLog' in database '4DHQ' because the 'PRIMARY' filegroup is full."

I suspect that this is occuring because SQLExpress is not increasing the database size automatically for some reason. How can I manually increase the database size to see if this corrects the problem (and set it up to automatically increase the database size in the future)?

Reply to
Jason

Hi Jason, I recommend installing full SQL rather than SQL Server Express. This is standard in all multi-store installation in my experience.

Regards, Todd

Reply to
Todd

If that is the case, then Microsoft should bundle full SQL with RMS HQ because partners are duping thier customers by not telling them about this significant cost in thier near futures.

I do not accept this as an answer. The product should WORK as sold to me. This limitation is advertised NOWHERE to the customer. It borders on bait and switch tactics.

Has anyone ever sued MS over RMS that anyone know of?

Reply to
Jason

Update: My worst nightmare has been averted.

After upgrading to SQL Express I had a scare when the database would not open. After a reboot it opened normally. I am validating the data, but it seems to be fine so far.

However, 401's from all of my stores are still failing due to "Error 2147217900: Could not allocate space for object 'HQEventLog' in database '4DHQ' because the 'PRIMARY' filegroup is full."

I suspect that this is occuring because SQLExpress is not increasing the database size automatically for some reason. How can I manually increase the database size to see if this corrects the problem (and set it up to automatically increase the database size in the future)?

Reply to
CptSoft

Update: My worst nightmare has been averted.

After upgrading to SQL Express I had a scare when the database would not open. After a reboot it opened normally. I am validating the data, but it seems to be fine so far.

However, 401's from all of my stores are still failing due to "Error 2147217900: Could not allocate space for object 'HQEventLog' in database '4DHQ' because the 'PRIMARY' filegroup is full."

I suspect that this is occuring because SQLExpress is not increasing the database size automatically for some reason. How can I manually increase the database size to see if this corrects the problem (and set it up to automatically increase the database size in the future)?

Reply to
Jason

Update: My worst nightmare has been averted.

After upgrading to SQL Express I had a scare when the database would not open. After a reboot it opened normally. I am validating the data, but it seems to be fine so far.

However, 401's from all of my stores are still failing due to "Error 2147217900: Could not allocate space for object 'HQEventLog' in database '4DHQ' because the 'PRIMARY' filegroup is full."

I suspect that this is occuring because SQLExpress is not increasing the database size automatically for some reason. How can I manually increase the database size to see if this corrects the problem (and set it up to automatically increase the database size in the future)?

Reply to
Jason

Update: My worst nightmare has been averted.

After upgrading to SQL Express I had a scare when the database would not open. After a reboot it opened normally. I am validating the data, but it seems to be fine so far.

However, 401's from all of my stores are still failing due to "Error 2147217900: Could not allocate space for object 'HQEventLog' in database '4DHQ' because the 'PRIMARY' filegroup is full."

I suspect that this is occuring because SQLExpress is not increasing the database size automatically for some reason. How can I manually increase the database size to see if this corrects the problem (and set it up to automatically increase the database size in the future)?

Reply to
CptSoft

Update: My worst nightmare has been averted.

After upgrading to SQL Express I had a scare when the database would not open. After a reboot it opened normally. I am validating the data, but it seems to be fine so far.

However, 401's from all of my stores are still failing due to "Error 2147217900: Could not allocate space for object 'HQEventLog' in database '4DHQ' because the 'PRIMARY' filegroup is full."

I suspect that this is occuring because SQLExpress is not increasing the database size automatically for some reason. How can I manually increase the database size to see if this corrects the problem (and set it up to automatically increase the database size in the future)?

Reply to
CptSoft

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.