Have you checked also the last step mentioned in this:
http://www.asp.net/QuickStart/aspnet/doc/caching/SQLInvalidation.aspx
1.. Queries must explicitly include column names in the SELECT statement.
Using "SELECT *" results in a query that will not be registered with Sql
Server 2005 query notifications.
2.. Table names in queries must include the ownername. For example, if you
issue a query against the authors table in the pubs database, the query must
reference the table as "dbo.authors".
3.. The security identity running the query must have rights to register
queries for notification in Sql Server 2005. This right can be granted with
the following T-SQL command: GRANT SUBSCRIBE QUERY NOTIFICATIONS TO
username.
4.. The security identity running the query must also have rights to send
query notifications from Sql Server 2005. This right can be granted with the
following T-SQL command: GRANT SEND ON SERVICE::SqlQueryNotificationService
TO username.

Signature
Teemu Keiski
ASP.NET MVP, AspInsider
Finland, EU
http://blogs.aspadvice.com/joteke
>I have a ASP.NET web page with a SqlDataSource configured with the select
> pointing to a stored procedure. This works as expected and using the
[quoted text clipped - 51 lines]
>
> Thanks,
masmith - 04 Jul 2006 21:01 GMT
Yes I checked that and all the other information on what is required to make
it work.
What I have at this point is that it works on my development pc pointed to a
local database on my computer. It does not work when the connection is
pointed to a test database server or a production database server. All three
SQL instances are using the same copy of the database and have the same items
that are required to make it work set or permissions granted.
Is there any place or way I can get an error message or information when
what I assume is the SqlClient.SqlDependency.Start or the SqlDataSource fails
to do what is required for this to work?

Signature
Thank,
Mark
> Have you checked also the last step mentioned in this:
>
[quoted text clipped - 70 lines]
> >
> > Thanks,
masmith - 18 Jul 2006 16:46 GMT
After working with Microsoft I found two problems with what I was doing.
1) You can not use window authentication in the Application_Start event of
the Global.asax.
2) The SqlDependency.Start method needs some additional permission that you
would not normally give a typical user of the database. I determined that I
could leave the Start in the Application_Start event but hard code a SQL
login with the required permissions granted. I also implemented encryption
of the connectionString section in the web.config.
The following is a good article on permissions required by the
SqlDependency.Start:
http://www.codeproject.com/useritems/SqlDependencyPermissions.asp.

Signature
Sincerely,
Mark
> Yes I checked that and all the other information on what is required to make
> it work.
[quoted text clipped - 83 lines]
> > >
> > > Thanks,