I ran accross a field in a flat file yesterday that was in the format of "CCYYDDD". Now I can only assume that "CC" means century, but that's not the point. The actual value was "2008294". I needed to write an expression that converted the year and day of year format to a standard date. Here's the expression to do this (thank you to Ed Buhain for brainstorming): DATEADD("d", ((DT_I4)SUBSTRING(Date, 5, 3) - 1), (DT_DATE)("1/1/" + SUBSTRING(Date, 1, 4))) Where "Date" is the value you need to convert....
Man, this issue has been kicking my butt all day. We've been working on a SharePoint 2003 upgrade (testing) and got to the final content database. Life was good up to this point. 110GB of content had upgraded and there were just a few hiccups, mostly related to size. Then, it came. The nasty, evil, dispicable: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. Over and Over... Basically what's happening from what we can tell is SQL Server...
Again, maybe old news but I thought I would post something interesting that happened during a recent upgrade from SPS 2003 to MOSS. SharePoint is very finicky when it comes to database transactions and sizing during the gradual upgrade process. Here are a couple of things to note: 1. Make sure you have enough size - When upgrading a site that had about 150GB in content, we needed about 500GB in space to complete the migration. 2. Make sure you know where your _Pair DB's Are - SharePoint for some...
This may be old news, but we just hit this issue the other day. If you try to upgrade an instance of SharePoint Portal Server 2003 or WSS 2.0 that is running on a named instance of SQL Server called "SharePoint", the gradual upgrade option is greyed out. It turns out that this is because the installer thinks that you are trying to upgrade an instance of MSDE. Changing the instance name to something other than "SharePoint" does the trick. Talk about hardcoding something
To continue in the traditiion of trackbacks, and since I can't seem to find an orginal post in my body, I thought that I would share this one with you. Jason Follas psted a solution on how to get SQL Client, running on Vista, to use different credentials when connecting to a SQL Server using Windows Authentication. Basically, there are a ton of posts out there, but this is the ONLY one that that I could find that had the solution. Here's the link to the full explantion: Making SQL Server Management...