Showing posts with label file. Show all posts
Showing posts with label file. Show all posts

Friday, March 30, 2012

not a valid undo file for database

Hi,
I've restored a database from backup, with STANDBY option.
Now, when I'm trying to apply further Transaction logs to
this database, the restore log command is failing with an
error 'File 'd:\standby.undo' is not a valid undo file for
database 'xyz', database ID 24.
Please let me know how to I avoid this error and restore
logs to this database.
Does the file mentioned in the error message actually exist?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ykchakri" <anonymous@.discussions.microsoft.com> wrote in message
news:21a001c4aa62$329a33a0$a501280a@.phx.gbl...
> Hi,
> I've restored a database from backup, with STANDBY option.
> Now, when I'm trying to apply further Transaction logs to
> this database, the restore log command is failing with an
> error 'File 'd:\standby.undo' is not a valid undo file for
> database 'xyz', database ID 24.
> Please let me know how to I avoid this error and restore
> logs to this database.
|||Yes, it does. And I've tried renaming this file and then
it gives a different error that the file does not exist.
SO, I'm sure that it is able to access this file, but
something is not right in this file.
What's the purpose of this file anyway ?

>--Original Message--
>Does the file mentioned in the error message actually
exist?
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>
>"ykchakri" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:21a001c4aa62$329a33a0$a501280a@.phx.gbl...
option.[vbcol=seagreen]
to[vbcol=seagreen]
an[vbcol=seagreen]
for
>
>.
>
|||The UNDO file is created when you perform RESTORE using the STANDBY option.
This is because SQL Server will actually perform recovery based on the transaction log when you are
using STANDBY, but as you say you want to be able to perform additional restores, SQL Server will
save the recovery work it performs in this undo file so it can undo the recovery work when you do
the next restore.
SQL Server will remember the name of the undo file so it will automatically find it when next
restore is performed. In this case, SQL Server doesn't recognize the undo file as a valid file.
Perhaps someone deleted the file and just created one through notepad, or picked some other UNDO
file and renamed it? Bottom-line is that SLQ Server *need* a valid UNDO file for the next restore.
You can always re-start all restores from the latest database backup.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ykchakri" <anonymous@.discussions.microsoft.com> wrote in message
news:2abc01c4ab08$347ecdb0$a501280a@.phx.gbl...[vbcol=seagreen]
> Yes, it does. And I've tried renaming this file and then
> it gives a different error that the file does not exist.
> SO, I'm sure that it is able to access this file, but
> something is not right in this file.
> What's the purpose of this file anyway ?
> exist?
> message
> option.
> to
> an
> for
sql

not a valid undo file for database

