-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
not detecting any change in table when deployed on IIS 8 windows server #46
Comments
Hi. Deployment is done using a backup database? |
Backup database? |
I created database in sql server in windows server, everything is running fine but not detecting any change |
Ok. After runnig your application, can you see SqlTableDependency database objects? For example a new trigger on your database table? |
Also, which sqlserver version are you usung? |
private string ConnectionString { get { return System.Configuration.ConfigurationManager.ConnectionStrings["DefaultConnection"].ConnectionString; } }
|
sql 2014 enterprise |
ok...your code is fine. I ask that, because can be that DB you are using was created from a old SQL Server instance (for example 2008). Even if now it is under SQL 2014 enterprise, it conserve settings that make it not compatible with SqlTableDependency. |
If you run this SQL script on DB (the one used by deployed on IIS 8 windows server) SELECT DatabaseProperty('the database name', 'version') what is the result you get? |
Also, can you run these two scripts? SELECT name, compatibility_level from sys.databases WHERE name = 'the database name' SELECT name, version from master.dbo.sysdatabases where name = 'the database name' |
ok...last thing. |
thank you for your cooperation to
or in simple by just removing "Integrated Security=True" from my connection string |
It seems to not work with Integrated Authentication |
not detecting any change in table when deployed on IIS 8 windows server, I made dependencies on two tables but none of them is working, but working perfectly on localhost
The text was updated successfully, but these errors were encountered: