[help] installation problems with sql server express 2005

hello everybody
I've downloaded a free version of ms sql server express 2005
and while I lauch the install file, I Have a bug :
Something like :
"you don't have write and read permission" - conctact administator
but i'm logged on a administator session

if anyone can help me ..
thnx in advance ..
hzben

Hi,

Ensure you have Read & Write permission on the folder/drive you are trying to install SQL Server , i.e. Program Files folder!!! www.windowsecurity.com/articles/Understanding-Windows-NTFS-Permissions.html FYI.

Hemantgiri S. Goswami

|||thank you for this reply
Do i can export a sql 2000 database to sql 2005 express only with a .sql file or do i need the .mdf and .ldf files of my old database ?
I need to export only the structure (tables ,columns and triggers) of my database to sql express 2005 .
have a nice day !!
hzben|||

Hi hzben,

you can export the structure of your database with your .sql file (Script of Database Objects) and for that you don't need .mdf/.ldf files. But in case you wants to attach your database to sql server you require .mdf and .ldf.

HTH

Hemantgiri S. Goswami

[Bug] Jump to report from a Table (second page on HTML)

This seems like a bug:
I created a "jump to report" action on a TABLE in my report.
It works fine. But - when the table becomes long, and exceeds one
page on the HTML viewer, the "Jump to report" doesn't work anymore.
It keep throwing up blank pages.
Has anyone else encountered this?One question, is this from the IDE or from a deployed report. I have had a
variety of funky oddities that are only in the IDE, the deployed report
works fine.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Harsh" <harsh.vb@.gmail.com> wrote in message
news:1e70ecdd.0411130717.8685260@.posting.google.com...
> This seems like a bug:
> I created a "jump to report" action on a TABLE in my report.
> It works fine. But - when the table becomes long, and exceeds one
> page on the HTML viewer, the "Jump to report" doesn't work anymore.
> It keep throwing up blank pages.
> Has anyone else encountered this?

[Bug] Deadlock: Wait Type CXPACKET with CLUSTERED INDEXES