Hi,
I've restored a database from backup, with STANDBY option.
Now, when I'm trying to apply further Transaction logs to
this database, the restore log command is failing with an
error 'File 'd:\standby.undo' is not a valid undo file for
database 'xyz', database ID 24.
Please let me know how to I avoid this error and restore
logs to this database.Does the file mentioned in the error message actually exist?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ykchakri" <anonymous@.discussions.microsoft.com> wrote in message
news:21a001c4aa62$329a33a0$a501280a@.phx.gbl...
> Hi,
> I've restored a database from backup, with STANDBY option.
> Now, when I'm trying to apply further Transaction logs to
> this database, the restore log command is failing with an
> error 'File 'd:\standby.undo' is not a valid undo file for
> database 'xyz', database ID 24.
> Please let me know how to I avoid this error and restore
> logs to this database.|||Yes, it does. And I've tried renaming this file and then
it gives a different error that the file does not exist.
SO, I'm sure that it is able to access this file, but
something is not right in this file.
What's the purpose of this file anyway ?
>--Original Message--
>Does the file mentioned in the error message actually
exist?
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>
>"ykchakri" <anonymous@.discussions.microsoft.com> wrote in
message
>news:21a001c4aa62$329a33a0$a501280a@.phx.gbl...
>> Hi,
>> I've restored a database from backup, with STANDBY
option.
>> Now, when I'm trying to apply further Transaction logs
to
>> this database, the restore log command is failing with
an
>> error 'File 'd:\standby.undo' is not a valid undo file
for
>> database 'xyz', database ID 24.
>> Please let me know how to I avoid this error and restore
>> logs to this database.
>
>.
>|||The UNDO file is created when you perform RESTORE using the STANDBY option.
This is because SQL Server will actually perform recovery based on the transaction log when you are
using STANDBY, but as you say you want to be able to perform additional restores, SQL Server will
save the recovery work it performs in this undo file so it can undo the recovery work when you do
the next restore.
SQL Server will remember the name of the undo file so it will automatically find it when next
restore is performed. In this case, SQL Server doesn't recognize the undo file as a valid file.
Perhaps someone deleted the file and just created one through notepad, or picked some other UNDO
file and renamed it? Bottom-line is that SLQ Server *need* a valid UNDO file for the next restore.
You can always re-start all restores from the latest database backup.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ykchakri" <anonymous@.discussions.microsoft.com> wrote in message
news:2abc01c4ab08$347ecdb0$a501280a@.phx.gbl...
> Yes, it does. And I've tried renaming this file and then
> it gives a different error that the file does not exist.
> SO, I'm sure that it is able to access this file, but
> something is not right in this file.
> What's the purpose of this file anyway ?
>>--Original Message--
>>Does the file mentioned in the error message actually
> exist?
>>--
>>Tibor Karaszi, SQL Server MVP
>>http://www.karaszi.com/sqlserver/default.asp
>>http://www.solidqualitylearning.com/
>>
>>"ykchakri" <anonymous@.discussions.microsoft.com> wrote in
> message
>>news:21a001c4aa62$329a33a0$a501280a@.phx.gbl...
>> Hi,
>> I've restored a database from backup, with STANDBY
> option.
>> Now, when I'm trying to apply further Transaction logs
> to
>> this database, the restore log command is failing with
> an
>> error 'File 'd:\standby.undo' is not a valid undo file
> for
>> database 'xyz', database ID 24.
>> Please let me know how to I avoid this error and restore
>> logs to this database.
>>
>>.

'not a valid Microsoft Tape Format backup set' error when trying to restore DB

Hello
I have a point in time Microsoft SQL Server 2000 .mdf data
file which was taken from a snapshot. Basically, it is the
database at a point in time, which I can attach to and
view data no problem in a sql server.
I also have hourly transaction logs which occured after
the above .mdf data file snapshot. I would like to apply
those transaction log files to the .mdf data file. I've
tried many many varieties, but seem to get farthest with
the following code:
ALTER DATABASE JDE_PRODUCTION SET SINGLE_USER WITH
ROLLBACK IMMEDIATE
GO
RESTORE DATABASE JDE_PRODUCTION
FROM DISK='F:\mssql7\jdedata\jde_PRODUCTIONdata_new.mdf'
WITH NORECOVERY
RESTORE LOG JDE_PRODUCTION
FROM DISK='F:\mssql7\jdedata\07-22-
2004_7.00.00__JDE_PRODUCTION.trb'
WITH NORECOVERY
[...MORE RESTORE HOURLY LOG STATEMENTS...]
RESTORE LOG JDE_PRODUCTION
FROM DISK='F:\mssql7\jdedata\07-22-
2004_13.00.01__JDE_PRODUCTION.trb'
WITH RECOVERY
/****end****/
My problem seems to be the following error:
Server: Msg 3242, Level 16, State 1, Line 2
The file on device 'F:\mssql7
\jdedata\jde_PRODUCTIONdata_new.mdf' is not a valid
Microsoft Tape Format backup set.
Can't seem to get around the fact that Microsoft is
looking for the restore database file as a Tape format,
which it isn't, it's a .mdf database file.
Any clues?
Thanks in advance...
JeffYou can't RESTORE from an 'mdf' file because a RESTORE command expects a
file created with BACKUP. The backup file will be in MTF format regardless
of the underlying media type.
The proper way to accomplish your task is to start with a full backup.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Jeff" <jblanding@.nwpasta.com> wrote in message
news:76fd01c47672$4443f470$a401280a@.phx.gbl...
> Hello
> I have a point in time Microsoft SQL Server 2000 .mdf data
> file which was taken from a snapshot. Basically, it is the
> database at a point in time, which I can attach to and
> view data no problem in a sql server.
> I also have hourly transaction logs which occured after
> the above .mdf data file snapshot. I would like to apply
> those transaction log files to the .mdf data file. I've
> tried many many varieties, but seem to get farthest with
> the following code:
> ALTER DATABASE JDE_PRODUCTION SET SINGLE_USER WITH
> ROLLBACK IMMEDIATE
> GO
> RESTORE DATABASE JDE_PRODUCTION
> FROM DISK='F:\mssql7\jdedata\jde_PRODUCTIONdata_new.mdf'
> WITH NORECOVERY
> RESTORE LOG JDE_PRODUCTION
> FROM DISK='F:\mssql7\jdedata\07-22-
> 2004_7.00.00__JDE_PRODUCTION.trb'
> WITH NORECOVERY
> [...MORE RESTORE HOURLY LOG STATEMENTS...]
> RESTORE LOG JDE_PRODUCTION
> FROM DISK='F:\mssql7\jdedata\07-22-
> 2004_13.00.01__JDE_PRODUCTION.trb'
> WITH RECOVERY
> /****end****/
> My problem seems to be the following error:
> Server: Msg 3242, Level 16, State 1, Line 2
> The file on device 'F:\mssql7
> \jdedata\jde_PRODUCTIONdata_new.mdf' is not a valid
> Microsoft Tape Format backup set.
> Can't seem to get around the fact that Microsoft is
> looking for the restore database file as a Tape format,
> which it isn't, it's a .mdf database file.
> Any clues?
> Thanks in advance...
> Jeff

