Mysterious Views

I have two views in a production database that I did not create and I cannot account for. From the names used and the syntax of the views, it seems that the system (SQL Server) generated them.

Name: _hypmv_0_5771
Name: _hypmv_0

The syntax crushes the entire SELECT statement (4357 characters) onto a single line of T-SQL (not something I'm usually in the habit of doing).

I have read on kbAlertz that there was a bug in the original release of SQL server where the Index Tuning Wizard did not always remove hypothetical indices used to calculate performance improvements. I have not found anything related to hypothetical views. I do have indexed views, but none that reference these views.

I have checked dependencies; nothing depends on these views and they, in turn, do not depend on anything else.

Has anyone else encountered this problem? Aside from saving the definitions and then dropping them (just to see what may break), are there any suggestions for how to deal with this?

The database is medium-large. About 25GB.

Thanks,

Hugh ScottHere is the article on hypothetical indexes...

http://support.microsoft.com/?id=290414

MySQL 5.0 Views wont work with crystal reports

I can access my view data through the application, but when i try to create the report in crytal reports and set up the database through an odbc driver 3.51.

If i click on a normal table its fine, but with the views it says

"Error Opening File: There are no fields in the file: "[View name]".Hi,

I've got a similar problem but using a stored proc. (See earlier posting for more info)

After much hair-pulling and soul searching i think that their might be a compatibility problem with MySQL5, MyODBC 3.51 and Crystal.

Have you tried MyODBC 5.0 yet? If it installs and works on yr side that might take yr problem away. And if it does, please let us know what you did cause it dont wanna install here.

Thanks and good luck|||Thanks

I have tried the 5.0 ODBC Connector, but unfortunatly i had no joy. Still the same error.