Viewing 15 posts - 46 through 60 (of 308 total)
Service broker is the messaging technology that db mail implements in order to send messages, as the error states without it db mail will only queue messages and not be...
May 29, 2015 at 8:59 am
Yep, the data in the BLOBs is data retained "just in case". It has nothing to do with the day to day application operations.
I'm definitely leaning towards creating a dedicated...
May 6, 2015 at 8:52 am
I've been looking at filestream. From what I can see we get a good payoff with SELECTs hitting the table but pay a small penalty with inserts and deletes (which...
May 5, 2015 at 10:14 am
Sorry for the late reply Steve. It's been a three day weekend over here in Ireland. 😀
The tables holding the data are ~200-300GB on average I'd say. Not huge but...
May 5, 2015 at 6:59 am
Thanks again Steve.
Most of the applications that we have log XML blobs into their respective database(s), the worst example has over 1TB of data stored as XML.
Andrew
May 1, 2015 at 2:57 am
Further update on this (if anyone's watching it).
I added a new filegroup to the database and migrated all the nonclustered indexes to it. I was worried I'd get the same...
April 30, 2015 at 9:56 am
No one out there using a Content Addressable Storage system for blobs?
April 30, 2015 at 1:48 am
Nail on the head right there, test, test and test again.
Thanks very much!
April 29, 2015 at 9:59 am
Thanks for the reply Steve. Are there any issues around performing point in time restores with filestream? I've read a couple of articles online telling me to be wary.
April 29, 2015 at 9:51 am
The main challenge I'm facing with these BLOBs is that currently they go into a partitioned table (by day) and are stored for three months. After that, a stored procedure...
April 29, 2015 at 7:48 am
I'd get rid of the shrink database task immediately and then look at removing the index and statistics maintenance task by using Ola Hallengren's scripts separately.
I'd recommend running the...
April 28, 2015 at 4:28 am
Yes you can install SQL 2014 next to SQL 2008 and then restore the database.
Just remember to run the SQL upgrade advisor to make sure there won't be any problems...
April 28, 2015 at 4:25 am
I dropped and re-created the index on Saturday but excluded the database from any index maintenance until today. Have just re-tried running the maintenance job but had to stop it...
April 27, 2015 at 2:04 am
I'm not able to replicate on my dev instance and the job has again failed today with the same error even though I excluded the database.
I tried to drop and...
April 25, 2015 at 2:55 am
Running the rebuild now on my dev instance. Hopefully I'll be able to replicate the issue
April 24, 2015 at 10:52 am
Viewing 15 posts - 46 through 60 (of 308 total)