Wednesday, March 28, 2012

Northwind database

Hello,
Can somebody send me the Nortwind database?
The MDF file or the sql file with the creates and inserts.
Thanks!
Arjenthere is a script on CD or in SQL folder to recreate Northwind. I don't
have SQL CD with me at this moment but I will look later. It must be there.
"Arjen" <boah123@.hotmail.com> wrote in message
news:bu9f45$eml$1@.news3.tilbu1.nb.home.nl...
quote:

> Hello,
> Can somebody send me the Nortwind database?
> The MDF file or the sql file with the creates and inserts.
> Thanks!
> Arjen
>
>
|||The script to create Northwind is part of the SQLServer distribution.
The file is called instnwnd.sql and the default path where it's located is:
C:\Program Files\Microsoft SQL Server\MSSQL\Install
David Portas
--
Please reply only to the newsgroup
--|||Okay! If you can find it... thaks!
Bacause I can't find it!
Thanks,
Arjen
"ME" <mail@.moon.net> schreef in bericht
news:%233R3VwG3DHA.2060@.TK2MSFTNGP10.phx.gbl...
quote:

> there is a script on CD or in SQL folder to recreate Northwind. I don't
> have SQL CD with me at this moment but I will look later. It must be

there.
quote:

> "Arjen" <boah123@.hotmail.com> wrote in message
> news:bu9f45$eml$1@.news3.tilbu1.nb.home.nl...
>
|||Correct!
Thanks!
Arjen
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> schreef in bericht
news:Jsqdncz5V9V-2ZXdRVn-gQ@.giganews.com...
quote:

> The script to create Northwind is part of the SQLServer distribution.
> The file is called instnwnd.sql and the default path where it's located

is:
quote:

> C:\Program Files\Microsoft SQL Server\MSSQL\Install
> --
> David Portas
> --
> Please reply only to the newsgroup
> --
>
|||Found it!
Thanks for your support!
Arjen
"ME" <mail@.moon.net> schreef in bericht
news:%233R3VwG3DHA.2060@.TK2MSFTNGP10.phx.gbl...
quote:

> there is a script on CD or in SQL folder to recreate Northwind. I don't
> have SQL CD with me at this moment but I will look later. It must be

there.
quote:

> "Arjen" <boah123@.hotmail.com> wrote in message
> news:bu9f45$eml$1@.news3.tilbu1.nb.home.nl...
>

Northwind database

