Viewing 15 posts - 11,521 through 11,535 (of 49,562 total)
Here things are still getting worse (mining problems and government blunderings not helping), so I'm seeing less demand for competant (expensive) people and more 'oh, you've done a university course...
September 28, 2013 at 4:44 am
I don't have links to any offhand. I use google for that.
September 28, 2013 at 4:38 am
Thursday at Summit is going to be sooo funny. Just saying...
September 27, 2013 at 4:36 pm
Ok, so you can nest roles. So you'd add db_datareader and db_datawriter to your custom role.
September 27, 2013 at 4:05 pm
Sean Lange (9/27/2013)
When all else fails...do as the Romans!!!
Fall upon your sword? Fiddle while Rome burns?
September 27, 2013 at 4:03 pm
You can't just run checktable on all tables, you need check alloc and check catalog too. Could be that it's one of those phases that's failing checkDB. Can't tell without...
September 27, 2013 at 9:57 am
Please read what I wrote
CheckDB and CheckCatalog BEFORE the upgrade and if there are any errors do not proceed!!!
Then, after the upgrade CheckDB with data purity, update usage, update...
September 27, 2013 at 9:54 am
Grant those roles to the user, you can't afaik nest roles.
September 27, 2013 at 9:51 am
If there is corruption, CheckDB will always find it. If you've manually edited an unallocated page, or the middle of a page when you don't have page checksums enabled, then...
September 27, 2013 at 6:14 am
BEFORE you update, run DBCC CheckDB and DBCC CheckCatalog. If there are any errors, do not go further.
After, checkDB with data purity, update all statistics, update usage. Order doesn't really...
September 27, 2013 at 6:12 am
More insecure dynamic SQL....
Please, do you company a favour and stop writing dynamic SQL until you've read up and understand SQL injection.
September 27, 2013 at 1:58 am
You'll need to download a SQL 2008 or earlier adventureworks. The 2012 one is a 2012 database and hence can only be restored to SQL 2012 or newer.
September 27, 2013 at 1:56 am
Depends on the workload. There is absolutely no way to answer that question in a useful way.
September 27, 2013 at 1:54 am
johntam (9/26/2013)
Updating stats on all of the affected tables with FULLSCAN solved the problem.
That's what I suspected. The plans showed different estimated row counts, so that was a second indication...
September 27, 2013 at 1:50 am
Viewing 15 posts - 11,521 through 11,535 (of 49,562 total)