Our site has experienced a dead lock issue with a query that uses parallel
processing. Anyone know how to report this to Microsoft?
When running a load for one of our datamarts we have a query that uses 12
threads of execution, we have several queries like this but only 1 which
locks up. Half way to 3/4 of the way through execution many of threads stop
and are waiting with a type CXPACKET, CPU utilizations grinds to halt and the
query never returns. It ran this entire weekend, Friday 11:30 PM to Monday
9:00 AM.
Our workaround, believe it or not, was to change the primary key's on a
couple lookup tables from CLUSTERED to NON-CLUSTERED. This fixed the problem
and still allows us to use parallel execution and we did not have to resort
to OPTION (MAXDOP 1)
There is clearly some kind of bug with SQL Server and the creation and
execution of the query plan. How do I get a solid core dump and log of the
server and submit a bug report to MS so they can fix this.
AdamAdam,
If you are up-to-date on service packs and not just encountering
http://support.microsoft.com/kb/293232/, the best way to report this is
probably to open a case with Microsoft Product Support (PSS). This
doesn't sound like the kind of problem that can easily be distilled down
to a reproducible Query Analyzer script.
If the problem is caused by a bug, there's a good chance the support
incident will be free, but whether or not there will be a fix in the
short term is hard to say. But changing indexes to nonclustered isn't a
very convenient workaround, and PSS might be able to find a better
workaround. There are occasional newsgroup reports of this situation,
and you can browse recent threads here to see if there is a better
workaround:
http://groups-beta.google.com/groups?q=CXPACKET+sqlserver&start=0&scoring=d&hl=en&
Steve Kass
Drew University
Adam wrote:
>Our site has experienced a dead lock issue with a query that uses parallel
>processing. Anyone know how to report this to Microsoft?
>When running a load for one of our datamarts we have a query that uses 12
>threads of execution, we have several queries like this but only 1 which
>locks up. Half way to 3/4 of the way through execution many of threads stop
>and are waiting with a type CXPACKET, CPU utilizations grinds to halt and the
>query never returns. It ran this entire weekend, Friday 11:30 PM to Monday
>9:00 AM.
>Our workaround, believe it or not, was to change the primary key's on a
>couple lookup tables from CLUSTERED to NON-CLUSTERED. This fixed the problem
>and still allows us to use parallel execution and we did not have to resort
>to OPTION (MAXDOP 1)
>There is clearly some kind of bug with SQL Server and the creation and
>execution of the query plan. How do I get a solid core dump and log of the
>server and submit a bug report to MS so they can fix this.
>Adam
>|||Thanks Steve, I will go the PSS route.
"Steve Kass" wrote:
> Adam,
> If you are up-to-date on service packs and not just encountering
> http://support.microsoft.com/kb/293232/, the best way to report this is
> probably to open a case with Microsoft Product Support (PSS). This
> doesn't sound like the kind of problem that can easily be distilled down
> to a reproducible Query Analyzer script.
> If the problem is caused by a bug, there's a good chance the support
> incident will be free, but whether or not there will be a fix in the
> short term is hard to say. But changing indexes to nonclustered isn't a
> very convenient workaround, and PSS might be able to find a better
> workaround. There are occasional newsgroup reports of this situation,
> and you can browse recent threads here to see if there is a better
> workaround:
> http://groups-beta.google.com/groups?q=CXPACKET+sqlserver&start=0&scoring=d&hl=en&
>
> Steve Kass
> Drew University
> Adam wrote:
> >Our site has experienced a dead lock issue with a query that uses parallel
> >processing. Anyone know how to report this to Microsoft?
> >
> >When running a load for one of our datamarts we have a query that uses 12
> >threads of execution, we have several queries like this but only 1 which
> >locks up. Half way to 3/4 of the way through execution many of threads stop
> >and are waiting with a type CXPACKET, CPU utilizations grinds to halt and the
> >query never returns. It ran this entire weekend, Friday 11:30 PM to Monday
> >9:00 AM.
> >
> >Our workaround, believe it or not, was to change the primary key's on a
> >couple lookup tables from CLUSTERED to NON-CLUSTERED. This fixed the problem
> >and still allows us to use parallel execution and we did not have to resort
> >to OPTION (MAXDOP 1)
> >
> >There is clearly some kind of bug with SQL Server and the creation and
> >execution of the query plan. How do I get a solid core dump and log of the
> >server and submit a bug report to MS so they can fix this.
> >
> >Adam
> >
> >
>|||On Mon, 20 Dec 2004 12:59:05 -0800, "Adam"
<Adam@.discussions.microsoft.com> wrote:
>Our workaround, believe it or not, was to change the primary key's on a
>couple lookup tables from CLUSTERED to NON-CLUSTERED. This fixed the problem
>and still allows us to use parallel execution and we did not have to resort
>to OPTION (MAXDOP 1)
I believe it.
You don't happen to use any little lock hints in your query, do you?
I recently had some queries hang up because the programmer had
helpfully specified tablockx, and this turned out to be
counterproductive.
J.

[Bug?] Where clause in SQLSERVER7 doesn't return results where it really should

Hi group,
I found the following behaviour really surprising:
[SQLServer 7]
consider following query:
SELECT L.logid, L.logdate, L.vragensetid, L.dooruserid, L.incidentid,
L.action, U.realname
FROM tbllog AS L LEFT OUTER JOIN tbluser AS U ON (L.dooruserid=U.userid)
WHERE((logdate >= '2006-02-08') AND (logdate <= '2006-02-08'))
ORDER BY logdate;
This query returns 0 results.
If I remove one part of the where-clause, it works just fine:
Like this
SELECT L.logid, L.logdate, L.vragensetid, L.dooruserid, L.incidentid,
L.action, U.realname
FROM tbllog AS L LEFT OUTER JOIN tbluser AS U ON (L.dooruserid=U.userid)
WHERE((logdate <= '2006-02-08'))
ORDER BY logdate;
or
SELECT L.logid, L.logdate, L.vragensetid, L.dooruserid, L.incidentid,
L.action, U.realname
FROM tbllog AS L LEFT OUTER JOIN tbluser AS U ON (L.dooruserid=U.userid)
WHERE((logdate >= '2006-02-08'))
ORDER BY logdate;
(These queries only differ in the >= or <= in the whereclause.)
Both queries return some rows!
(As expected by me because I know the table does have rows with logdate
'2006-02-08')
It seems that SQLServer is unable to find ANY records if I use both
whereclauses at the same time.
The reason this weird situation is needed is because I need to assemble the
query dynamically based on some form-info posted by a user.
Can anybody explain this?
Is this a known bug?
Or is maybe something going on that has to do with my (limmited)
understanding of SQLServer/SQL ?
I can of course code around this issue by checking in my script if the dates
are the same and in that case make only whereclause (logdate='2006-02-08'),
but I am curious what is going on.
Thanks for your time!
Regards,
Erwin Moller
Erwin Moller wrote:
Hi, I made the situation even simpler, and found the reason for my problem.
I removed the join, and left only 1 where-clause.
So the following query:
SELECT logid, logdate, vragensetid, dooruserid, incidentid, action
FROM tbllog
WHERE(logdate <= '2006-02-08') ORDER BY logdate;
Resulted in NO results.
Where the database contains records on this date.
Reason is: I am a simpleminded idiot.
I do not tell the database how many hours/minutes/seconds....
So while there are records on 2006-02-08, they are ALL after midnight.
:-)
Sorry for the noise!
Regards,
Erwin Moller