Hello,
Can somebody send me the Nortwind database?
The MDF file or the sql file with the creates and inserts.
Thanks!
Arjenthere is a script on CD or in SQL folder to recreate Northwind. I don't
have SQL CD with me at this moment but I will look later. It must be there.
"Arjen" <boah123@.hotmail.com> wrote in message
news:bu9f45$eml$1@.news3.tilbu1.nb.home.nl...
> Hello,
> Can somebody send me the Nortwind database?
> The MDF file or the sql file with the creates and inserts.
> Thanks!
> Arjen
>
>|||The script to create Northwind is part of the SQLServer distribution.
The file is called instnwnd.sql and the default path where it's located is:
C:\Program Files\Microsoft SQL Server\MSSQL\Install
--
David Portas
--
Please reply only to the newsgroup
--|||Okay! If you can find it... thaks!
Bacause I can't find it!
Thanks,
Arjen
"ME" <mail@.moon.net> schreef in bericht
news:%233R3VwG3DHA.2060@.TK2MSFTNGP10.phx.gbl...
> there is a script on CD or in SQL folder to recreate Northwind. I don't
> have SQL CD with me at this moment but I will look later. It must be
there.
> "Arjen" <boah123@.hotmail.com> wrote in message
> news:bu9f45$eml$1@.news3.tilbu1.nb.home.nl...
> > Hello,
> >
> > Can somebody send me the Nortwind database?
> > The MDF file or the sql file with the creates and inserts.
> >
> > Thanks!
> > Arjen
> >
> >
> >
>|||Correct!
Thanks!
Arjen
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> schreef in bericht
news:Jsqdncz5V9V-2ZXdRVn-gQ@.giganews.com...
> The script to create Northwind is part of the SQLServer distribution.
> The file is called instnwnd.sql and the default path where it's located
is:
> C:\Program Files\Microsoft SQL Server\MSSQL\Install
> --
> David Portas
> --
> Please reply only to the newsgroup
> --
>|||Found it!
Thanks for your support!
Arjen
"ME" <mail@.moon.net> schreef in bericht
news:%233R3VwG3DHA.2060@.TK2MSFTNGP10.phx.gbl...
> there is a script on CD or in SQL folder to recreate Northwind. I don't
> have SQL CD with me at this moment but I will look later. It must be
there.
> "Arjen" <boah123@.hotmail.com> wrote in message
> news:bu9f45$eml$1@.news3.tilbu1.nb.home.nl...
> > Hello,
> >
> > Can somebody send me the Nortwind database?
> > The MDF file or the sql file with the creates and inserts.
> >
> > Thanks!
> > Arjen
> >
> >
> >
>

Normalize data?

I have two columes F1 and F2
Both are NUMBER but were orginally imported from a TXT file.
Is there any way to ENSURE, that there are no spaces and such inside the
fields to ensure proper matching? i.e. if I am trying to match F2 with F2
and one records is "1" and the second is "1 " (space added to the end) it
won't match, how do i remove spaces like this?
DennisIf both columns are numeric datatypes then they won't have leading or
trailing spaces. I don't know what you mean by "Both are NUMBER". There
is no built-in datatype called "NUMBER". Maybe you have a user-defined
type in which case you could just change the column to be a proper
NUMERIC or INTEGER for example.
David Portas
SQL Server MVP
--|||db wrote:
> I have two columes F1 and F2
> Both are NUMBER but were orginally imported from a TXT file.
> Is there any way to ENSURE, that there are no spaces and such inside
> the fields to ensure proper matching? i.e. if I am trying to match
> F2 with F2 and one records is "1" and the second is "1 " (space added
> to the end) it won't match, how do i remove spaces like this?
> Dennis
If your NUMBER columns are actually a character datatype, you should
trim your values before you insert into the table. You can also issue a
trim on the columns now to remove any leading white space.
David Gugick
Imceda Software
www.imceda.comsql

Monday, March 26, 2012

noobie question on CSV Flat Files

Hi there,

I am connecting to a CSV file. When I look at the raw CSV, most of rows look something like this:

"19056","CD","Rick James"
These rows work fine but I run it to trouble when some rows look like this in the raw form:

"134530","Poster","Elizabeth on the set of "Giant", 1955"

You can see the issue that will arrise, SSIS parses this as 4 columns. Note: In the "Flat File Connection Manager" I have the "text qualifier" set to ".

