Autogrowth 32000 percent

I have a database with a 3G datafile, and 1G logfile. I have set the
Autogrowth on the datafile to 250M, for the third time. Somehow, I don't know
when, the Autogrowth is getting changed to [32000 percent]. So when the
datafile tries to expand it take a considerable amount of disk space (106G),
then my log dumps start failing due to low disk space.
Autogrowth=32000%
Has anyone seen this before?
Thanks in advance,
KenL wrote:
> I have a database with a 3G datafile, and 1G logfile. I have set the
> Autogrowth on the datafile to 250M, for the third time. Somehow, I don't know
> when, the Autogrowth is getting changed to [32000 percent]. So when the
> datafile tries to expand it take a considerable amount of disk space (106G),
> then my log dumps start failing due to low disk space.
> Autogrowth=32000%
> Has anyone seen this before?
> Thanks in advance,
You don't say, but I'm assuming this is on SQL 2005? This is a known
bug:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Tracy, thanks very much for the response. The feedback referenced below is
talking about SQL 2000, and says it will be fixed in the next release of SQL
Server. I am using SQL 2005, so isn't that the next release? I do not see a
resolution?
Thanks,
"Tracy McKibben" wrote:

> KenL wrote:
> You don't say, but I'm assuming this is on SQL 2005? This is a known
> bug:
> http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
|||KenL wrote:
> Tracy, thanks very much for the response. The feedback referenced below is
> talking about SQL 2000, and says it will be fixed in the next release of SQL
> Server. I am using SQL 2005, so isn't that the next release? I do not see a
> resolution?
No, this is definately a SQL 2005 bug... The article that I linked to
talks about one possible cause of this as being a status bit in a
converted SQL 2000 database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Tracy, again thanks for the response.
The database is in SQL 2005, and was upgraded from a SQL 7 to SQL 2000, and
then SQL 2005. So are your saying this is a known bug that there currently is
no fix or workaround?
Thanks,
Ken
"Tracy McKibben" wrote:

> KenL wrote:
> No, this is definately a SQL 2005 bug... The article that I linked to
> talks about one possible cause of this as being a status bit in a
> converted SQL 2000 database.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>

Autogrowth 32000 percent

I have a database with a 3G datafile, and 1G logfile. I have set the
Autogrowth on the datafile to 250M, for the third time. Somehow, I don't kno
w
when, the Autogrowth is getting changed to [32000 percent]. So when the
datafile tries to expand it take a considerable amount of disk space (106G),
then my log dumps start failing due to low disk space.
Autogrowth=32000%
Has anyone seen this before?
Thanks in advance,KenL wrote:
> I have a database with a 3G datafile, and 1G logfile. I have set the
> Autogrowth on the datafile to 250M, for the third time. Somehow, I don't k
now
> when, the Autogrowth is getting changed to [32000 percent]. So when th
e
> datafile tries to expand it take a considerable amount of disk space (106G
),
> then my log dumps start failing due to low disk space.
> Autogrowth=32000%
> Has anyone seen this before?
> Thanks in advance,
You don't say, but I'm assuming this is on SQL 2005? This is a known
bug:
http://connect.microsoft.com/SQLSer...=12717
7
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy, thanks very much for the response. The feedback referenced below is
talking about SQL 2000, and says it will be fixed in the next release of SQL
Server. I am using SQL 2005, so isn't that the next release? I do not see a
resolution?
Thanks,
"Tracy McKibben" wrote:

> KenL wrote:
> You don't say, but I'm assuming this is on SQL 2005? This is a known
> bug:
> http://connect.microsoft.com/SQLSer...=127
177
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||KenL wrote:
> Tracy, thanks very much for the response. The feedback referenced below is
> talking about SQL 2000, and says it will be fixed in the next release of S
QL
> Server. I am using SQL 2005, so isn't that the next release? I do not see
a
> resolution?
No, this is definately a SQL 2005 bug... The article that I linked to
talks about one possible cause of this as being a status bit in a
converted SQL 2000 database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy, again thanks for the response.
The database is in SQL 2005, and was upgraded from a SQL 7 to SQL 2000, and
then SQL 2005. So are your saying this is a known bug that there currently i
s
no fix or workaround?
Thanks,
Ken
"Tracy McKibben" wrote:

> KenL wrote:
> No, this is definately a SQL 2005 bug... The article that I linked to
> talks about one possible cause of this as being a status bit in a
> converted SQL 2000 database.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>

Autogrowth 32000 percent

