Thursday, August 5, 2010
migrating login and password from sql server 2000 to sql server 2005
for personal ref: http://support.microsoft.com/kb/246133
Monday, August 2, 2010
Quick way to migrate DTS packages to SQL Server 2005
Migration is done using the SQL Server Package Migration Wizard.
This works to an extent - more complex packages will require some customizations and code changes.
Go to\Microsoft SQL Server\90\DTS\Binn to locate DTSMigrationWizard.exe. Alternatively, expand the DB server in Management Studio, expand management and then legacy in Object Explorer. Right click on DTS and select the wizard.
Choose source/destination server, and DTS packages. Then click Finish and wait for the wizard to import.
So now the packages are migrated, how do you know whether it works?
In SQL Server Management Studio, connect to Integration Services. (File->Connect Object Explorer).
Expand Stored Packages of the server instance. The migrated packages should be under MSDB.
Start performing test runs and pray for no errors to occur!
There's a great article that shows more details, here.
Part 2:
After successfully importing the DTS packages, we still need to set up the jobs. Script the jobs from SS2000 and just run the queries to create jobs in SS2005 master database.
Some stuff to take note:
Create a new database maintenance plan and let SSIS and SS2005 take care of the rest, as opposed to migrating the job and DTS over from SS2000 and spend time troubleshooting.
If the migrated job failed with an error like this:
Message
Executed as user: XXXXX\SYSTEM. Description: One or more component failed validation. End Error Error: 2010-08-04 01:00:43.37 Code: 0xC0024107 Source: DTSTask_DTSDataPumpTask_1 Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 1:00:00 AM Finished: 1:00:43 AM Elapsed: 42.75 seconds. The package execution failed. The step failed.
Try changing the DTS package's protection level as stated here.
For my case I just re-import the package from my local File System and used "Rely on Server Storage and Roles..."
EOS.
This works to an extent - more complex packages will require some customizations and code changes.
Go to
Choose source/destination server, and DTS packages. Then click Finish and wait for the wizard to import.
So now the packages are migrated, how do you know whether it works?
In SQL Server Management Studio, connect to Integration Services. (File->Connect Object Explorer).
Expand Stored Packages of the server instance. The migrated packages should be under MSDB.
Start performing test runs and pray for no errors to occur!
There's a great article that shows more details, here.
Part 2:
After successfully importing the DTS packages, we still need to set up the jobs. Script the jobs from SS2000 and just run the queries to create jobs in SS2005 master database.
Some stuff to take note:
Create a new database maintenance plan and let SSIS and SS2005 take care of the rest, as opposed to migrating the job and DTS over from SS2000 and spend time troubleshooting.
If the migrated job failed with an error like this:
Message
Executed as user: XXXXX\SYSTEM. Description: One or more component failed validation. End Error Error: 2010-08-04 01:00:43.37 Code: 0xC0024107 Source: DTSTask_DTSDataPumpTask_1 Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 1:00:00 AM Finished: 1:00:43 AM Elapsed: 42.75 seconds. The package execution failed. The step failed.
Try changing the DTS package's protection level as stated here.
For my case I just re-import the package from my local File System and used "Rely on Server Storage and Roles..."
EOS.
unicode escape formats
For my personal reference only. The original article can be found here.
The following are ASCII representations of Unicode characters known to be used in
various contexts. In a few cases we also include unusual representations of integers
since integers are sometimes converted to characters.
The following are ASCII representations of Unicode characters known to be used in
various contexts. In a few cases we also include unusual representations of integers
since integers are sometimes converted to characters.
| Description | Example | Usage |
|---|---|---|
| raw hex | 00E9 | Unicode Consortium file NamesList.txt |
| prefix 0x hex | 0x00E9 | Yudit keymap source files |
| prefix v decimal | v233 | Perl |
| prefix $ hex | $00E9 | Alex Eulenberg Mac OS X keyboard map source files |
| prefix # with suffix # hex | #00E9# | Mimer SQL |
| prefix #$ hex | #$00E9 | some Pascals including Delphi |
| prefix 16# hex | 16#00E9 | Postscript |
| prefix #x hex | #x00E9 | some Common Lisp implementations |
| prefix #16r hex | #16r00E9 | Common Lisp integer |
| prefix backslash hex [4] | \00E9 | Oracle in unistr function |
| prefix backslash-u decimal | \u0233 | Rich Text Format |
| prefix backslash-u hex [4] | \u00E9 | Java, Ruby |
| prefix backslash-u left brace hex [variable] right brace | \u{E9}, \u{000E9}, multiple codepoints: \u{E9 74 E9} | Ruby |
| prefix backslash-U hex [8] outside BMP, prefix backslash-u hex [4] within BMP | \u00E9 | C#, D, Python, Scheme, Tcl |
| prefix U hex | U00E9 | |
| prefix u hex | u00E9 | |
| prefix u HEX [5-6] | u100E9 | Fontlab Studio outside BMP |
| prefix %u hex | %u00E9 | |
| prefix U+ hex | U+00E9 | Unicode Consortium documents |
| prefix uni HEX [4] | uni00E9 | Fontlab Studio within BMP |
| prefix X with hex in single quotes | X'00E9' | some IBM documentation |
| prefix X with hex in double quotes with optional type postfix character c[har], d[char], w[char] | X"00E9"d | D |
| prefix 16# and suffix # hex | 16#00E9# | Ada |
| prefix U in angle brackets hex | <U00E9> | POSIX locale specifications |
| prefix backslash-x hex | \x00E9 | C wide string, Tcl integer |
| prefix backslash-x hex in braces | \x{00E9} | Perl |
| prefix backslash {U+ hex with suffix } | \{U+E9} | BitC |
| prefix &# with suffix ; decimal | é | HTML, XML, XHTML |
| prefix &#x hex with suffix ; | é | HTML, XML, XHTML |
| prefix &# decimal | é | SGML, HTML (deprecated) |
| prefix &#x hex | é | SGML, HTML (deprecated) |
| prefix backslash-# decimal | \#0233; | SGML |
| prefix backslash-#x hex | \#x00E9; | SGML |
| prefix _x and suffix _ hex | _x00E9_ | OOXML, SQL/XML |
| 3 low bytes each with backslash prefix in big-endian order octal | \000\000\351 | |
| 3 low bytes each with backslash-x prefix in big-endian order hex | \x00\x00\xE9 | |
| 3 low bytes each with backslash-d prefix in big-endian order decimal | \d000\d000\d233 | POSIX locale specifications |
| prefix " hex[4] (UTF16 - use surrogate pairs beyond BMP) | "00E9 | XeTeX |
| hex UTF-8 with each byte's hex preceded by an =-sign | =C3=A9 | RFC 2045 Quoted Printable |
| hex UTF-8 with each byte's hex preceded by a %-sign | %C3%A9 | RFC 2396 URI escape format |
| hex UTF-8 with each byte's hex preceded by a backslash-x | \xC3\xA9 | Apache log format |
| hex UTF-8 with each byte's hex surrounded by angle brackets | <C3><A9> | print format for uninterpreted bytes used by various programs |
| octal UTF-8 with backslash prefixes | \303\251 | print format for uninterpreted bytes used by various programs |
Tuesday, July 27, 2010
sharepoint 2007 - group list by week
Was googling for sharepoint formulas on retrieving a week number based on date when this came up 2nd on top.
http://sharepoint-guru.blogspot.com/2008/03/group-list-by-week-number.html
Nifty, short and sweet.
INT(([Column name]-DATE(YEAR([Start Time]),1,1))/7)
http://sharepoint-guru.blogspot.com/2008/03/group-list-by-week-number.html
Nifty, short and sweet.
INT(([Column name]-DATE(YEAR([Start Time]),1,1))/7)
Monday, July 26, 2010
neverendingshowingoffness
neverendingshowingoffness ANNOYS the hell out of me.
Subscribe to:
Posts (Atom)