Wednesday, March 28, 2012
Opening up SQL 2005 Management studio generates Winmgmt error
when I connect to a clustered SQL 2005 server using SQL Management Studio.
Has anyone ever encountered this and does anyone know how to stop this?
Event filter with query "select * from __InstanceModificationEvent within 10
where TargetInstance isa 'Win32_Service'" could not be (re)activated in
namespace "//./root/Microsoft/SqlServer/ComputerManagement" because of error
0x80041010. Events may not be delivered through this filter until the
problem is corrected.
ThanksI have the same error. It appears mmc cannot connect to wmi class.
"Steven" wrote:
> I have been getting the following winmgmt error in my application event log
> when I connect to a clustered SQL 2005 server using SQL Management Studio.
> Has anyone ever encountered this and does anyone know how to stop this?
> Event filter with query "select * from __InstanceModificationEvent within 10
> where TargetInstance isa 'Win32_Service'" could not be (re)activated in
> namespace "//./root/Microsoft/SqlServer/ComputerManagement" because of error
> 0x80041010. Events may not be delivered through this filter until the
> problem is corrected.
> Thanks
>
>
>
>
>sql
Opening up SQL 2005 Management studio generates Winmgmt erro
when I connect to a clustered SQL 2005 server using SQL Management Studio.
Has anyone ever encountered this and does anyone know how to stop this?
Event filter with query "select * from __InstanceModificationEvent within 10
where TargetInstance isa 'Win32_Service'" could not be (re)activated in
namespace "//./root/Microsoft/SqlServer/ComputerManagement" because of error
0x80041010. Events may not be delivered through this filter until the
problem is corrected.
ThanksI have the same problem any help would be appreciated :D
|||
We get the same "select *" error message and found that it was probably resulting from a unisys sentinel script; practically the exact verbage could be found in several such .vbs scripts. Certainly some event is triggered and the sentinel software attempts to run one of the scripts and fails. The failure may be due to the sentinel software trying to perform a sql2000 task on a sql2005 server. We're still hunting for an exact cause though.
I hope that this points you in the right direction for your particular case.
Opening up SQL 2005 Management studio generates Winmgmt erro
when I connect to a clustered SQL 2005 server using SQL Management Studio.
Has anyone ever encountered this and does anyone know how to stop this?
Event filter with query "select * from __InstanceModificationEvent within 10
where TargetInstance isa 'Win32_Service'" could not be (re)activated in
namespace "//./root/Microsoft/SqlServer/ComputerManagement" because of error
0x80041010. Events may not be delivered through this filter until the
problem is corrected.
ThanksI have the same problem any help would be appreciated :D|||
We get the same "select *" error message and found that it was probably resulting from a unisys sentinel script; practically the exact verbage could be found in several such .vbs scripts. Certainly some event is triggered and the sentinel software attempts to run one of the scripts and fails. The failure may be due to the sentinel software trying to perform a sql2000 task on a sql2005 server. We're still hunting for an exact cause though.
I hope that this points you in the right direction for your particular case.
Wednesday, March 21, 2012
Open transactions
transactions?
For example: You have a 10 MB transaction log that is 50% full ( DBCC
sqlperf(logspace) ) and you backup the log. After the log backup you see it
is 25% full. Therefore, 25% of the transaction log held open transactions.
How can I tell there this before I back the log up?I am not sure how you can tell without looking at each entry in the log and
calculating this all. But I don't agree with your assumption based on your
example. Just because it freed up 25% space does not mean that there was
25% open transactions. A single open transaction in the wrong place can
prevent the log from being truncated and the space reused. That has no
correlation to how many open transactions there were.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Jay" <nospan@.nospam.org> wrote in message
news:O4juyqKHIHA.1184@.TK2MSFTNGP04.phx.gbl...
> Is there a way to tell how much of a transaction log file has open
> transactions?
>
> For example: You have a 10 MB transaction log that is 50% full ( DBCC
> sqlperf(logspace) ) and you backup the log. After the log backup you see
> it is 25% full. Therefore, 25% of the transaction log held open
> transactions.
> How can I tell there this before I back the log up?
>|||On Thu, 1 Nov 2007 10:14:43 -0700, "Jay" <nospan@.nospam.org> wrote:
>Is there a way to tell how much of a transaction log file has open
>transactions?
>
>For example: You have a 10 MB transaction log that is 50% full ( DBCC
>sqlperf(logspace) ) and you backup the log. After the log backup you see it
>is 25% full. Therefore, 25% of the transaction log held open transactions.
>How can I tell there this before I back the log up?
Besides the points that Andrew covered, there is also the matter of
Virtual Log Files. You can read up on them in the Books on Line (BOL)
but essentially it is a unit of space within the log file. Information
on space in the log is, if I have things right, in multiples of the
VLF, so 25% full could simply mean there are 4 VLFs and only one is in
use - but it might be far from full.
Roy Harvey
Beacon Falls, CT|||> A single open transaction in the wrong place can prevent the log from
> being truncated and the space reused.
OK, this is confusing. I'm not talking about shrinking the log file (where I
would understand this), I'm talking about marking transactions as backed up
so the the space in the .ldf can be reused.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:ebpe%230LHIHA.5544@.TK2MSFTNGP02.phx.gbl...
>I am not sure how you can tell without looking at each entry in the log and
>calculating this all. But I don't agree with your assumption based on your
>example. Just because it freed up 25% space does not mean that there was
>25% open transactions. A single open transaction in the wrong place can
>prevent the log from being truncated and the space reused. That has no
>correlation to how many open transactions there were.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Jay" <nospan@.nospam.org> wrote in message
> news:O4juyqKHIHA.1184@.TK2MSFTNGP04.phx.gbl...
>> Is there a way to tell how much of a transaction log file has open
>> transactions?
>>
>> For example: You have a 10 MB transaction log that is 50% full ( DBCC
>> sqlperf(logspace) ) and you backup the log. After the log backup you see
>> it is 25% full. Therefore, 25% of the transaction log held open
>> transactions.
>> How can I tell there this before I back the log up?
>|||Are you saying that DBCC sqlperf(logspace) reports a number that corasponds
to the VLF's and not to the actual space used? If so, that would explain a
couple other things, like how the really small .ldf files constantly have
such a large % used, when nothing is going on in that DB.
"Roy Harvey (SQL Server MVP)" <roy_harvey@.snet.net> wrote in message
news:ehcki31hv9q36sd8n9q7vs52c7ktflikri@.4ax.com...
> On Thu, 1 Nov 2007 10:14:43 -0700, "Jay" <nospan@.nospam.org> wrote:
>>Is there a way to tell how much of a transaction log file has open
>>transactions?
>>
>>For example: You have a 10 MB transaction log that is 50% full ( DBCC
>>sqlperf(logspace) ) and you backup the log. After the log backup you see
>>it
>>is 25% full. Therefore, 25% of the transaction log held open transactions.
>>How can I tell there this before I back the log up?
> Besides the points that Andrew covered, there is also the matter of
> Virtual Log Files. You can read up on them in the Books on Line (BOL)
> but essentially it is a unit of space within the log file. Information
> on space in the log is, if I have things right, in multiples of the
> VLF, so 25% full could simply mean there are 4 VLFs and only one is in
> use - but it might be far from full.
> Roy Harvey
> Beacon Falls, CT|||On Thu, 1 Nov 2007 14:21:00 -0700, "Jay" <nospan@.nospam.org> wrote:
>Are you saying that DBCC sqlperf(logspace) reports a number that corasponds
>to the VLF's and not to the actual space used? If so, that would explain a
>couple other things, like how the really small .ldf files constantly have
>such a large % used, when nothing is going on in that DB.
That is my understanding, or misunderstanding as the case may be.
Roy Harvey
Beacon Falls, CT|||With a DB that is NOT in SIMPLE mode a VLF can only be truncated and reused
when there are no Open Trans and it has been check pointed and backed up.
If there is a single open tran in a VLF with 1000 committed trans the VLF
can not be reused. If you have 4 VLF's and 2 VLF's are in use the results of
DBCC SQLPERF(Logspace) will show it as being 50% used or empty which ever
way you want to look at it. But that does not mean you had 50% uncommitted
transactions. You only need 2, one in each VLF to make it appear that way.
So in your example:
>> For example: You have a 10 MB transaction log that is 50% full ( DBCC
>> sqlperf(logspace) ) and you backup the log. After the log backup you see
>> it is 25% full. Therefore, 25% of the transaction log held open
>> transactions.
you imply that 25% of the log was uncommitted transactions. It may have only
been a fraction of a % of actual uncommitted transactions. If all you care
about is usable space then fine state it as how much space is usable at that
point in time or not. Your question of:
>> Is there a way to tell how much of a transaction log file has open
>> transactions?
is not that simple based on usable space. You would have to use something
like fn_dblog() (google for more details) to identify each LSN to see what
state it was in. This is just not practical. I went thru this exercise not
to be picky about wording but to ensure you understand how VLF's affect the
log in hits way.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Jay" <nospan@.nospam.org> wrote in message
news:%238PZLyMHIHA.2328@.TK2MSFTNGP03.phx.gbl...
>> A single open transaction in the wrong place can prevent the log from
>> being truncated and the space reused.
> OK, this is confusing. I'm not talking about shrinking the log file (where
> I would understand this), I'm talking about marking transactions as backed
> up so the the space in the .ldf can be reused.
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:ebpe%230LHIHA.5544@.TK2MSFTNGP02.phx.gbl...
>>I am not sure how you can tell without looking at each entry in the log
>>and calculating this all. But I don't agree with your assumption based on
>>your example. Just because it freed up 25% space does not mean that there
>>was 25% open transactions. A single open transaction in the wrong place
>>can prevent the log from being truncated and the space reused. That has no
>>correlation to how many open transactions there were.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "Jay" <nospan@.nospam.org> wrote in message
>> news:O4juyqKHIHA.1184@.TK2MSFTNGP04.phx.gbl...
>> Is there a way to tell how much of a transaction log file has open
>> transactions?
>>
>> For example: You have a 10 MB transaction log that is 50% full ( DBCC
>> sqlperf(logspace) ) and you backup the log. After the log backup you see
>> it is 25% full. Therefore, 25% of the transaction log held open
>> transactions.
>> How can I tell there this before I back the log up?
>>
>sql
Monday, March 12, 2012
Open and read the log file
verify ones definitive inserts that they had been made in the database. How
I can make this?
--
Nuno PereiraSee if this helps:
Log Explorer for SQL Server
http://www.lumigent.com/products/le_sql.html
AMB
"Nuno Pereira" wrote:
> I need to open the log file of a database to see the commands in it kept t
o
> verify ones definitive inserts that they had been made in the database. H
ow
> I can make this?
> --
> Nuno Pereira|||There's a 3rd party utility from www.lumigent.com
Other than that, you're out of luck.
"Nuno Pereira" <NunoPereira@.discussions.microsoft.com> wrote in message
news:E3D67B03-7911-47B2-8209-016CC23BA074@.microsoft.com...
> I need to open the log file of a database to see the commands in it kept
to
> verify ones definitive inserts that they had been made in the database.
How
> I can make this?
> --
> Nuno Pereira
Friday, March 9, 2012
Open a TEXTE file with SQL server (stored procedure)
I would like to open a *.log file (TEXTE format) from un stored
procedure SQL SERVER. After that, i just want to read each lines and
insert each line in a sql server table.
With that, i'll could schedule this stored procedure in the jobs of
sql server
Thant a lot for your help.
Alex.Have a look at BULK INSERT in BOL
--
HTH
Ryan Waight, MCDBA, MCSE
"alexfayard" <alexfayard@.hotmail.com> wrote in message
news:e3ed656a.0309170523.3b897e91@.posting.google.com...
> Hi,
> I would like to open a *.log file (TEXTE format) from un stored
> procedure SQL SERVER. After that, i just want to read each lines and
> insert each line in a sql server table.
> With that, i'll could schedule this stored procedure in the jobs of
> sql server
> Thant a lot for your help.
> Alex.
OnVariableChangedEvent Log Message
I have posted a very simple request to have the message in the SSIS log from an OnVariableValueChanged Event to include the vale the variable has been set to.
If you like the idea of this enhancement please go and vote and validate it here
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=238803
Phil,
What does it have in there currently?
-Jamie
|||Just the name of the variable that changed
Saturday, February 25, 2012
Only administrators can connect
denying connections. The errors in the sql log say "login failed for
<user>. only administrators may connect at this time". I've been unable to
find any documentation on the net for what exactly this is and I can't seem
to figure out what's causing it. Any suggestions?Did you by any chance start the server with -m? If so, remove -m will allow
non administrator to connect.
--
Gang He
SQL Server Storage Engine Development
This posting is provided "AS IS" with no warranties, and confers no rights.
"Brent Mills" <*bcm*@.hotmail.com> wrote in message
news:u7MycX#$DHA.1224@.TK2MSFTNGP11.phx.gbl...
> We have been having a problem recently where all of a sudden sql starts
> denying connections. The errors in the sql log say "login failed for
> <user>. only administrators may connect at this time". I've been unable
to
> find any documentation on the net for what exactly this is and I can't
seem
> to figure out what's causing it. Any suggestions?
>|||No, that's the weird thing. It works fine for about a week or two and then
all of a sudden it just starts denying connections.
"Gang He [MSFT]" <ganghe@.online.microsoft.com> wrote in message
news:OPZBCl$$DHA.1452@.TK2MSFTNGP09.phx.gbl...
> Did you by any chance start the server with -m? If so, remove -m will
allow
> non administrator to connect.
> --
> Gang He
> SQL Server Storage Engine Development
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Brent Mills" <*bcm*@.hotmail.com> wrote in message
> news:u7MycX#$DHA.1224@.TK2MSFTNGP11.phx.gbl...
> > We have been having a problem recently where all of a sudden sql starts
> > denying connections. The errors in the sql log say "login failed for
> > <user>. only administrators may connect at this time". I've been
unable
> to
> > find any documentation on the net for what exactly this is and I can't
> seem
> > to figure out what's causing it. Any suggestions?
> >
> >
>
Only administrators can connect
denying connections. The errors in the sql log say "login failed for
<user>. only administrators may connect at this time". I've been unable to
find any documentation on the net for what exactly this is and I can't seem
to figure out what's causing it. Any suggestions?Did you by any chance start the server with -m? If so, remove -m will allow
non administrator to connect.
Gang He
SQL Server Storage Engine Development
This posting is provided "AS IS" with no warranties, and confers no rights.
"Brent Mills" <*bcm*@.hotmail.com> wrote in message
news:u7MycX#$DHA.1224@.TK2MSFTNGP11.phx.gbl...
> We have been having a problem recently where all of a sudden sql starts
> denying connections. The errors in the sql log say "login failed for
> <user>. only administrators may connect at this time". I've been unable
to
> find any documentation on the net for what exactly this is and I can't
seem
> to figure out what's causing it. Any suggestions?
>|||No, that's the weird thing. It works fine for about a week or two and then
all of a sudden it just starts denying connections.
"Gang He [MSFT]" <ganghe@.online.microsoft.com> wrote in message
news:OPZBCl$$DHA.1452@.TK2MSFTNGP09.phx.gbl...
> Did you by any chance start the server with -m? If so, remove -m will
allow
> non administrator to connect.
> --
> Gang He
> SQL Server Storage Engine Development
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Brent Mills" <*bcm*@.hotmail.com> wrote in message
> news:u7MycX#$DHA.1224@.TK2MSFTNGP11.phx.gbl...
unable
> to
> seem
>