Comments
Sort by recent activity
Hi Dylan,
that would be SQL Response checking the index fragmentation of your databases. I would expect that this might take more than 15 seconds to execute. / comments
Hi Dylan,
that would be SQL Response checking the index fragmentation of your databases. I would expect that this might take more than 15 seconds to execute.
Hi Dylan,
I take it from the forum thread that you are regularly seeing two types of long running queries that are coming from SQL Response
One relating to xp_readerrorlog - this has now been resolved by truncating the error log
One relating to DBCC TRACESTATUS - which is still occuring
I've had a look at the 2nd query and don't see anything that should be taking a long time to execute.
Could you run the following SQL Queries on the problem server and let me know how log each one takes to execute DBCC TRACESTATUS(1204) WITH NO_INFOMSGS
CREATE TABLE #dbccstat
(
TraceFlag INT,
Status INT,
)
INSERT INTO #dbccstat EXEC('DBCC TRACESTATUS(1204) WITH NO_INFOMSGS')
DECLARE @status INT
SELECT @status = Status FROM #dbccstat
IF @status = 0
BEGIN
DBCC TRACEON( 1204, -1 ) WITH NO_INFOMSGS;
END
DROP TABLE #dbccstat
Cheers / comments
Hi Dylan,
I take it from the forum thread that you are regularly seeing two types of long running queries that are coming from SQL Response
One relating to xp_readerrorlog - this has now been resol...
Hi Carolyn,
I'm very sorry to hear about the issues you've been having with SQL Response. We haven't come across anything like this before.
Do you have any details of the error that happened?
I'm going to email you a diagnostic sql script. I'd be very grateful if you could run it and send me back the results.
Cheers,
--
Daniel / comments
Hi Carolyn,
I'm very sorry to hear about the issues you've been having with SQL Response. We haven't come across anything like this before.
Do you have any details of the error that happened?
I'm g...
Hi Ztuner,
I'm sorry for the confusion, Brian's post (Posted: Mon Mar 16, 2009 3:11 pm) was a bit of a simplification, and doesn't reflect the full functionality of SQL Response.
The answer to your question is yes, you can connect from Response Repository (DOMAIN1) to SQLSERVER2 (DOMAIN2) using operating DOMAIN2\sql_demo domain windows login account to monitor system part of the server without trust links between domains.
Cheers,
--
Daniel / comments
Hi Ztuner,
I'm sorry for the confusion, Brian's post (Posted: Mon Mar 16, 2009 3:11 pm) was a bit of a simplification, and doesn't reflect the full functionality of SQL Response.
The answer to your...
Hi,
It isn't possible to disable the windows server information monitoring.
If you are running the Alert Repository on Windows Server 2003 or later, you should be able to specify the windows account to be used in the server properties. This does not require trust links between the domains.
--
Daniel / comments
Hi,
It isn't possible to disable the windows server information monitoring.
If you are running the Alert Repository on Windows Server 2003 or later, you should be able to specify the windows accoun...
Hi Zturner,
That sounds about correct. You will be able to use the machine local account for the operating system part of the monitoring connection. For the SQL you will have to use SQL Server authentication.
Both the windows account and the sql server account will need to have the appropriate admin rights on the server and the SQL instance respectively.
Cheers,
--
Daniel / comments
Hi Zturner,
That sounds about correct. You will be able to use the machine local account for the operating system part of the monitoring connection. For the SQL you will have to use SQL Server auth...
Hi ZTuner,
SQL Response is usable in a multi domain envoroment, but with a restricted set of supported configurations. If you domains have a trust link between them, ie the domains recognise each others credentials, you can use SQL Response as if you only had one domain.
The more complex scenario is when you have mulitple domains which do not have a trust link. The SQL Response client depends on windows authentication to connect to the Alert Repository. This requires you to site your Alert Repository in the same domain as the admin machine you are intending to run the SQL Response Client from.
As your SQL Server may then reside in domains without a trust link, you will not be able to use windows authentication to connect to the SQL instance. In the Server properties dialog for your remote server you will need to explicitly specify the Windows credentials for the operating system and the SQL Server authentication credentials to be used for the SQL instance.
If you have any issues with this, please let me know.
Cheers / comments
Hi ZTuner,
SQL Response is usable in a multi domain envoroment, but with a restricted set of supported configurations. If you domains have a trust link between them, ie the domains recognise each o...
Hi Father Jack,
the batch separator (which is configured by default to be GO) and its relating syntax are not features of SQL Server. They are entirely part of SQL Server Management Studio.
As such, we decided support batch separators, but we have chosen not to support the <batch separator> nnn syntax.
This is already listed in our bug track system as issue SE-395
Cheers,
--
Daniel / comments
Hi Father Jack,
the batch separator (which is configured by default to be GO) and its relating syntax are not features of SQL Server. They are entirely part of SQL Server Management Studio.
As such...
How odd,
Could you email me a screenshot of the recommendation and the output you are getting in SSMS
Thanks,
--
Daniel / comments
How odd,
Could you email me a screenshot of the recommendation and the output you are getting in SSMS
Thanks,
--
Daniel
Hi Fatherjack.
You're correct, we use DBCC SHOWCONTIG (...) WITH TABLERESULTS, FAST and then filter the results by the LogicalFragmentation and minimum page count according to the Fragmented index recommendation configuration for that server.
Cheers,
--
Daniel / comments
Hi Fatherjack.
You're correct, we use DBCC SHOWCONTIG (...) WITH TABLERESULTS, FAST and then filter the results by the LogicalFragmentation and minimum page count according to the Fragmented index ...