[Bug?] Where clause in SQLSERVER7 doesn't return results where it really should

Hi group,
I found the following behaviour really surprising:
[SQLServer 7]
consider following query:
SELECT L.logid, L.logdate, L.vragensetid, L.dooruserid, L.incidentid,
L.action, U.realname
FROM tbllog AS L LEFT OUTER JOIN tbluser AS U ON (L.dooruserid=U.userid)
WHERE((logdate >= '2006-02-08') AND (logdate <= '2006-02-08'))
ORDER BY logdate;
--
This query returns 0 results.
If I remove one part of the where-clause, it works just fine:
Like this
--
SELECT L.logid, L.logdate, L.vragensetid, L.dooruserid, L.incidentid,
L.action, U.realname
FROM tbllog AS L LEFT OUTER JOIN tbluser AS U ON (L.dooruserid=U.userid)
WHERE((logdate <= '2006-02-08'))
ORDER BY logdate;
--
or
SELECT L.logid, L.logdate, L.vragensetid, L.dooruserid, L.incidentid,
L.action, U.realname
FROM tbllog AS L LEFT OUTER JOIN tbluser AS U ON (L.dooruserid=U.userid)
WHERE((logdate >= '2006-02-08'))
ORDER BY logdate;
--
(These queries only differ in the >= or <= in the whereclause.)
Both queries return some rows!
(As expected by me because I know the table does have rows with logdate
'2006-02-08')
It seems that SQLServer is unable to find ANY records if I use both
whereclauses at the same time.
The reason this weird situation is needed is because I need to assemble the
query dynamically based on some form-info posted by a user.
Can anybody explain this?
Is this a known bug?
Or is maybe something going on that has to do with my (limmited)
understanding of SQLServer/SQL '
I can of course code around this issue by checking in my script if the dates
are the same and in that case make only whereclause (logdate='2006-02-08'),
but I am curious what is going on.
Thanks for your time!
Regards,
Erwin MollerErwin Moller wrote:
Hi, I made the situation even simpler, and found the reason for my problem.
I removed the join, and left only 1 where-clause.
So the following query:
SELECT logid, logdate, vragensetid, dooruserid, incidentid, action
FROM tbllog
WHERE(logdate <= '2006-02-08') ORDER BY logdate;
--
Resulted in NO results.
Where the database contains records on this date.
Reason is: I am a simpleminded idiot.
I do not tell the database how many hours/minutes/seconds....
So while there are records on 2006-02-08, they are ALL after midnight.
:-)
Sorry for the noise!
Regards,
Erwin Moller

[bug?] Hidden parameters

Hello,
I have troubles with hidden parameters. What am I doing:
1) define a report parameter based on a dataset's field (a dataset is
"Stored proc." type, the procedure returns the only string value -- if it is
important)
2) Build & deploy a solution, run the report from Report manager -- it's ok
3) run the report from Report manager, click on "Properties" tab, choose
"parameters":
Has Default - leave checked on
Default Value - (Query Based)
Null - (none)
Prompt User - leave checked on
Prompt String - I cleared this textbox
4) run the report again:
Reporting Services Error
Default value or value provided for the report parameter 'MyParam' is not a
valid value. (rsInvalidReportParameter) Get Online Help
Refresh button on RM or the IE's same button don't change this error message
5) Properties -> Parameters -> Prompt String: type a former prompt string
6) run the report: it works ok, however the aforementioned parameter acts
like it doesn't have Default Value anymore.
What have I do to hide param properly?
(MS RS sp1)
Microsoft SQL Server Reporting Services Version 8.00.878.00
Thanks,
Lucy.Does it have list of available values?
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lusy Crown" <evesq@.uk2.net> wrote in message
news:OBEtp5laEHA.3892@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I have troubles with hidden parameters. What am I doing:
> 1) define a report parameter based on a dataset's field (a dataset is
> "Stored proc." type, the procedure returns the only string value -- if it
> is
> important)
> 2) Build & deploy a solution, run the report from Report manager -- it's
> ok
> 3) run the report from Report manager, click on "Properties" tab, choose
> "parameters":
> Has Default - leave checked on
> Default Value - (Query Based)
> Null - (none)
> Prompt User - leave checked on
> Prompt String - I cleared this textbox
> 4) run the report again:
> Reporting Services Error
> Default value or value provided for the report parameter 'MyParam' is not
> a
> valid value. (rsInvalidReportParameter) Get Online Help
> Refresh button on RM or the IE's same button don't change this error
> message
> 5) Properties -> Parameters -> Prompt String: type a former prompt string
> 6) run the report: it works ok, however the aforementioned parameter acts
> like it doesn't have Default Value anymore.
> What have I do to hide param properly?
> (MS RS sp1)
> Microsoft SQL Server Reporting Services Version 8.00.878.00
> Thanks,
> Lucy.
>|||Yes. From query. Same to "default".
"Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
news:%2300zztpaEHA.3352@.TK2MSFTNGP12.phx.gbl...
> Does it have list of available values?
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Lusy Crown" <evesq@.uk2.net> wrote in message
> news:OBEtp5laEHA.3892@.TK2MSFTNGP10.phx.gbl...
> > Hello,
> >
> > I have troubles with hidden parameters. What am I doing:
> >
> > 1) define a report parameter based on a dataset's field (a dataset is
> > "Stored proc." type, the procedure returns the only string value -- if
it
> > is
> > important)
> > 2) Build & deploy a solution, run the report from Report manager -- it's
> > ok
> > 3) run the report from Report manager, click on "Properties" tab, choose
> > "parameters":
> > Has Default - leave checked on
> > Default Value - (Query Based)
> > Null - (none)
> > Prompt User - leave checked on
> > Prompt String - I cleared this textbox
> > 4) run the report again:
> >
> > Reporting Services Error
> > Default value or value provided for the report parameter 'MyParam' is
not
> > a
> > valid value. (rsInvalidReportParameter) Get Online Help
> >
> > Refresh button on RM or the IE's same button don't change this error
> > message
> >
> > 5) Properties -> Parameters -> Prompt String: type a former prompt
string
> > 6) run the report: it works ok, however the aforementioned parameter
acts
> > like it doesn't have Default Value anymore.
> >
> > What have I do to hide param properly?
> >
> > (MS RS sp1)
> > Microsoft SQL Server Reporting Services Version 8.00.878.00
> >
> > Thanks,
> > Lucy.
> >
> >
>|||To summarize, error rsInvalidReportParameter happened because same stored
procedure was used for available values and default value, and this stored
procedure returned unique result for every call.
Report Server was executing this stored procedure twice (1st time for
available values and 2nd time for default value) and was unable to match
default value with available value.
Solution is not to set available values.
Also because you just wanted to have read-only parameter, it is enough to
leave prompt blank, and Report Desinger would set parameter properties
during Deploy procedure.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lusy Crown" <evesq@.uk2.net> wrote in message
news:OAYt06paEHA.1764@.TK2MSFTNGP10.phx.gbl...
> Yes. From query. Same to "default".
>
> "Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
> news:%2300zztpaEHA.3352@.TK2MSFTNGP12.phx.gbl...
>> Does it have list of available values?
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>>
>> "Lusy Crown" <evesq@.uk2.net> wrote in message
>> news:OBEtp5laEHA.3892@.TK2MSFTNGP10.phx.gbl...
>> > Hello,
>> >
>> > I have troubles with hidden parameters. What am I doing:
>> >
>> > 1) define a report parameter based on a dataset's field (a dataset is
>> > "Stored proc." type, the procedure returns the only string value -- if
> it
>> > is
>> > important)
>> > 2) Build & deploy a solution, run the report from Report manager --
>> > it's
>> > ok
>> > 3) run the report from Report manager, click on "Properties" tab,
>> > choose
>> > "parameters":
>> > Has Default - leave checked on
>> > Default Value - (Query Based)
>> > Null - (none)
>> > Prompt User - leave checked on
>> > Prompt String - I cleared this textbox
>> > 4) run the report again:
>> >
>> > Reporting Services Error
>> > Default value or value provided for the report parameter 'MyParam' is
> not
>> > a
>> > valid value. (rsInvalidReportParameter) Get Online Help
>> >
>> > Refresh button on RM or the IE's same button don't change this error
>> > message
>> >
>> > 5) Properties -> Parameters -> Prompt String: type a former prompt
> string
>> > 6) run the report: it works ok, however the aforementioned parameter
> acts
>> > like it doesn't have Default Value anymore.
>> >
>> > What have I do to hide param properly?
>> >
>> > (MS RS sp1)
>> > Microsoft SQL Server Reporting Services Version 8.00.878.00
>> >
>> > Thanks,
>> > Lucy.
>> >
>> >
>>
>|||How do you not set available values...in report designer report params
dialog, my parameter has a name, 'tick', has the non-queried available values
radio button clicked and the list to the right is completely blank, as I want
it to be. This parameter is unique everytime a report is executed and cannot
be selected from a list of existing values...but I'm still getting the
following error when I call the web service render method...
+ System.SystemException {"The value provided for the report parameter
'tick' is not valid for its type. --> The value provided for the report
parameter 'tick' is not valid for its type. --> The value provided for the
report parameter 'tick' is not valid for its type."} System.SystemException
"Lev Semenets [MSFT]" wrote:
> To summarize, error rsInvalidReportParameter happened because same stored
> procedure was used for available values and default value, and this stored
> procedure returned unique result for every call.
> Report Server was executing this stored procedure twice (1st time for
> available values and 2nd time for default value) and was unable to match
> default value with available value.
> Solution is not to set available values.
> Also because you just wanted to have read-only parameter, it is enough to
> leave prompt blank, and Report Desinger would set parameter properties
> during Deploy procedure.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Lusy Crown" <evesq@.uk2.net> wrote in message
> news:OAYt06paEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > Yes. From query. Same to "default".
> >
> >
> > "Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
> > news:%2300zztpaEHA.3352@.TK2MSFTNGP12.phx.gbl...
> >> Does it have list of available values?
> >>
> >> --
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >>
> >>
> >> "Lusy Crown" <evesq@.uk2.net> wrote in message
> >> news:OBEtp5laEHA.3892@.TK2MSFTNGP10.phx.gbl...
> >> > Hello,
> >> >
> >> > I have troubles with hidden parameters. What am I doing:
> >> >
> >> > 1) define a report parameter based on a dataset's field (a dataset is
> >> > "Stored proc." type, the procedure returns the only string value -- if
> > it
> >> > is
> >> > important)
> >> > 2) Build & deploy a solution, run the report from Report manager --
> >> > it's
> >> > ok
> >> > 3) run the report from Report manager, click on "Properties" tab,
> >> > choose
> >> > "parameters":
> >> > Has Default - leave checked on
> >> > Default Value - (Query Based)
> >> > Null - (none)
> >> > Prompt User - leave checked on
> >> > Prompt String - I cleared this textbox
> >> > 4) run the report again:
> >> >
> >> > Reporting Services Error
> >> > Default value or value provided for the report parameter 'MyParam' is
> > not
> >> > a
> >> > valid value. (rsInvalidReportParameter) Get Online Help
> >> >
> >> > Refresh button on RM or the IE's same button don't change this error
> >> > message
> >> >
> >> > 5) Properties -> Parameters -> Prompt String: type a former prompt
> > string
> >> > 6) run the report: it works ok, however the aforementioned parameter
> > acts
> >> > like it doesn't have Default Value anymore.
> >> >
> >> > What have I do to hide param properly?
> >> >
> >> > (MS RS sp1)
> >> > Microsoft SQL Server Reporting Services Version 8.00.878.00
> >> >
> >> > Thanks,
> >> > Lucy.
> >> >
> >> >
> >>
> >>
> >
> >
>
>

