141 reputation
6
bio website
location
age
visits member for 3 months
seen 16 hours ago
stats profile views 5

Feb
8
comment SQL Server: reset all database tables
In our environment we always keep a baseline db with barebones lookups populated, every deployment we do starts with that baseline db, and all schema changes are synced to it. We also have the scripts to recreate this db and the lookups in source control, for versioning.
Feb
8
comment Quick way to validate two tables against each other
Is SSIS an option? It'd be fairly easy to read in the one table and do a lookup against the other.
Feb
5
awarded  Custodian
Feb
5
reviewed Reviewed Academic Journals and Reviews for Database Systems
Feb
2
comment Who changed the size of the transaction log?
Here's an example of using the default trace to find out about log growth: strictlysql.blogspot.ca/2011/01/…
Feb
1
awarded  Scholar
Feb
1
accepted Error: 9245, Severity: 16, State: 1. / During the last time interval XXX query notification errors were suppressed
Jan
30
revised Error: 9245, Severity: 16, State: 1. / During the last time interval XXX query notification errors were suppressed
added 129 characters in body
Jan
30
answered Error: 9245, Severity: 16, State: 1. / During the last time interval XXX query notification errors were suppressed
Jan
30
revised Error: 9245, Severity: 16, State: 1. / During the last time interval XXX query notification errors were suppressed
added 205 characters in body
Jan
30
comment Error: 9245, Severity: 16, State: 1. / During the last time interval XXX query notification errors were suppressed
@JonSeigel, yes we are using SqlDependency, and quite possibly incorrectly. I've added some additional information to the question regarding that.
Jan
30
revised Error: 9245, Severity: 16, State: 1. / During the last time interval XXX query notification errors were suppressed
added 1357 characters in body
Jan
30
awarded  Supporter
Jan
29
awarded  Student
Jan
29
asked Error: 9245, Severity: 16, State: 1. / During the last time interval XXX query notification errors were suppressed
Jan
28
comment Primary filegroup is full SQL Server 2008
Do you have more physical disk space available? If so, check the SQL Server error logs and see if there is additional information on why the autogrowth failed.
Jan
23
awarded  Teacher
Jan
23
awarded  Editor
Jan
23
revised Use Older Versions Of SQL Server Databases With 2012?
added 106 characters in body
Jan
23
answered Use Older Versions Of SQL Server Databases With 2012?