Viewing 15 posts - 31 through 45 (of 73 total)
Great question.
I did not find it ambiguous, in fact this line removed the ambiguity.
Restore all transaction log backups taken since the latest differential backup restored with norecovery.
April 30, 2010 at 8:54 am
Unfortunately, I don't have an answer yet for the cause. We've restored the backup and run the reindexing job on another server (same SAN and disks though), but it...
February 26, 2010 at 8:08 am
Agreed, we've looked over our SAN logs, but haven't found the "smoking gun" yet. We're in the process of looking over our fiber channel logs. Just an FYI,...
February 25, 2010 at 8:25 am
Whoops, I suppose I wasn't reading the best in the heat of moment. You are correct, this is an SQL Server 2005 instance.
February 24, 2010 at 12:57 pm
Thanks Gila. I was hoping to do a page restore, but I guess we're not looking good. I did read on BOL that we wouldn't be able to restore...
February 24, 2010 at 11:45 am
Thanks David, I appreciate your follow up comments and great article.
February 10, 2010 at 1:18 pm
David.Poole (2/10/2010)
I didn't use a filtered or nonclustered index on the base table for two reasons.1. The original solution was on SQL2000.
Given SQL 2005/2008 would you recommend the same solution,...
February 10, 2010 at 12:04 pm
In regards to "The dreaded BIT field problem", what are your throughts on using an indexed filtered view instead of a table? IE
CREATE VIEW DocumentList WITH SchemaBinding
AS
SELECT DocumentID
FROM ProcessingQueue
WHERE...
February 10, 2010 at 8:28 am
I can see where this could come in handly during ETL processes.
In regards to creating a delimited list see the example here on MSDN http://msdn2.microsoft.com/en-us/library/ms131056.aspx. Using a CLR it...
January 26, 2010 at 8:06 am
adrinkwine (11/11/2009)
It appears the SQL Job isn't passing in my string value correctly. Its a basic UNC path to a folder, but the path does have some spaces it a...
December 23, 2009 at 8:35 am
After some thought I came up with the following solutions.
1. Turn a blind eye and hope for the best
2. Develop our own package configuration mechanism
3. Treat all warnings as errors
4....
June 10, 2009 at 10:51 am
I recently posted about Package Configurations throwing Warnings rather than Errors. I don't suppose you've solved that problem as well? My current solution treats all warnings as errors.
http://www.sqlservercentral.com/Forums/Topic724499-148-1.aspx#bm724516
June 3, 2009 at 8:38 am
Jamie Thompson noted this as a problem as well and provided us a link to an MSDN forum discussion here.
May 27, 2009 at 4:25 pm
I just found this on Connect. Please vote for it if you are affected by this issue.
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127206
Also, I'm still looking for a viable work around. So far, I...
May 27, 2009 at 1:35 pm
Perhaps using Persisted Computed Columns could provide the best of both worlds? Define the attributes as columns accordingly and then use the computed columns to be the bit stuffed...
May 21, 2009 at 8:18 am
Viewing 15 posts - 31 through 45 (of 73 total)