Tuesday, March 27, 2012
Cleanup Task / xp_delete_file
I found some posts but not really a solution. Environment: SQL 2005 EE, SP1,
english version but german regional settings
The following code does nothing in the file system, but allways states
success:
EXECUTE master.dbo.xp_delete_file 0,N'D:\test\',N'.bak',N'06/03/2006 15:06:2
9'
nor does it work with 'bak" ,'trn, '*.trn' or '*.*' or the seeting to
include subfolders.
Any ideas ?
MichaelOne problem is that xp_delete_file belongs to the sys schema
not the dbo schema.
-Sue
On Tue, 6 Jun 2006 06:17:01 -0700, Michael Roedeske
<MichaelRoedeske@.discussions.microsoft.com> wrote:
>Hello together,
>I found some posts but not really a solution. Environment: SQL 2005 EE, SP1
,
>english version but german regional settings
>The following code does nothing in the file system, but allways states
>success:
>EXECUTE master.dbo.xp_delete_file 0,N'D:\test',N'.bak',N'06/03/2006 15:06:
29'
>nor does it work with 'bak" ,'trn, '*.trn' or '*.*' or the seeting to
>include subfolders.
>Any ideas ?
>Michael
>|||Dear Sue,
even when I call the sp with the sys schema it happes nothing in the
filesystem.
Any other idea?
Regards
Michael
"Sue Hoegemeier" wrote:
> One problem is that xp_delete_file belongs to the sys schema
> not the dbo schema.
> -Sue
> On Tue, 6 Jun 2006 06:17:01 -0700, Michael Roedeske
> <MichaelRoedeske@.discussions.microsoft.com> wrote:
>
>|||Others have had the same issue - and others do not. I
haven't seen anyone post what solved the issue.
Try removing the dot from the extension - for example have
it list as just BAK without the dot before BAK. Make sure
the extension is exactly what you are using for your
backups.
It was suppose to be fixed in SP1 but you may also want to
try creating a cleanup task for each subdirectory.
People sometimes spend too much time troubleshooting
maintenance plans when they can just write scripts that have
more flexibility in less time then they spend addressing
maintenance plan issue.
-Sue
On Wed, 7 Jun 2006 01:06:02 -0700, Michael Roedeske
<MichaelRoedeske@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Dear Sue,
>even when I call the sp with the sys schema it happes nothing in the
>filesystem.
>Any other idea?
>Regards
>Michael
>"Sue Hoegemeier" wrote:
>sqlsql
Cleanup Task / xp_delete_file
I found some posts but not really a solution. Environment: SQL 2005 EE, SP1,
english version but german regional settings
The following code does nothing in the file system, but allways states
success:
EXECUTE master.dbo.xp_delete_file 0,N'D:\test\',N'.bak',N'06/03/2006 15:06:29'
nor does it work with 'bak" ,'trn, '*.trn' or '*.*' or the seeting to
include subfolders.
Any ideas ?
MichaelOne problem is that xp_delete_file belongs to the sys schema
not the dbo schema.
-Sue
On Tue, 6 Jun 2006 06:17:01 -0700, Michael Roedeske
<MichaelRoedeske@.discussions.microsoft.com> wrote:
>Hello together,
>I found some posts but not really a solution. Environment: SQL 2005 EE, SP1,
>english version but german regional settings
>The following code does nothing in the file system, but allways states
>success:
>EXECUTE master.dbo.xp_delete_file 0,N'D:\test\',N'.bak',N'06/03/2006 15:06:29'
>nor does it work with 'bak" ,'trn, '*.trn' or '*.*' or the seeting to
>include subfolders.
>Any ideas ?
>Michael
>|||Dear Sue,
even when I call the sp with the sys schema it happes nothing in the
filesystem.
Any other idea?
Regards
Michael
"Sue Hoegemeier" wrote:
> One problem is that xp_delete_file belongs to the sys schema
> not the dbo schema.
> -Sue
> On Tue, 6 Jun 2006 06:17:01 -0700, Michael Roedeske
> <MichaelRoedeske@.discussions.microsoft.com> wrote:
> >Hello together,
> >
> >I found some posts but not really a solution. Environment: SQL 2005 EE, SP1,
> >english version but german regional settings
> >
> >The following code does nothing in the file system, but allways states
> >success:
> >
> >EXECUTE master.dbo.xp_delete_file 0,N'D:\test\',N'.bak',N'06/03/2006 15:06:29'
> >
> >nor does it work with 'bak" ,'trn, '*.trn' or '*.*' or the seeting to
> >include subfolders.
> >
> >Any ideas ?
> >
> >Michael
> >
>|||Others have had the same issue - and others do not. I
haven't seen anyone post what solved the issue.
Try removing the dot from the extension - for example have
it list as just BAK without the dot before BAK. Make sure
the extension is exactly what you are using for your
backups.
It was suppose to be fixed in SP1 but you may also want to
try creating a cleanup task for each subdirectory.
People sometimes spend too much time troubleshooting
maintenance plans when they can just write scripts that have
more flexibility in less time then they spend addressing
maintenance plan issue.
-Sue
On Wed, 7 Jun 2006 01:06:02 -0700, Michael Roedeske
<MichaelRoedeske@.discussions.microsoft.com> wrote:
>Dear Sue,
>even when I call the sp with the sys schema it happes nothing in the
>filesystem.
>Any other idea?
>Regards
>Michael
>"Sue Hoegemeier" wrote:
>> One problem is that xp_delete_file belongs to the sys schema
>> not the dbo schema.
>> -Sue
>> On Tue, 6 Jun 2006 06:17:01 -0700, Michael Roedeske
>> <MichaelRoedeske@.discussions.microsoft.com> wrote:
>> >Hello together,
>> >
>> >I found some posts but not really a solution. Environment: SQL 2005 EE, SP1,
>> >english version but german regional settings
>> >
>> >The following code does nothing in the file system, but allways states
>> >success:
>> >
>> >EXECUTE master.dbo.xp_delete_file 0,N'D:\test\',N'.bak',N'06/03/2006 15:06:29'
>> >
>> >nor does it work with 'bak" ,'trn, '*.trn' or '*.*' or the seeting to
>> >include subfolders.
>> >
>> >Any ideas ?
>> >
>> >Michael
>> >
>>
Sunday, March 11, 2012
chinese localization of english software suite
Our company is planning a project to localise our current software suite for
chinese market. As a SQL DBA, I would like to get more information of what
is involved from database admin and development perspective. I would
appreciate any help, artical links and/or materials links etc. Thanks.
I'm interested in this too. I would guess that you need Chinese locale,
collation etc. for the specific database.
Tables would be able to store Chinese characters. Developing programs may
still use English.
"flologic" <flo@.flo.net> wrote in message
news:%23bdrZYqlEHA.1244@.TK2MSFTNGP15.phx.gbl...
> Hi,
> Our company is planning a project to localise our current software suite
for
> chinese market. As a SQL DBA, I would like to get more information of what
> is involved from database admin and development perspective. I would
> appreciate any help, artical links and/or materials links etc. Thanks.
>
|||Here are some good article you can start with
http://msdn.microsoft.com/library/de...server2000.asp
http://www.microsoft.com/globaldev/g...s/wrguide.mspx
http://msdn.microsoft.com/library/de...plications.asp
Wei Xiao [MSFT]
SQL Server Storage Engine Development
This posting is provided "AS IS" with no warranties, and confers no rights.
"Richard Ding" <rding@.acadian-asset.com> wrote in message
news:u$eSew0lEHA.2380@.TK2MSFTNGP14.phx.gbl...
> I'm interested in this too. I would guess that you need Chinese locale,
> collation etc. for the specific database.
> Tables would be able to store Chinese characters. Developing programs may
> still use English.
>
> "flologic" <flo@.flo.net> wrote in message
> news:%23bdrZYqlEHA.1244@.TK2MSFTNGP15.phx.gbl...
> for
>
chinese localization of english software suite
Our company is planning a project to localise our current software suite for
chinese market. As a SQL DBA, I would like to get more information of what
is involved from database admin and development perspective. I would
appreciate any help, artical links and/or materials links etc. Thanks.I'm interested in this too. I would guess that you need Chinese locale,
collation etc. for the specific database.
Tables would be able to store Chinese characters. Developing programs may
still use English.
"flologic" <flo@.flo.net> wrote in message
news:%23bdrZYqlEHA.1244@.TK2MSFTNGP15.phx.gbl...
> Hi,
> Our company is planning a project to localise our current software suite
for
> chinese market. As a SQL DBA, I would like to get more information of what
> is involved from database admin and development perspective. I would
> appreciate any help, artical links and/or materials links etc. Thanks.
>|||Here are some good article you can start with
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/intlfeaturesinsqlserver2000.asp
http://www.microsoft.com/globaldev/getWR/steps/wrguide.mspx
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpcondesigningglobalapplications.asp
Wei Xiao [MSFT]
SQL Server Storage Engine Development
This posting is provided "AS IS" with no warranties, and confers no rights.
"Richard Ding" <rding@.acadian-asset.com> wrote in message
news:u$eSew0lEHA.2380@.TK2MSFTNGP14.phx.gbl...
> I'm interested in this too. I would guess that you need Chinese locale,
> collation etc. for the specific database.
> Tables would be able to store Chinese characters. Developing programs may
> still use English.
>
> "flologic" <flo@.flo.net> wrote in message
> news:%23bdrZYqlEHA.1244@.TK2MSFTNGP15.phx.gbl...
>> Hi,
>> Our company is planning a project to localise our current software suite
> for
>> chinese market. As a SQL DBA, I would like to get more information of
>> what
>> is involved from database admin and development perspective. I would
>> appreciate any help, artical links and/or materials links etc. Thanks.
>>
>
Chinese garbled in MSSQL2000 - by ASP
Hi experts,
Here I got some problems with my application. (ASP & English Version SQL Server 2000)
As we are using English MSSQL Server 2000, we got some new functions and we have to facilitate support of Chinese characters in the DB. I have set the collation for those Chinese fields already and those queries or Stored Procs for Chinese are working fine, ONLY if I execute them in Enterprise Manager. Chinese characters can be displayed in the relevant tables.
However here comes the big problem and I got really frustrated. As we will provide user interface in ASP pages, we 'll let users to insert the information which will be sent to the DB. If there's Chinese characters in the query string, the Chinese characters added in the DB would be garbled.
e.g. EXECUTE proc_TestChinese 'XYZ', 'test123' (assume XYZ be those Chinese words)
I am wondering if there's any way I can solve this problem. Should I add special handling for these Chinese words? I have set the ASP pages in UTF-8 or Big5 encoding but it doesn't help. Hope you experts can show me the way out of the mess. Thanks in advance!
Manfred
Is your input variabl for the stored procedure a NVARCHAR or any other unicode data type, if not the data will be converted, leading to the problems you described. if you are fine on the database side you should consider posting some code in here which is used for getting the data in the database using ASP Code.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Hi Jens,
For that particular field for storing Chinese characters, I have set it as nvarchar already with collation settting as Chinese_Taiwan_Stroke_BIN. Here below is the Stored Procedure for testing.
Thanks in advance!
Manfred
to insert the Chinese characters for Germany: 德國 (德國)
use N'xxxx' for nvarchar
EXECUTE proc_TestChinese N'德國', 'Germany'
CREATE Procedure dbo.proc_TestChinese
@.chineseCharacters nvarchar(20),
@.Description varchar(50)
AS
BEGIN
INSERT INTO dbo.tblTestChinese
VALUES(@.chineseCharacters, @.Description)
END
GO
After the SP is executed, the table would shown as ?w°ê for those Chinese characters.
If I have a html file, see http://www.neocollage.com/de.htm . If you change the encoding to Western European then you 'll see the garbled text as in the DB.