Retrieving SMSVIEW Data Using MS Access

Last reviewed: February 4, 1998
Article ID: Q153534
The information in this article applies to:

- Microsoft Systems Management Server, versions 1.0, 1.1 and 1.2

SUMMARY

There are problems associated with Querying within SMS - SMS Query Results Display Only First Data Record. Another application is necessary to retrieve the correct data. For instance, Access can be used to retrieve drive information from the SMS Database Views.

MORE INFORMATION

To retrieve drive information from SMS Databease Views using Access, perform the following steps.

  1. Run SMSVIEW to create the views.

  2. Confirm SQL connectivity using ODBC Manager.

  3. Start Access and create a new database.

  4. Select File, and then select Get External Data.

  5. Select Import and in Files of Type select ODBC Databases.

  6. Select your SMS data source and log in to SQL.

  7. Select all the tables preceded by 'dbo.v' - the views.

  8. Open the Tools / Relationships and Added dbo.vDisk and dbo_vIdentification.

  9. In the first table, select dwMachineID. Drag and drop dwMachineID into the second table.

  10. Open the Relationships window and select Create.

  11. In the Database window, select Queries and select New.

  12. Use the Simple Query Wizard.

  13. At the first screen, select dbo.vIdentification and choose SMSID0 as the selected field. Select dbo.vDisk and choose Disk_Index0, Storage_Size_MByte_0, Storage_Used_MByte_0, Free_Storage_MByte_0, and __Disk_Full0 as selected fields.

  14. At the next screen select Detail. At the Final screen give it a title and select Finish. At this point you should see all your SMSIDs and associated drives.

  15. Select View and selct SQL. You should see a query similar to:

SELECT DISTINCTROW [dbo.vIdentification].[SMSID0], [dbo.vDisk].[Disk_Index0], [dbo.vDisk].[Storage_Size__MByte_0], [dbo.vDisk].[Storage_Used__MByte_0], [dbo.vDisk].[Free_Storage__MByte_0], [dbo.vDisk].[__Disk_Full0] FROM dbo.vDisk INNER JOIN dbo.vIdentification ON dbo.vDisk].[dwMachineID]=[dbo.vIdentification].[dwMachineID];

  1. Modify this query to have the following as the final statement (note

        the query ends with the semicolon(;), so remove it from the original
        query before adding the final line):
    

    WHERE (((dbo.vDisk.Disk_Index0)>"B"));

Here is an example output:

SMSID0   Disk_Index0 Storage_Size__MByte_0   Storage_Used__MByte_0
Free_Storage__MByte_0   __Disk_Full0
UUU01000     C     324         284         40          88
UUU01000     D     324         267         57          83
UUU02000     C     502         398         104         80
UUU02000     D     1545        1426        119         93
UUU02001     C     514         347         167         68
UUU01001     C     514         347         167         68
UUU01002     C     202         171         31          85


KBCategory: kbnetwork
KBSubcategory: smsdatabase
Additional query words: 1.00 1.10 1.20 prodsms views smsview.exe report
Keywords : smsdatabase kbfaq kbnetwork
Version : 1.00 1.10 1.20
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 4, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.