Any suggestions as to how I might process files that have this type of situation? Maybe some sort of pre-process is necessary?

Other than that I've had great success with the other components and I am enjoying SSIS very much, great product!

Flat File Source does not support Embedded Qualifiers. Parsing columns that contain data with text qualifiers will fail at run time.You can use the Flat File Source to load the data as unqualified data and use a script component later to strip off the qualifiers downstream. You can also write a custom component to do the same. There is an Undouble component available for download from

http://www.microsoft.com/downloads/details.aspx?FamilyID=B51463E9-2907-4B82-A353-E15016486E1D&displaylang=en

which you can use.

|||

Thanks Ranjeeta,

This is kind of what I figured would be the case. I'll ask the publisher of the CSV to perhaps rethink their practice of embedded qualifiers. If I have no luck with that, I'll have to do something similar to what you're describing. Thanks for the link!

Monday, March 12, 2012

non unicode

Hi,
Is DT_STR Unicode? From SSIS I am using a data conversion component
and defining the data type as DT_STR and saving the output in excel
file. I am getting an error that 'can not convert from Unicode to non-
unicode'. I thought I have already taken care of that in data
conversion.Could you explain exactly which data conversion you prepared? The DT_STR was
specified for the input field or for the output? In this last case, which is
the input field data type?
Gilberto Zampatti
"SB" wrote:
> Hi,
> Is DT_STR Unicode? From SSIS I am using a data conversion component
> and defining the data type as DT_STR and saving the output in excel
> file. I am getting an error that 'can not convert from Unicode to non-
> unicode'. I thought I have already taken care of that in data
> conversion.
>|||On Apr 20, 2:10 pm, Gilberto Zampatti
<GilbertoZampa...@.discussions.microsoft.com> wrote:
> Could you explain exactly which data conversion you prepared? The DT_STR was
> specified for the input field or for the output? In this last case, which is
> the input field data type?
> Gilberto Zampatti
>
> "SB" wrote:
> > Hi,
> > Is DT_STR Unicode? From SSIS I am using a data conversion component
> > and defining the data type as DT_STR and saving the output in excel
> > file. I am getting an error that 'can not convert from Unicode to non-
> > unicode'. I thought I have already taken care of that in data
> > conversion.- Hide quoted text -
> - Show quoted text -
Hi,
DT_STR should be an input field because I am getting data from a table
using ole db source.|||OK; supposing that input field is actually non-unicode (DT_STR could be the
right data type), verify the transformation task to be sure about the output
data type. SQL 2005 uses UNICODE by default, and you should explicitly
declare non unicode data types.
If you correct the input field definition specifying Unicode (DT_WSTR), you
should avoid such error message.
The fact that you are accessing input table via OLE DB does'nt change the
fact that QSL 2005 uses Unicode by default.
Gilberto Zampatti
"SB" wrote:
> On Apr 20, 2:10 pm, Gilberto Zampatti
> <GilbertoZampa...@.discussions.microsoft.com> wrote:
> > Could you explain exactly which data conversion you prepared? The DT_STR was
> > specified for the input field or for the output? In this last case, which is
> > the input field data type?
> > Gilberto Zampatti
> >
> >
> >
> > "SB" wrote:
> > > Hi,
> > > Is DT_STR Unicode? From SSIS I am using a data conversion component
> > > and defining the data type as DT_STR and saving the output in excel
> > > file. I am getting an error that 'can not convert from Unicode to non-
> > > unicode'. I thought I have already taken care of that in data
> > > conversion.- Hide quoted text -
> >
> > - Show quoted text -
> Hi,
> DT_STR should be an input field because I am getting data from a table
> using ole db source.
>|||On Apr 20, 3:28 pm, Gilberto Zampatti
<GilbertoZampa...@.discussions.microsoft.com> wrote:
> OK; supposing that input field is actually non-unicode (DT_STR could be the
> right data type), verify the transformation task to be sure about the output
> data type. SQL 2005 uses UNICODE by default, and you should explicitly
> declare non unicode data types.
> If you correct the input field definition specifying Unicode (DT_WSTR), you
> should avoid such error message.
> The fact that you are accessing input table via OLE DB does'nt change the
> fact that QSL 2005 uses Unicode by default.
> Gilberto Zampatti
>
> "SB" wrote:
> > On Apr 20, 2:10 pm, Gilberto Zampatti
> > <GilbertoZampa...@.discussions.microsoft.com> wrote:
> > > Could you explain exactly which data conversion you prepared? The DT_STR was
> > > specified for the input field or for the output? In this last case, which is
> > > the input field data type?
> > > Gilberto Zampatti
> > > "SB" wrote:
> > > > Hi,
> > > > Is DT_STR Unicode? From SSIS I am using a data conversion component
> > > > and defining the data type as DT_STR and saving the output in excel
> > > > file. I am getting an error that 'can not convert from Unicode to non-
> > > > unicode'. I thought I have already taken care of that in data
> > > > conversion.- Hide quoted text -
> > > - Show quoted text -
> > Hi,
> > DT_STR should be an input field because I am getting data from a table
> > using ole db source.- Hide quoted text -
> - Show quoted text -
Thanks.
For output I have created a excel table using the statement:
CREATE TABLE `Excel Destination` (
`NAME` VARCHAR(),
)
I have tried string, text etc but no success.
Excel Destination editor:
Data Access Mode:
Table or view
Name of the excel sheet:
Excel Destination|||On Apr 20, 3:28 pm, Gilberto Zampatti
<GilbertoZampa...@.discussions.microsoft.com> wrote:
> OK; supposing that input field is actually non-unicode(DT_STR could be the
> right data type), verify the transformation task to be sure about the output
> data type. SQL 2005 usesUNICODEby default, and you should explicitly
> declare nonunicodedata types.
> If you correct the input field definition specifyingUnicode(DT_WSTR), you
> should avoid such error message.
> The fact that you are accessing input table via OLE DB does'nt change the
> fact that QSL 2005 usesUnicodeby default.
> Gilberto Zampatti
>
> "SB" wrote:
> > On Apr 20, 2:10 pm, Gilberto Zampatti
> > <GilbertoZampa...@.discussions.microsoft.com> wrote:
> > > Could you explain exactly which data conversion you prepared? The DT_STR was
> > > specified for the input field or for the output? In this last case, which is
> > > the input field data type?
> > > Gilberto Zampatti
> > > "SB" wrote:
> > > > Hi,
> > > > Is DT_STRUnicode? From SSIS I am using a data conversion component
> > > > and defining the data type as DT_STR and saving the output in excel
> > > > file. I am getting an error that 'can not convert fromUnicodeto non-
> > > >unicode'. I thought I have already taken care of that in data
> > > > conversion.- Hide quoted text -
> > > - Show quoted text -
> > Hi,
> > DT_STR should be an input field because I am getting data from a table
> > using ole db source.- Hide quoted text -
> - Show quoted text -
Hi,
Is it alright if I declare a datatype as nvarchar 'create table (name
nvarchar(20))' and then treat it as if varchar for example functions,
inserts and join with other varchar columns etc? Except giving a
larger string size I don't have much use for unicode. They might as
well keep this type internal so that we didn't have to worry about it.|||On Apr 23, 10:41 am, SB <othell...@.yahoo.com> wrote:
> On Apr 20, 3:28 pm, Gilberto Zampatti
>
>
> <GilbertoZampa...@.discussions.microsoft.com> wrote:
> > OK; supposing that input field is actually non-unicode(DT_STR could be the
> > right data type), verify the transformation task to be sure about the output
> > data type. SQL 2005 usesUNICODEby default, and you should explicitly
> > declare nonunicodedata types.
> > If you correct the input field definition specifyingUnicode(DT_WSTR), you
> > should avoid such error message.
> > The fact that you are accessing input table via OLE DB does'nt change the
> > fact that QSL 2005 usesUnicodeby default.
> > Gilberto Zampatti
> > "SB" wrote:
> > > On Apr 20, 2:10 pm, Gilberto Zampatti
> > > <GilbertoZampa...@.discussions.microsoft.com> wrote:
> > > > Could you explain exactly which data conversion you prepared? The DT_STR was
> > > > specified for the input field or for the output? In this last case, which is
> > > > the input field data type?
> > > > Gilberto Zampatti
> > > > "SB" wrote:
> > > > > Hi,
> > > > > Is DT_STRUnicode? From SSIS I am using a data conversion component
> > > > > and defining the data type as DT_STR and saving the output in excel
> > > > > file. I am getting an error that 'can not convert fromUnicodeto non-
> > > > >unicode'. I thought I have already taken care of that in data
> > > > > conversion.- Hide quoted text -
> > > > - Show quoted text -
> > > Hi,
> > > DT_STR should be an input field because I am getting data from a table
> > > using ole db source.- Hide quoted text -
> > - Show quoted text -
> Hi,
> Is it alright if I declare a datatype as nvarchar 'create table (name
> nvarchar(20))' and then treat it as if varchar for example functions,
> inserts and join with other varchar columns etc? Except giving a
> larger string size I don't have much use for unicode. They might as
> well keep this type internal so that we didn't have to worry about it.- Hide quoted text -
> - Show quoted text -
That question was not related to SSIS package (as you have told ssis
is unicode). FWIW I was able to get the data (ssis) imported when I
used unicode for input and output data using a data conversion in
between from varchar to unicode string.