I have a database with a 3G datafile, and 1G logfile. I have set the
Autogrowth on the datafile to 250M, for the third time. Somehow, I don't know
when, the Autogrowth is getting changed to [32000 percent]. So when the
datafile tries to expand it take a considerable amount of disk space (106G),
then my log dumps start failing due to low disk space.
Autogrowth=32000%
Has anyone seen this before?
Thanks in advance,KenL wrote:
> I have a database with a 3G datafile, and 1G logfile. I have set the
> Autogrowth on the datafile to 250M, for the third time. Somehow, I don't know
> when, the Autogrowth is getting changed to [32000 percent]. So when the
> datafile tries to expand it take a considerable amount of disk space (106G),
> then my log dumps start failing due to low disk space.
> Autogrowth=32000%
> Has anyone seen this before?
> Thanks in advance,
You don't say, but I'm assuming this is on SQL 2005? This is a known
bug:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy, thanks very much for the response. The feedback referenced below is
talking about SQL 2000, and says it will be fixed in the next release of SQL
Server. I am using SQL 2005, so isn't that the next release? I do not see a
resolution?
Thanks,
"Tracy McKibben" wrote:
> KenL wrote:
> > I have a database with a 3G datafile, and 1G logfile. I have set the
> > Autogrowth on the datafile to 250M, for the third time. Somehow, I don't know
> > when, the Autogrowth is getting changed to [32000 percent]. So when the
> > datafile tries to expand it take a considerable amount of disk space (106G),
> > then my log dumps start failing due to low disk space.
> >
> > Autogrowth=32000%
> > Has anyone seen this before?
> >
> > Thanks in advance,
> You don't say, but I'm assuming this is on SQL 2005? This is a known
> bug:
> http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||KenL wrote:
> Tracy, thanks very much for the response. The feedback referenced below is
> talking about SQL 2000, and says it will be fixed in the next release of SQL
> Server. I am using SQL 2005, so isn't that the next release? I do not see a
> resolution?
No, this is definately a SQL 2005 bug... The article that I linked to
talks about one possible cause of this as being a status bit in a
converted SQL 2000 database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy, again thanks for the response.
The database is in SQL 2005, and was upgraded from a SQL 7 to SQL 2000, and
then SQL 2005. So are your saying this is a known bug that there currently is
no fix or workaround?
Thanks,
Ken
"Tracy McKibben" wrote:
> KenL wrote:
> > Tracy, thanks very much for the response. The feedback referenced below is
> > talking about SQL 2000, and says it will be fixed in the next release of SQL
> > Server. I am using SQL 2005, so isn't that the next release? I do not see a
> > resolution?
> No, this is definately a SQL 2005 bug... The article that I linked to
> talks about one possible cause of this as being a status bit in a
> converted SQL 2000 database.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>

Auto-Generate MDX Query from Cube OWC Settings?

Can I somehow auto-generate an MDX query based on current settings in the AS OWC cube browser? Why? If so, I will want to use the AS OWC cube browser to filter the data down to < 66K rows, then auto-generate an MDX query from the current browsed settings, copy and paste the MDX script into MS Excel's OLAP query, and use it. I'm trying to avoid the 66K row limitation in Excel 2002.

If this is innappropriate, is there another way, besides raw MDX hand-coding, to accomplish the same thing?

You can start a trace using the SQL Server Profiler, and see the MDX query created by OWC. Then use that query in Excel?

Chris.

Auto starting the sqlserver service

Hello all,
I am by no means a SLQ admin/DBA I am the Layer2/3 network admin who somehow
got thrown into figuring out how to fix an issue on one of our production
servers. We have a machine that is regularly rebooted (this is a whole
'nother story) and at times when it comes back on it does not start the
sqlserver service.
I was wondering if anyone knew how to right a batch file that would
regularly check, say every 15min, to see if the service was running, and if
not to star it.
Any help or even a nudge in the right direction would be ever so appreciated.go to start-->run-->services.msc-->look for MSSQLSERVER and double
click on that-->change the startup type to Automatic...|||It has been verified to be set at automatic. For some reason the
sqlserveragent does not start at bootup on occasion. If we go into the
services panel and right click "start" the service will come up fine. But
unfortunatly we do not know until the end user complains.
We are currently implementing MOM which may help us monitor when the service
is not running.
"Shadow" wrote:
> go to start-->run-->services.msc-->look for MSSQLSERVER and double
> click on that-->change the startup type to Automatic...
>|||Use this to check the sqlagent status:
exec xp_servicecontrol 'querystate', 'sqlserveragent'
If it returns "stopped" then start the service by:
exec master..xp_servicecontrol N'start', N'sqlserveragent'
"FranklinST_Admin" <FranklinSTAdmin@.discussions.microsoft.com> wrote in
message news:F6293761-0C54-4BB4-B6CD-390A8C27C584@.microsoft.com...
> Hello all,
> I am by no means a SLQ admin/DBA I am the Layer2/3 network admin who
> somehow
> got thrown into figuring out how to fix an issue on one of our production
> servers. We have a machine that is regularly rebooted (this is a whole
> 'nother story) and at times when it comes back on it does not start the
> sqlserver service.
> I was wondering if anyone knew how to right a batch file that would
> regularly check, say every 15min, to see if the service was running, and
> if
> not to star it.
> Any help or even a nudge in the right direction would be ever so
> appreciated.

Auto Number or Identity Seed on Oracle Database

Need help on the Auto Number or Identity Seed on the Oracle Database

I got an Access database that need to be converted to Oracle 9i.
Somehow the Trigger we created to simulate the "AUTO NUMBER" on Access
could not create the sequence number as soon as the value has been
inserted. The sequence number can only be created after we go to the
second line. Please see the trigger below.

Is there anyway we could create a trigger that could create the
sequence number as soon as we enter a value? It should be very
similar to the "Auto Number" on Access, or "Identity Seed" on SQL
Server.

------------------
1. sequence SNP.SECTION_ID_SQ:

CREATE SEQUENCE SNP.SECTION_ID_SQ
START WITH 1
INCREMENT BY 1
NOMINVALUE
NOMAXVALUE
NOCYCLE
CACHE 20
NOORDER
/
GRANT SELECT ON SNP.SECTION_ID_SQ TO "PUBLIC"
/

2. Trigger SNP.SNP001_T_I_GET_NEXT_SECTION_ID:

CREATE OR REPLACE TRIGGER SNP.SNP001_T_I_GET_NEXT_SECTION_ID
BEFORE INSERT
ON SNP.SNP001_SECTION
REFERENCING OLD AS OLD NEW AS NEW
FOR EACH ROW WHEN (new.section_id IS NULL)
BEGIN
SELECT section_id_sq.nextval
INTO :new.section_id
FROM dual;
END;Ken wrote:
[snip]

Already answered in c.d.m.a and a shedload of oracle groups, why are you
asking an Access/Oracle question in a SQL Server group? You're going to
annoy Celko in a minute <g
--
This sig left intentionally blank