@@IDLE Bug?

I have written a custom monitor, similar to sp_monitor that stores the
values of @.@.cpu_busy, @.@.io_busy, @.@.idle, etc... to a table.
I have observed that the value of @.@.idle prematurely wraps to a negative
number. Since this value is comprised of a 4 byte integer, one would expect
the value to wrap around to a negative value when it reaches 2,147,483,647.
However, my observations show that this value is wrapping at a value
somewhere just over 441150174 to a negative value somewhere just
under -95648727.
Does anyone have any insight as to why this system variable is prematurely
wrapping? What are the exact values that @.@.idle wraps at?Does anyone have insight into the SQL internals on how the @.@.idle value
rolls over?
"Don Ferguson" <don@.nospamplease> wrote in message
news:uyi0lQLhEHA.1724@.tk2msftngp13.phx.gbl...
> I have written a custom monitor, similar to sp_monitor that stores the
> values of @.@.cpu_busy, @.@.io_busy, @.@.idle, etc... to a table.
> I have observed that the value of @.@.idle prematurely wraps to a negative
> number. Since this value is comprised of a 4 byte integer, one would
expect
> the value to wrap around to a negative value when it reaches
2,147,483,647.
> However, my observations show that this value is wrapping at a value
> somewhere just over 441150174 to a negative value somewhere just
> under -95648727.
> Does anyone have any insight as to why this system variable is prematurely
> wrapping? What are the exact values that @.@.idle wraps at?
>