Friday, March 9, 2012

NON DOMAIN AND DOMAIN CONNECTION

Hi all,

it happen to me a strange problem:

i have a mdb file (in Access 2K) with SQL Server 2K linked tables who
runs on a workstation which is on a different domain that the SQL
Server. It works.

If i create a mdb file from a workstation which is a the domain of the
SQL Server and then i run it a my non-domain workstation i have error
message:

Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection

But if i reattached my tables it works.

If someone have an idea...

PS: same ODBC on both machinesRavieR (principle@.caramail.com) writes:
> it happen to me a strange problem:
> i have a mdb file (in Access 2K) with SQL Server 2K linked tables who
> runs on a workstation which is on a different domain that the SQL
> Server. It works.
> If i create a mdb file from a workstation which is a the domain of the
> SQL Server and then i run it a my non-domain workstation i have error
> message:
> Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL Server connection

I'm nor sure that I followed the confiuguration exactly, but trusted
connections in workgroups is usually an iffy thing. For instance, at
home I have a non-domain workstation, on which I run a non-domain
virtual machine where I have the beta version of SQL 2005. From the
host machine I cannot conenct with trusted connection to SQL2005 on
the virtual machine, but not the other way round.

I think you need to be logged with the same username on both, and the
two users need to have the same password.

You may be better off with SQL authentication in this case.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Wednesday, March 7, 2012

