Microsoft has started WINDOWS 7 Blog

 

http://blogs.msdn.com/yochay/default.aspx

The Microsoft Developer Network (MSDN) “Windows 7 Blog for Developers” is just what it’s name indicates, according to the first post, dated October 23.

“This blog will mainly focus on the development aspects of Windows 7 by providing valuable content for developers….By valuable content we mean that this blog will be a ‘one stop shop’ on the road to get yourself familiar with what Windows 7 has to offer for developers and how you can ‘Light-Up’ using Windows 7 features in your application.”

“(T)his blog is part of an effort to highlight Windows 7 development story, a story that for some reason got lost with Windows Vista. As part of the Windows 7 Evangelism team and as developers, we hope, together with you and the rest of the community will be able to create an open and direct dialog about developing for Windows 7.”

Microsoft also has started another Windows 7-related blog, known as the Springboard Series blog, which it is aiming at IT professionals.  According to the first post on that site by Windows Client IT Pro Director Celine Allee, the Windows client division will use this site to help business users make sense of “the speculation out there.”

PROACTIVE ISSUES

Proactive ISSUES

I have wondered many times, why a tester doesn’t share their test scripts to developers. Yes, for the reason they read the possible cases of testing and can pass the issue for those cases.

This envisaged an idea, how this can be done to help in a right direction and for delivering a high quality product. There arise a thought like revealing certain cases to the developers before they submit for testing.

Like, when the issue has been first raised by the tester, the tester should also raise few more issues like linked temporary issues. Such that when the developer goes thought the issue would also have knowledge of the linked issues that might occur while fixing this issue. This proactive method though raises few more issues but if you look closer into the design, the closing up of issues will be fast and with very high quality than the previous.

Now, digging onto the core concept of Proactive Issues. As the analyst suggest for any change request, the request document is sent to both development team and test team. The development team starts the design process and the test team starts writing test scripts. Now as an extra effort, the test team should also write scripts for proactive issues and should straight away raise proactive issues in the issue tracker tool. Now the developer will get the design doc as well the set of proactive issues. Any developer who fixes the code will have an understanding on what are the possible issues and the fixed code will not raise any error now. If so any error occurred and issue has been raised, now the tester should not raise a single issue, he should also raise the link and supportive issues along with it.

This stringent process can avoid the delay of issue cycle rotation and will boost up the delivery date. This was Just a flash came to my mind when I was about to sleep.

Hope the industry experts will reply comments about the same.

Dynamic Management Views (DMV)

Dynamic Management Views (DMV)

The Dynamic Management Views (DMV’s) gives administrator information about the current state of the SQL server machine. This information helps the administrator to diagnose the problems and tune the server for optimal performance.

The DMV’s exists in sys schema and starts with the name dm_.

For e.g.: to see the total physical memory of the SQL Server machine; then execute the below TSQL command:-

SELECT (Physical_memory_in_bytes/1024.0)/1024.0 AS Physical_memory_in_Mb

FROM sys.dm_os_sys_info

1. sys.dm_os_sys_info

This view returns the information about the SQL Server machine, available resources and the resource consumption.

select * from sys.dm_os_sys_info

2. sys.dm_os_hosts

This view returns all the hosts registered with SQL Server 2005.

select * from sys.dm_os_hosts

3. sys.dm_os_schedulers

Sys.dm_os_schedulers view will help you identify if there is any CPU bottleneck in the SQL Server machine.

SELECT * FROM sys.dm_os_schedulers

4. sys.dm_io_pending_io_requests

This dynamic view will return the I/O requests pending in SQL Server side.

select * from sys.dm_io_pending_io_requests

5. sys.dm_io_virtual_file_stats

This view returns I/O statistics for data and log files [both MDF and LDF files]

select * from sys.dm_io_virtual_file_stats(6,2)

6. sys.dm_os_memory_clerks

This DMV will help how much memory SQL Server has allocated through AWE.

To get the memory consumption by internal components of SQL Server 2005.

SELECT TOP 10 type,

SUM(single_pages_kb) as [SPA Mem, Kb]

FROM sys.dm_os_memory_clerks

GROUP BY type

ORDER BY SUM(single_pages_kb) DESC

7. sys.dm_os_ring_buffers

This DMV uses RING_BUFFER_RESOURCE_MONITOR and gives information from resource monitor notifications to identify memory state changes. Internally, SQL Server has a framework that monitors different memory pressures. When the memory state changes, the resource monitor task generates a notification. This notification is used internally by the components to adjust their memory usage according to the memory state.

The record column will be in the XML format.

SELECT * FROM sys.dm_os_ring_buffers

WHERE ring_buffer_type = ‘RING_BUFFER_RESOURCE_MONITOR’

8. sys.dm_db_file_space_usage

This DMV provides the space usage information of TEMPDB database.

select * from sys.dm_db_file_space_usage

9. sys.dm_db_session_space_usage

This DMV provides the number of pages allocated and de-allocated by each session for the database.

select * from sys.dm_db_session_space_usage

10. sys.dm_db_partition_stats

This DMV provides page and row-count information for every partition in the current database.

SELECT * FROM sys.dm_db_partition_stats

11. sys.dm_os_performance_counters

Returns the SQL Server / Database related counters maintained by the server.

SELECT * FROM sys.dm_os_performance_counters WHERE counter_name = ‘Log File(s) Used Size (KB)’

12. sys.dm_db_index_usage_stats

This DMV is used to get useful information about the index usage for all objects in all databases. This also shows the amount of seeks and scan for each index.

SELECT * FROM sys.dm_db_index_usage_stats ORDER BY object_id, index_id

13. sys.dm_exec_sessions

This DMV will show all the information about each session connected to SQL server.

SELECT * FROM sys.dm_exec_sessions WHERE session_id >= 51

14. sys.dm_exec_connections

This DMV shows all the connections to SQL server.

SELECT * FROM sys.dm_exec_connections

15. sys.dm_exec_requests

This will give details on what each connection is actually performing in SQL server.

SELECT * FROM sys.dm_exec_requests WHERE session_id >= 51

16. sys.dm_exec_sql_text

This dynamic management function returns the text of a SQL statement given a sql handle.

SELECT * FROM sys.dm_exec_requests r

CROSS APPLY

sys.dm_exec_sql_text(sql_handle) AS st

WHERE r.session_id > 51

 

Push forward your comments…