|
|
Posted by candide_sh on 01/29/07 10:27
hello Erland
the GUID-value was created by the upsizing wizard of MS-Access2003 and
I really don't know what for it is. But the conservative way is to not
touch the values created by this wizard. As the script generated by DB
Pub wizard crashed at only this one GUID-value (others worked fine) I
commented this line out and manually copy/pasted this value. Well
done...
On 26 Jan., 23:42, Erland Sommarskog <esq...@sommarskog.se> wrote:
> (candide...@yahoo.de) writes:
> > DB Pub Wizard comes from SS2005, from Microsoft SQLServer2005 website
> > (search for feature pack)
> > I guess it creates a script file (myscript.sql) but doesn't create this
> > file in UNICODE. I searched and played around in SS2005, but I think I
> > can't influence the behaviour of DB Pub Wizard (writing only ANSI) from
> > SS2005.
>
> > Remember I open QA in SS2000 to start this script. Thanks for your
> > hint, I found the dialog box in QA and changed the file format to
> > Unicode, but no success.I downloaded the DB Publish Wizard, and it does indeed generate a Unicode
> file. I had created this table on SQL 2005:
>
> CREATE TABLE utländsk(a nvarchar(234) NOT NULL)
> go
> INSERT utländsk(a) VALUES (nchar(8080) + nchar(324))
>
> and I was able to insert that data successfully on SQL 2000 through
> Query Analyzer.
>
> Maybe there is some special catch with extended properties. (I never
> use them myself, so I did not play with one.)
>
> What is in that extended property on SQL 2005?
>
> --
> Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
>
> Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
> Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|