@@IDLE Bug?

I have written a custom monitor, similar to sp_monitor that stores the
values of @.@.cpu_busy, @.@.io_busy, @.@.idle, etc... to a table.
I have observed that the value of @.@.idle prematurely wraps to a negative
number. Since this value is comprised of a 4 byte integer, one would expect
the value to wrap around to a negative value when it reaches 2,147,483,647.
However, my observations show that this value is wrapping at a value
somewhere just over 441150174 to a negative value somewhere just
under -95648727.
Does anyone have any insight as to why this system variable is prematurely
wrapping? What are the exact values that @.@.idle wraps at?
Does anyone have insight into the SQL internals on how the @.@.idle value
rolls over?
"Don Ferguson" <don@.nospamplease> wrote in message
news:uyi0lQLhEHA.1724@.tk2msftngp13.phx.gbl...
> I have written a custom monitor, similar to sp_monitor that stores the
> values of @.@.cpu_busy, @.@.io_busy, @.@.idle, etc... to a table.
> I have observed that the value of @.@.idle prematurely wraps to a negative
> number. Since this value is comprised of a 4 byte integer, one would
expect
> the value to wrap around to a negative value when it reaches
2,147,483,647.
> However, my observations show that this value is wrapping at a value
> somewhere just over 441150174 to a negative value somewhere just
> under -95648727.
> Does anyone have any insight as to why this system variable is prematurely
> wrapping? What are the exact values that @.@.idle wraps at?
>

@@IDLE Bug?

I have written a custom monitor, similar to sp_monitor that stores the
values of @.@.cpu_busy, @.@.io_busy, @.@.idle, etc... to a table.
I have observed that the value of @.@.idle prematurely wraps to a negative
number. Since this value is comprised of a 4 byte integer, one would expect
the value to wrap around to a negative value when it reaches 2,147,483,647.
However, my observations show that this value is wrapping at a value
somewhere just over 441150174 to a negative value somewhere just
under -95648727.
Does anyone have any insight as to why this system variable is prematurely
wrapping? What are the exact values that @.@.idle wraps at?Does anyone have insight into the SQL internals on how the @.@.idle value
rolls over?
"Don Ferguson" <don@.nospamplease> wrote in message
news:uyi0lQLhEHA.1724@.tk2msftngp13.phx.gbl...
> I have written a custom monitor, similar to sp_monitor that stores the
> values of @.@.cpu_busy, @.@.io_busy, @.@.idle, etc... to a table.
> I have observed that the value of @.@.idle prematurely wraps to a negative
> number. Since this value is comprised of a 4 byte integer, one would
expect
> the value to wrap around to a negative value when it reaches
2,147,483,647.
> However, my observations show that this value is wrapping at a value
> somewhere just over 441150174 to a negative value somewhere just
> under -95648727.
> Does anyone have any insight as to why this system variable is prematurely
> wrapping? What are the exact values that @.@.idle wraps at?
>