Viewing 15 posts - 31 through 45 (of 70 total)
Unfortunately that is not possible, SQL Database Dashboard uses SQL 2005 DMV's only.
I recommend you use @analyticsperformance Tool [/url] (http://www.analyticsperformance.com/) to monitoring SQL 2000, SQL 2005 and SQL...
November 29, 2009 at 1:50 pm
Hi
What exactly do you need?? I don't follow you.
Regards
November 29, 2009 at 1:18 pm
November 29, 2009 at 1:16 pm
Microsoft doesn't recommend restore or overwrite a database into replication schema.
You should rebuilt the database replication again to maintain the same SNC into the new database restored.
November 29, 2009 at 1:08 pm
If you can record your IO, CPU, Memory, etc., you can use @analyticsperformance (http://www.analyticsperformance.com/%5B/url%5D) and get amazing information to analyze different IO configurations and get metrics about them.
If...
November 29, 2009 at 12:57 pm
Hi we did a test using HP StorageWorks DButil and EMC technology as well, they works fine in small database with low transaction processing, but when the databases were big...
November 29, 2009 at 12:49 pm
You need to implement a control process to know when there are pending records to process,
Something like create a control tables to know when there is a pending process and...
November 29, 2009 at 12:40 pm
You can implement Service Broker and Messaging Technology to notify your clients.
Review this link for more information.
http://www.developer.com/db/article.php/3640771/Getting-Started-with-SQL-Server-Service-Broker.htm
November 29, 2009 at 9:55 am
By default the user must have READ-ONLY, you don't modify the permissions on system dictionary objects.
Regards
November 29, 2009 at 9:51 am
Could you explain with more details your environment? , I don't follow you
Regards
November 29, 2009 at 9:46 am
You can save the DTS package and review the workflow to detect the truncate problem.
November 29, 2009 at 9:39 am
You should try to enable a SQL Job output Log to some log file and verify what was the last step done and get more info about this.
November 28, 2009 at 4:19 pm
Please try to analyze and review the Setup log file located into to get more information about the error.
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files
Regards
November 27, 2009 at 3:28 pm
Please take as reference this Microsoft Guide
SQL Server 2008 Upgrade Technical Reference Guide
November 27, 2009 at 3:14 pm
Viewing 15 posts - 31 through 45 (of 70 total)