Noise File.

After changing a noise file - does the FTS have to be restarted?
Also, any way to determine which noise.eng file is being used? There
are several locations...
On Apr 16, 3:41 pm, "AF" <af.at.w...@.gmail.com> wrote:
> After changing a noise file - does the FTS have to be restarted?
> Also, any way to determine which noise.eng file is being used? There
> are several locations...
It looks like C:\Program Files\Common Files\System\MSSearch\Data\Config
\noise.enu is the file used... *but* this is in a clustered
environment... how would this noise file get to the other server?
|||The path should be X:\Program Files\Microsoft SQL
Server\MSSQL$instancename\MSSQL\FTData\Server\Conf ig, IIRC
"AF" <af.at.work@.gmail.com> wrote in message
news:1176753798.884846.13040@.q75g2000hsh.googlegro ups.com...
> On Apr 16, 3:41 pm, "AF" <af.at.w...@.gmail.com> wrote:
> It looks like C:\Program Files\Common Files\System\MSSearch\Data\Config
> \noise.enu is the file used... *but* this is in a clustered
> environment... how would this noise file get to the other server?
>
|||On Apr 18, 10:05 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:[vbcol=seagreen]
> The path should be X:\Program Files\Microsoft SQL
> Server\MSSQL$instancename\MSSQL\FTData\Server\Conf ig, IIRC"AF" <af.at.w...@.gmail.com> wrote in message
> news:1176753798.884846.13040@.q75g2000hsh.googlegro ups.com...
>
OK... how can I change that?