Hi,
I'm trying to localize Report Manager (Reporting Services 2005) by
implementing my own Finnish version of the resources in
ReportingServicesWebUserInterface.dll assembly.
I have the satellite assembly in the following folder:
C:\Program Files\Microsoft SQL Server\MSSQL.6\Reporting
Services\ReportManager\Bin\fi
I used the Assembly Linker tool (al) to create the assembly and used the
ReportingServicesWebUserInterface.dll in the base directory as the template.
I tried delay signing the assembly using my own key. Then I used the Strong
Name
Utility (sn) to add the assembly to skip verification list.
For some reason my satellite assembly is not loaded when I set my web
browser language to Finnish. If I set it to German it works ok. I have very
little .NET experience by I suspect that is due to the fact that the
sattelite assembly should be signed with the same key as the base assembly?
So is it possible to implement your own language version of the
ReportingServicesWebUserInterface.dll satellite assembly to use it to
localize report manager?
If it is possible is there any document that describes the process and the
related security issues?
If it's not possible then please tell me so that I can make a decision about
developing a new report portal web application. We would like to use the
Report Manager if we only could localize it.
I tried emailing the Gold Certified Partner support address, but got no
answer. Any assitance will be greatly appreciated.
Thank you,
Juho Salo> I tried emailing the Gold Certified Partner support address, but got no
> answer.
Scractch that. They actually called me instead of emailing, but my phone was
not on, stupid I know. I will post the answer here when I get it.
Juho|||I have received a very decisive answer from Microsoft.
Quote:
"You have asked if it is possible to implement your own language version of
the ReportingServicesWebUserInterface.dll satellite assembly to use it to
localize report manager. Unfortunately, this is NOT possible. The Report
Manager resource assemblies MUST be signed with a Microsoft key."
So if anyone else is wondering, if you need to localize Report Manager
easily it's not possible (unless ofcourse you live in one of those
priviledged countries that are provided with localization for it).
I'm off to writing my own report portal application then.|||I actually came up with a solution that is a bit of a hack but will do nicely
and let's me use the Report Manager. Just add the code below to all of the
aspx pages under the Report Manager\Pages folder
<script language=cs runat=server src= "Dictionary.cs"/>
<script language="C#" runat="server">
void Page_LoadComplete(object sender, EventArgs e) {
TranslateControls(Page);
}
private void TranslateControls(Control c)
{
Type t = c.GetType();
System.Reflection.PropertyInfo p = t.GetProperty("Text");
string s;
if (p != null) {
s = (string) p.GetValue(c, null);
if (s!= null ) {
if (s.Length > 0 ) {
if (p.CanWrite)
{
p.SetValue(c, Dictionary.Translate((string) p.GetValue(c, null)), null);
}
}
}
}
foreach (Control child in c.Controls)
{
TranslateControls(child);
}
}
</script>
Then just create some sort of implementation for the Dictionary class in the
Dictionary.cs file. The code above is not the final version but it works.
Comments are welcome.
Showing posts with label version. Show all posts
Showing posts with label version. Show all posts
Wednesday, March 28, 2012
Is it possible to load such XML file using SQLXML BulkLoad?
Hello
I have an XML file:
<?xml version="1.0" encoding="UTF-8"?>
<root>
<Item>
<ItemID>1</ItemID>
<Property1>...</Property1>
<Property2>...</Property2>
<Property3>...</Property3>
</Item>
<Item>
<ItemID>2</ItemID>
<Property1>...</Property1>
<Property2>...</Property2>
<Property3>...</Property3>
<Property4>...</Property3>
..
</Item>
...
</root>
Number of properties for <Item> is not fixed and their names also not
defined (except ItemID). Is it possible to create XSD schema for
importing this into table using SQLXML BulkLoad facility?
Table:
ItemID PropertyName PropertyValue
=================================
1 Property1 ...
1 Property2 ...
1 Property3 ...
2 Property1 ...
2 Property2 ...
2 Property3 ...
2 Property4 ...
...
Thank you
Martin Rakhmanov
jimmers@.yandex.ruYou cannot map names of elements into data using the schema mapping. You
need to use OpenXML for such mappings.
HTH
Michael
"jimmers" <jimmers@.yandex.ru> wrote in message
news:b0ede647.0501200116.5025661d@.posting.google.com...
> Hello
> I have an XML file:
> <?xml version="1.0" encoding="UTF-8"?>
> <root>
> <Item>
> <ItemID>1</ItemID>
> <Property1>...</Property1>
> <Property2>...</Property2>
> <Property3>...</Property3>
> </Item>
> <Item>
> <ItemID>2</ItemID>
> <Property1>...</Property1>
> <Property2>...</Property2>
> <Property3>...</Property3>
> <Property4>...</Property3>
> ...
> </Item>
> ...
> </root>
> Number of properties for <Item> is not fixed and their names also not
> defined (except ItemID). Is it possible to create XSD schema for
> importing this into table using SQLXML BulkLoad facility?
> Table:
> ItemID PropertyName PropertyValue
> =================================
> 1 Property1 ...
> 1 Property2 ...
> 1 Property3 ...
> 2 Property1 ...
> 2 Property2 ...
> 2 Property3 ...
> 2 Property4 ...
> ...
>
> Thank you
> Martin Rakhmanov
> jimmers@.yandex.ru|||No, not this exact data file can be mapped using XSD schema. Use XSLT to
transform this data file to look something like, .
<?xml version="1.0" encoding="UTF-8"?>
<root>
<Item>
<ItemID>1</ItemID>
<Property><Name>Property1</Name><Value>...</Value></Property>
<Property><Name>Property2</Name><Value>...</Value></Property>
<Property><Name>Property3</Name><Value>...</Value></Property>
</Item>
HTH,
Chandra
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
news:ekbVtMv$EHA.1188@.tk2msftngp13.phx.gbl...
> You cannot map names of elements into data using the schema mapping. You
> need to use OpenXML for such mappings.
> HTH
> Michael
> "jimmers" <jimmers@.yandex.ru> wrote in message
> news:b0ede647.0501200116.5025661d@.posting.google.com...
>|||Hello Michael and Chandra
First of all, thank you for prompt responses.
Unfortunately I cannot do XSLT transformation because input file size is
huge (~300 Mb): I made test with .NET XslTransform class on 100 Mb XML input
file and simple XSLT file. The program executed approximately 10 minutes and
then out-of-memory exception was thrown. On disk I got incomplete 42 Mb
result file. The server has 512 Mb memory, P4 2.8 GHz CPU and runs under
Windows 2003 Server Standard Edition.
Right now I stick with the following solution: console application reads
elements from input file with help of XmlTextReader class until size
threshold is reached and saves them in temporary files. Then each resulting
file contents is passed to stored procedure that utilized OPENXML. In other
words, I had to duplicate SQLXMLBulkLoad functionality in Transactional mode
and then use OPENXML feature.
By the way, what is the meaning of HTH signature?
Thank you
Martin Rakhmanov
jimmers@.yandex.ru
"Chandra Kalyanaraman [MSFT]" wrote:
> No, not this exact data file can be mapped using XSD schema. Use XSLT to
> transform this data file to look something like, .
> <?xml version="1.0" encoding="UTF-8"?>
> <root>
> <Item>
> <ItemID>1</ItemID>
> <Property><Name>Property1</Name><Value>...</Value></Property>
> <Property><Name>Property2</Name><Value>...</Value></Property>
> <Property><Name>Property3</Name><Value>...</Value></Property>
> </Item>
> HTH,
> Chandra
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
> news:ekbVtMv$EHA.1188@.tk2msftngp13.phx.gbl...
>
>|||Hi Martin.
300MB XML file: What on earth do you have in that? :-) XML files should be
kept as small as possible and not be used as a "database replacement". :-)
HTH means: Hope This Helps
Best regards
Michael
"jimmers" <jimmers@.discussions.microsoft.com> wrote in message
news:214EF7CD-F4BB-4E5A-AD6C-1A57CFA00C12@.microsoft.com...
> Hello Michael and Chandra
> First of all, thank you for prompt responses.
> Unfortunately I cannot do XSLT transformation because input file size is
> huge (~300 Mb): I made test with .NET XslTransform class on 100 Mb XML
> input
> file and simple XSLT file. The program executed approximately 10 minutes
> and
> then out-of-memory exception was thrown. On disk I got incomplete 42 Mb
> result file. The server has 512 Mb memory, P4 2.8 GHz CPU and runs under
> Windows 2003 Server Standard Edition.
> Right now I stick with the following solution: console application reads
> elements from input file with help of XmlTextReader class until size
> threshold is reached and saves them in temporary files. Then each
> resulting
> file contents is passed to stored procedure that utilized OPENXML. In
> other
> words, I had to duplicate SQLXMLBulkLoad functionality in Transactional
> mode
> and then use OPENXML feature.
> By the way, what is the meaning of HTH signature?
> Thank you
> Martin Rakhmanov
> jimmers@.yandex.ru
>
> "Chandra Kalyanaraman [MSFT]" wrote:
>|||300 Mb XML file is maximum size, normally it will be about 100 Mb. It is
generated by external system and I cannot affect this unfortunately.
Thank you
Martin
"Michael Rys [MSFT]" wrote:
> Hi Martin.
> 300MB XML file: What on earth do you have in that? :-) XML files should be
> kept as small as possible and not be used as a "database replacement". :-)
> HTH means: Hope This Helps
> Best regards
> Michael
> "jimmers" <jimmers@.discussions.microsoft.com> wrote in message
> news:214EF7CD-F4BB-4E5A-AD6C-1A57CFA00C12@.microsoft.com...
>
>sql
I have an XML file:
<?xml version="1.0" encoding="UTF-8"?>
<root>
<Item>
<ItemID>1</ItemID>
<Property1>...</Property1>
<Property2>...</Property2>
<Property3>...</Property3>
</Item>
<Item>
<ItemID>2</ItemID>
<Property1>...</Property1>
<Property2>...</Property2>
<Property3>...</Property3>
<Property4>...</Property3>
..
</Item>
...
</root>
Number of properties for <Item> is not fixed and their names also not
defined (except ItemID). Is it possible to create XSD schema for
importing this into table using SQLXML BulkLoad facility?
Table:
ItemID PropertyName PropertyValue
=================================
1 Property1 ...
1 Property2 ...
1 Property3 ...
2 Property1 ...
2 Property2 ...
2 Property3 ...
2 Property4 ...
...
Thank you
Martin Rakhmanov
jimmers@.yandex.ruYou cannot map names of elements into data using the schema mapping. You
need to use OpenXML for such mappings.
HTH
Michael
"jimmers" <jimmers@.yandex.ru> wrote in message
news:b0ede647.0501200116.5025661d@.posting.google.com...
> Hello
> I have an XML file:
> <?xml version="1.0" encoding="UTF-8"?>
> <root>
> <Item>
> <ItemID>1</ItemID>
> <Property1>...</Property1>
> <Property2>...</Property2>
> <Property3>...</Property3>
> </Item>
> <Item>
> <ItemID>2</ItemID>
> <Property1>...</Property1>
> <Property2>...</Property2>
> <Property3>...</Property3>
> <Property4>...</Property3>
> ...
> </Item>
> ...
> </root>
> Number of properties for <Item> is not fixed and their names also not
> defined (except ItemID). Is it possible to create XSD schema for
> importing this into table using SQLXML BulkLoad facility?
> Table:
> ItemID PropertyName PropertyValue
> =================================
> 1 Property1 ...
> 1 Property2 ...
> 1 Property3 ...
> 2 Property1 ...
> 2 Property2 ...
> 2 Property3 ...
> 2 Property4 ...
> ...
>
> Thank you
> Martin Rakhmanov
> jimmers@.yandex.ru|||No, not this exact data file can be mapped using XSD schema. Use XSLT to
transform this data file to look something like, .
<?xml version="1.0" encoding="UTF-8"?>
<root>
<Item>
<ItemID>1</ItemID>
<Property><Name>Property1</Name><Value>...</Value></Property>
<Property><Name>Property2</Name><Value>...</Value></Property>
<Property><Name>Property3</Name><Value>...</Value></Property>
</Item>
HTH,
Chandra
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
news:ekbVtMv$EHA.1188@.tk2msftngp13.phx.gbl...
> You cannot map names of elements into data using the schema mapping. You
> need to use OpenXML for such mappings.
> HTH
> Michael
> "jimmers" <jimmers@.yandex.ru> wrote in message
> news:b0ede647.0501200116.5025661d@.posting.google.com...
>|||Hello Michael and Chandra
First of all, thank you for prompt responses.
Unfortunately I cannot do XSLT transformation because input file size is
huge (~300 Mb): I made test with .NET XslTransform class on 100 Mb XML input
file and simple XSLT file. The program executed approximately 10 minutes and
then out-of-memory exception was thrown. On disk I got incomplete 42 Mb
result file. The server has 512 Mb memory, P4 2.8 GHz CPU and runs under
Windows 2003 Server Standard Edition.
Right now I stick with the following solution: console application reads
elements from input file with help of XmlTextReader class until size
threshold is reached and saves them in temporary files. Then each resulting
file contents is passed to stored procedure that utilized OPENXML. In other
words, I had to duplicate SQLXMLBulkLoad functionality in Transactional mode
and then use OPENXML feature.
By the way, what is the meaning of HTH signature?
Thank you
Martin Rakhmanov
jimmers@.yandex.ru
"Chandra Kalyanaraman [MSFT]" wrote:
> No, not this exact data file can be mapped using XSD schema. Use XSLT to
> transform this data file to look something like, .
> <?xml version="1.0" encoding="UTF-8"?>
> <root>
> <Item>
> <ItemID>1</ItemID>
> <Property><Name>Property1</Name><Value>...</Value></Property>
> <Property><Name>Property2</Name><Value>...</Value></Property>
> <Property><Name>Property3</Name><Value>...</Value></Property>
> </Item>
> HTH,
> Chandra
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
> news:ekbVtMv$EHA.1188@.tk2msftngp13.phx.gbl...
>
>|||Hi Martin.
300MB XML file: What on earth do you have in that? :-) XML files should be
kept as small as possible and not be used as a "database replacement". :-)
HTH means: Hope This Helps
Best regards
Michael
"jimmers" <jimmers@.discussions.microsoft.com> wrote in message
news:214EF7CD-F4BB-4E5A-AD6C-1A57CFA00C12@.microsoft.com...
> Hello Michael and Chandra
> First of all, thank you for prompt responses.
> Unfortunately I cannot do XSLT transformation because input file size is
> huge (~300 Mb): I made test with .NET XslTransform class on 100 Mb XML
> input
> file and simple XSLT file. The program executed approximately 10 minutes
> and
> then out-of-memory exception was thrown. On disk I got incomplete 42 Mb
> result file. The server has 512 Mb memory, P4 2.8 GHz CPU and runs under
> Windows 2003 Server Standard Edition.
> Right now I stick with the following solution: console application reads
> elements from input file with help of XmlTextReader class until size
> threshold is reached and saves them in temporary files. Then each
> resulting
> file contents is passed to stored procedure that utilized OPENXML. In
> other
> words, I had to duplicate SQLXMLBulkLoad functionality in Transactional
> mode
> and then use OPENXML feature.
> By the way, what is the meaning of HTH signature?
> Thank you
> Martin Rakhmanov
> jimmers@.yandex.ru
>
> "Chandra Kalyanaraman [MSFT]" wrote:
>|||300 Mb XML file is maximum size, normally it will be about 100 Mb. It is
generated by external system and I cannot affect this unfortunately.
Thank you
Martin
"Michael Rys [MSFT]" wrote:
> Hi Martin.
> 300MB XML file: What on earth do you have in that? :-) XML files should be
> kept as small as possible and not be used as a "database replacement". :-)
> HTH means: Hope This Helps
> Best regards
> Michael
> "jimmers" <jimmers@.discussions.microsoft.com> wrote in message
> news:214EF7CD-F4BB-4E5A-AD6C-1A57CFA00C12@.microsoft.com...
>
>sql
Is it possible to load such XML file using SQLXML BulkLoad?
Hello
I have an XML file:
<?xml version="1.0" encoding="UTF-8"?>
<root>
<Item>
<ItemID>1</ItemID>
<Property1>...</Property1>
<Property2>...</Property2>
<Property3>...</Property3>
</Item>
<Item>
<ItemID>2</ItemID>
<Property1>...</Property1>
<Property2>...</Property2>
<Property3>...</Property3>
<Property4>...</Property3>
...
</Item>
...
</root>
Number of properties for <Item> is not fixed and their names also not
defined (except ItemID). Is it possible to create XSD schema for
importing this into table using SQLXML BulkLoad facility?
Table:
ItemID PropertyName PropertyValue
=================================
1 Property1 ...
1 Property2 ...
1 Property3 ...
2 Property1 ...
2 Property2 ...
2 Property3 ...
2 Property4 ...
...
Thank you
Martin Rakhmanov
jimmers@.yandex.ru
You cannot map names of elements into data using the schema mapping. You
need to use OpenXML for such mappings.
HTH
Michael
"jimmers" <jimmers@.yandex.ru> wrote in message
news:b0ede647.0501200116.5025661d@.posting.google.c om...
> Hello
> I have an XML file:
> <?xml version="1.0" encoding="UTF-8"?>
> <root>
> <Item>
> <ItemID>1</ItemID>
> <Property1>...</Property1>
> <Property2>...</Property2>
> <Property3>...</Property3>
> </Item>
> <Item>
> <ItemID>2</ItemID>
> <Property1>...</Property1>
> <Property2>...</Property2>
> <Property3>...</Property3>
> <Property4>...</Property3>
> ...
> </Item>
> ...
> </root>
> Number of properties for <Item> is not fixed and their names also not
> defined (except ItemID). Is it possible to create XSD schema for
> importing this into table using SQLXML BulkLoad facility?
> Table:
> ItemID PropertyName PropertyValue
> =================================
> 1 Property1 ...
> 1 Property2 ...
> 1 Property3 ...
> 2 Property1 ...
> 2 Property2 ...
> 2 Property3 ...
> 2 Property4 ...
> ...
>
> Thank you
> Martin Rakhmanov
> jimmers@.yandex.ru
|||No, not this exact data file can be mapped using XSD schema. Use XSLT to
transform this data file to look something like, .
<?xml version="1.0" encoding="UTF-8"?>
<root>
<Item>
<ItemID>1</ItemID>
<Property><Name>Property1</Name><Value>...</Value></Property>
<Property><Name>Property2</Name><Value>...</Value></Property>
<Property><Name>Property3</Name><Value>...</Value></Property>
</Item>
HTH,
Chandra
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
news:ekbVtMv$EHA.1188@.tk2msftngp13.phx.gbl...
> You cannot map names of elements into data using the schema mapping. You
> need to use OpenXML for such mappings.
> HTH
> Michael
> "jimmers" <jimmers@.yandex.ru> wrote in message
> news:b0ede647.0501200116.5025661d@.posting.google.c om...
>
|||Hello Michael and Chandra
First of all, thank you for prompt responses.
Unfortunately I cannot do XSLT transformation because input file size is
huge (~300 Mb): I made test with .NET XslTransform class on 100 Mb XML input
file and simple XSLT file. The program executed approximately 10 minutes and
then out-of-memory exception was thrown. On disk I got incomplete 42 Mb
result file. The server has 512 Mb memory, P4 2.8 GHz CPU and runs under
Windows 2003 Server Standard Edition.
Right now I stick with the following solution: console application reads
elements from input file with help of XmlTextReader class until size
threshold is reached and saves them in temporary files. Then each resulting
file contents is passed to stored procedure that utilized OPENXML. In other
words, I had to duplicate SQLXMLBulkLoad functionality in Transactional mode
and then use OPENXML feature.
By the way, what is the meaning of HTH signature?
Thank you
Martin Rakhmanov
jimmers@.yandex.ru
"Chandra Kalyanaraman [MSFT]" wrote:
> No, not this exact data file can be mapped using XSD schema. Use XSLT to
> transform this data file to look something like, .
> <?xml version="1.0" encoding="UTF-8"?>
> <root>
> <Item>
> <ItemID>1</ItemID>
> <Property><Name>Property1</Name><Value>...</Value></Property>
> <Property><Name>Property2</Name><Value>...</Value></Property>
> <Property><Name>Property3</Name><Value>...</Value></Property>
> </Item>
> HTH,
> Chandra
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
> news:ekbVtMv$EHA.1188@.tk2msftngp13.phx.gbl...
>
>
|||Hi Martin.
300MB XML file: What on earth do you have in that? :-) XML files should be
kept as small as possible and not be used as a "database replacement". :-)
HTH means: Hope This Helps
Best regards
Michael
"jimmers" <jimmers@.discussions.microsoft.com> wrote in message
news:214EF7CD-F4BB-4E5A-AD6C-1A57CFA00C12@.microsoft.com...[vbcol=seagreen]
> Hello Michael and Chandra
> First of all, thank you for prompt responses.
> Unfortunately I cannot do XSLT transformation because input file size is
> huge (~300 Mb): I made test with .NET XslTransform class on 100 Mb XML
> input
> file and simple XSLT file. The program executed approximately 10 minutes
> and
> then out-of-memory exception was thrown. On disk I got incomplete 42 Mb
> result file. The server has 512 Mb memory, P4 2.8 GHz CPU and runs under
> Windows 2003 Server Standard Edition.
> Right now I stick with the following solution: console application reads
> elements from input file with help of XmlTextReader class until size
> threshold is reached and saves them in temporary files. Then each
> resulting
> file contents is passed to stored procedure that utilized OPENXML. In
> other
> words, I had to duplicate SQLXMLBulkLoad functionality in Transactional
> mode
> and then use OPENXML feature.
> By the way, what is the meaning of HTH signature?
> Thank you
> Martin Rakhmanov
> jimmers@.yandex.ru
>
> "Chandra Kalyanaraman [MSFT]" wrote:
|||300 Mb XML file is maximum size, normally it will be about 100 Mb. It is
generated by external system and I cannot affect this unfortunately.
Thank you
Martin
"Michael Rys [MSFT]" wrote:
> Hi Martin.
> 300MB XML file: What on earth do you have in that? :-) XML files should be
> kept as small as possible and not be used as a "database replacement". :-)
> HTH means: Hope This Helps
> Best regards
> Michael
> "jimmers" <jimmers@.discussions.microsoft.com> wrote in message
> news:214EF7CD-F4BB-4E5A-AD6C-1A57CFA00C12@.microsoft.com...
>
>
I have an XML file:
<?xml version="1.0" encoding="UTF-8"?>
<root>
<Item>
<ItemID>1</ItemID>
<Property1>...</Property1>
<Property2>...</Property2>
<Property3>...</Property3>
</Item>
<Item>
<ItemID>2</ItemID>
<Property1>...</Property1>
<Property2>...</Property2>
<Property3>...</Property3>
<Property4>...</Property3>
...
</Item>
...
</root>
Number of properties for <Item> is not fixed and their names also not
defined (except ItemID). Is it possible to create XSD schema for
importing this into table using SQLXML BulkLoad facility?
Table:
ItemID PropertyName PropertyValue
=================================
1 Property1 ...
1 Property2 ...
1 Property3 ...
2 Property1 ...
2 Property2 ...
2 Property3 ...
2 Property4 ...
...
Thank you
Martin Rakhmanov
jimmers@.yandex.ru
You cannot map names of elements into data using the schema mapping. You
need to use OpenXML for such mappings.
HTH
Michael
"jimmers" <jimmers@.yandex.ru> wrote in message
news:b0ede647.0501200116.5025661d@.posting.google.c om...
> Hello
> I have an XML file:
> <?xml version="1.0" encoding="UTF-8"?>
> <root>
> <Item>
> <ItemID>1</ItemID>
> <Property1>...</Property1>
> <Property2>...</Property2>
> <Property3>...</Property3>
> </Item>
> <Item>
> <ItemID>2</ItemID>
> <Property1>...</Property1>
> <Property2>...</Property2>
> <Property3>...</Property3>
> <Property4>...</Property3>
> ...
> </Item>
> ...
> </root>
> Number of properties for <Item> is not fixed and their names also not
> defined (except ItemID). Is it possible to create XSD schema for
> importing this into table using SQLXML BulkLoad facility?
> Table:
> ItemID PropertyName PropertyValue
> =================================
> 1 Property1 ...
> 1 Property2 ...
> 1 Property3 ...
> 2 Property1 ...
> 2 Property2 ...
> 2 Property3 ...
> 2 Property4 ...
> ...
>
> Thank you
> Martin Rakhmanov
> jimmers@.yandex.ru
|||No, not this exact data file can be mapped using XSD schema. Use XSLT to
transform this data file to look something like, .
<?xml version="1.0" encoding="UTF-8"?>
<root>
<Item>
<ItemID>1</ItemID>
<Property><Name>Property1</Name><Value>...</Value></Property>
<Property><Name>Property2</Name><Value>...</Value></Property>
<Property><Name>Property3</Name><Value>...</Value></Property>
</Item>
HTH,
Chandra
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
news:ekbVtMv$EHA.1188@.tk2msftngp13.phx.gbl...
> You cannot map names of elements into data using the schema mapping. You
> need to use OpenXML for such mappings.
> HTH
> Michael
> "jimmers" <jimmers@.yandex.ru> wrote in message
> news:b0ede647.0501200116.5025661d@.posting.google.c om...
>
|||Hello Michael and Chandra
First of all, thank you for prompt responses.
Unfortunately I cannot do XSLT transformation because input file size is
huge (~300 Mb): I made test with .NET XslTransform class on 100 Mb XML input
file and simple XSLT file. The program executed approximately 10 minutes and
then out-of-memory exception was thrown. On disk I got incomplete 42 Mb
result file. The server has 512 Mb memory, P4 2.8 GHz CPU and runs under
Windows 2003 Server Standard Edition.
Right now I stick with the following solution: console application reads
elements from input file with help of XmlTextReader class until size
threshold is reached and saves them in temporary files. Then each resulting
file contents is passed to stored procedure that utilized OPENXML. In other
words, I had to duplicate SQLXMLBulkLoad functionality in Transactional mode
and then use OPENXML feature.
By the way, what is the meaning of HTH signature?
Thank you
Martin Rakhmanov
jimmers@.yandex.ru
"Chandra Kalyanaraman [MSFT]" wrote:
> No, not this exact data file can be mapped using XSD schema. Use XSLT to
> transform this data file to look something like, .
> <?xml version="1.0" encoding="UTF-8"?>
> <root>
> <Item>
> <ItemID>1</ItemID>
> <Property><Name>Property1</Name><Value>...</Value></Property>
> <Property><Name>Property2</Name><Value>...</Value></Property>
> <Property><Name>Property3</Name><Value>...</Value></Property>
> </Item>
> HTH,
> Chandra
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
> news:ekbVtMv$EHA.1188@.tk2msftngp13.phx.gbl...
>
>
|||Hi Martin.
300MB XML file: What on earth do you have in that? :-) XML files should be
kept as small as possible and not be used as a "database replacement". :-)
HTH means: Hope This Helps
Best regards
Michael
"jimmers" <jimmers@.discussions.microsoft.com> wrote in message
news:214EF7CD-F4BB-4E5A-AD6C-1A57CFA00C12@.microsoft.com...[vbcol=seagreen]
> Hello Michael and Chandra
> First of all, thank you for prompt responses.
> Unfortunately I cannot do XSLT transformation because input file size is
> huge (~300 Mb): I made test with .NET XslTransform class on 100 Mb XML
> input
> file and simple XSLT file. The program executed approximately 10 minutes
> and
> then out-of-memory exception was thrown. On disk I got incomplete 42 Mb
> result file. The server has 512 Mb memory, P4 2.8 GHz CPU and runs under
> Windows 2003 Server Standard Edition.
> Right now I stick with the following solution: console application reads
> elements from input file with help of XmlTextReader class until size
> threshold is reached and saves them in temporary files. Then each
> resulting
> file contents is passed to stored procedure that utilized OPENXML. In
> other
> words, I had to duplicate SQLXMLBulkLoad functionality in Transactional
> mode
> and then use OPENXML feature.
> By the way, what is the meaning of HTH signature?
> Thank you
> Martin Rakhmanov
> jimmers@.yandex.ru
>
> "Chandra Kalyanaraman [MSFT]" wrote:
|||300 Mb XML file is maximum size, normally it will be about 100 Mb. It is
generated by external system and I cannot affect this unfortunately.
Thank you
Martin
"Michael Rys [MSFT]" wrote:
> Hi Martin.
> 300MB XML file: What on earth do you have in that? :-) XML files should be
> kept as small as possible and not be used as a "database replacement". :-)
> HTH means: Hope This Helps
> Best regards
> Michael
> "jimmers" <jimmers@.discussions.microsoft.com> wrote in message
> news:214EF7CD-F4BB-4E5A-AD6C-1A57CFA00C12@.microsoft.com...
>
>
Friday, March 23, 2012
Is it possible to extract RS installation credentials
Have spent quite some time setting up an eval version of RS featuring
access to both an SQL Server and Analysis Services. Eventually i got it
running smooth. The issues where setting the accounts during
installation of RS in a combination that worked for my situation.
Now the problem: RS eval expired so i am not able to inspect any
settings and the RSReportServer.config file has encrypted values and
the rsconfig utility can only set values in the config file. Moment 22.
Is there anyway i can extract installation settings from the config
file so i can repeat the installation with a licensed version of RS?
No.
Only what you can see in the config files. The encrypted content is not accessible.
If you want to know the service accounts, check the Windows and Web services through the service control panel applet or through the IIS Manager plugin.
sqlFriday, March 9, 2012
Is it necessary...
Is it necessary to upgrade SQL Server version 7 to 2000?
Real question is that 'What's new in version 2000 from
version 7?'
Q. Is it necessary to upgrade SQL Server version 7 to 2000?
A. No, you can install a separate "named instance" on the same server as you
have SQL Server 7.0 installed.
Q. Real question is that 'What's new in version 2000 from version 7?'
A. If you're interested in just what is new in SQL Server 2000 Full-text
Search (as this is the topic of this newsgroup), then the answer is "Change
Tracking" with "Update Index in Background" as well as the ability to FT
Index and FT Search MS Office file type (doc, xls, etc. plus html) stored in
Image datatype columns. If you have SQL Server 2000 installed, you should
review the BOL under Contents and "What's New" as there are many
improvements in SQL Server 2000 over SQL Server 2000.
Regards,
John
"Jerry" <anonymous@.discussions.microsoft.com> wrote in message
news:1a1ac01c41d87$a2193d10$a401280a@.phx.gbl...
> Is it necessary to upgrade SQL Server version 7 to 2000?
> Real question is that 'What's new in version 2000 from
> version 7?'
Real question is that 'What's new in version 2000 from
version 7?'
Q. Is it necessary to upgrade SQL Server version 7 to 2000?
A. No, you can install a separate "named instance" on the same server as you
have SQL Server 7.0 installed.
Q. Real question is that 'What's new in version 2000 from version 7?'
A. If you're interested in just what is new in SQL Server 2000 Full-text
Search (as this is the topic of this newsgroup), then the answer is "Change
Tracking" with "Update Index in Background" as well as the ability to FT
Index and FT Search MS Office file type (doc, xls, etc. plus html) stored in
Image datatype columns. If you have SQL Server 2000 installed, you should
review the BOL under Contents and "What's New" as there are many
improvements in SQL Server 2000 over SQL Server 2000.
Regards,
John
"Jerry" <anonymous@.discussions.microsoft.com> wrote in message
news:1a1ac01c41d87$a2193d10$a401280a@.phx.gbl...
> Is it necessary to upgrade SQL Server version 7 to 2000?
> Real question is that 'What's new in version 2000 from
> version 7?'
Is it easy to upgrade from MSDE to Full blown SQL v2000
Hi,
Noob here....
Got server running app approaching 2gig limit using MSDE version of SQL. I've purchased the full version and just checking if there is anymore to it than inserting the CD and letting it find the MSDE version and upgrade it.
Also, don't remember getting a keycode with the CD - is this right?
Thanks for help :)
Kenny
(bump)
anyone?
|||I have gone from 2000 msde to 2000 developers edition and never had a problem.
Do a backup of your databases and give it a try.
|||I wish I had the same easy experience. So far my upgrade from MSDE 2k to full SQL never gives me the "Upgrade" option. I have to install a new instance.
This is in the course of migrating a SharePoint Services installation from the default MSDE database to SQL.
As this test server had SharePoint portal uninstalled and SQL 2k developer uninstalled, then SharePoint Services by themselves re installed, I wonder if the install wizard just somehow does not see the MSDE instance.
My co workers think I am making this up.. Any ideas as to why no upgrade?
Is it easy to upgrade from MSDE to Full blown SQL v2000
Hi,
Noob here....
Got server running app approaching 2gig limit using MSDE version of SQL. I've purchased the full version and just checking if there is anymore to it than inserting the CD and letting it find the MSDE version and upgrade it.
Also, don't remember getting a keycode with the CD - is this right?
Thanks for help :)
Kenny
(bump)
anyone?
|||I have gone from 2000 msde to 2000 developers edition and never had a problem.
Do a backup of your databases and give it a try.
|||I wish I had the same easy experience. So far my upgrade from MSDE 2k to full SQL never gives me the "Upgrade" option. I have to install a new instance.
This is in the course of migrating a SharePoint Services installation from the default MSDE database to SQL.
As this test server had SharePoint portal uninstalled and SQL 2k developer uninstalled, then SharePoint Services by themselves re installed, I wonder if the install wizard just somehow does not see the MSDE instance.
My co workers think I am making this up.. Any ideas as to why no upgrade?
Is it easy to upgrade from MSDE to Full blown SQL v2000
Hi,
Noob here....
Got server running app approaching 2gig limit using MSDE version of SQL. I've purchased the full version and just checking if there is anymore to it than inserting the CD and letting it find the MSDE version and upgrade it.
Also, don't remember getting a keycode with the CD - is this right?
Thanks for help :)
Kenny
(bump)
anyone?
|||I have gone from 2000 msde to 2000 developers edition and never had a problem.
Do a backup of your databases and give it a try.
|||I wish I had the same easy experience. So far my upgrade from MSDE 2k to full SQL never gives me the "Upgrade" option. I have to install a new instance.
This is in the course of migrating a SharePoint Services installation from the default MSDE database to SQL.
As this test server had SharePoint portal uninstalled and SQL 2k developer uninstalled, then SharePoint Services by themselves re installed, I wonder if the install wizard just somehow does not see the MSDE instance.
My co workers think I am making this up.. Any ideas as to why no upgrade?
Wednesday, March 7, 2012
Is Installing SQL05dev and VS05pro on the same machine supported?
When SQL05dev is installed a SQL05 version of Visual Studio (SQL05-VS) is also installed (called the “SQL Server Business Intelligence Development Studio”). The SQL05-VS installs files into a “C:\Program Files\Microsoft SQL Server\90\Tools\binn\VSShell\Common7\IDE” directory (and other directories - not described here).
When the full version VS05pro is installed it installs/uses files in a “C:\Program Files\Microsoft Visual Studio 8\Common7\IDE” directory.
The number of files in these two directories is different – the directory for VS05pro has (of course) many many more files than the directory for SQL05-VS. On the surface this seems ok since the install of VS05pro should supersede the install of the SQL05-VS and when VS05 is started it utilizes the files from the VS05pro directory and picks up the functions from the SQL05-VS (like SSIS, SSAS, SSRS and such).
But what about the SQL05-VS Common7/IDE directory? In this directory are 64 files that exist in both directores (556 files are not found in the VS05pro Common7/IDE directory). Additionally, there are 10 files that have different versions (mostly having to do with SQL-CE) – newer versions are in the SQL05-VS directory.
I’m confused. Is Microsoft going to support revision changes (Service Packs and such) to both directories? I suppose so, but this introduces possible versioning problems when SQL is updated but VS is not or VS is updated but SQL is not.
I guess I do not understand the rational for not maintaining a single VS directory structure and the problems that this creates. Microsoft is utilizing VS as the IDE for SQL but to not have a really good matching installation layout with the full version of VS is wacky – to say the least. Maybe M$ considers maintaing the versions of 64 files to be unimportant for the correct functioning of VS?
Is Installing SQL05dev and VS05pro on the same machine supported?
MikeC
Installing VS 2005 (and flavor) and SQL 2005 on the same machine is supported.
SQL installs what we call the Premier Partner Edition, which is just the basic IDE with no langauges. SQL then installs its own packages on top of the IDE.
The additional files are SQL specific. The Premier Partner Edition and any VS flavor will install to one location. If you install SQL first, when installing VS, VS will "lock" you to install to a specific directory and won't allow you to install anywhere you want.
That way, you only have one version of the file, its serviced in one place, and is properly ref counted.
|||
QuanT,
You said, "Installing VS 2005 (and flavor) and SQL 2005 on the same machine is supported.”
If this is the case, then I would like to see Microsoft fix the problems with SQL05 when VS and SQL05 are installed on the same machine – *but not to the C: volume*. That is - installing full VS05 (without SQL Express) and SQL05 to a non-C: volume on a freshly formatted/installed version of Windows 2003R2.
You said “If you install SQL first, when installing VS, VS will "lock" you to install to a specific directory and won't allow you to install anywhere you want."
It does not matter which you install first, installing VS to a non-C: volume after SQL is installed to a non-C: volume broke SSIS and the copy db wizard (I did not do any checking beyond these show-stoppers…)
Installing VS first (to a non-C: volume) allows the SQL install to install more components to a non-C: volume, but the problems still arise. Installing in this order should also be supported.
Installing VS to C: and SQL to E: works, but then RS has issues...
It appears that very little SQL05 installation testing was done to anything other than a C: volume - when VS05 is also installed on the same machine - as would be the case on development boxes. On a production db server it is unlikly that I would install the full VS, but who knows, it might be necessary, and should be possible without worry that SQL05 will be broken.
MikeC
Error from create SSIS package (save to server):
===================================
No description found (Microsoft Visual Studio)
Program Location: at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package package, IDTSEvents events, String packagePath, String serverName, String serverUserName, String serverPassword) at Microsoft.DataTransformationServices.Controls.PackageLocationControl.SavePackage(Package package) at Microsoft.DataTransformationServices.Design.Controls.PackageSaveCopyForm.PackageSaveCopyForm_FormClosing(Object sender, FormClosingEventArgs e)
===================================
Error from copy db wizard:
===================================
No description found (Copy Database Wizard)
Program Location: at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package package, IDTSEvents events, String packagePath, String serverName, String
serverUserName, String serverPassword) at Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.SavePackage()
===================================
Thanks for the feedback Mike.
I'm moving this to the SQL Setup alias to get comments from the SQL Team.
|||
Mike,
is your issue resolved? I would like to know what the resolution was if it has been resolved. Iam encountering the same issue now.
My setup is:
1. Installed SQL2000 (default instance)
2. Installed SQL2005 (named instance)
All on C:
I was able to save SSIS packages to the DB until recently using "Save Copy of <pkg> As".
Now I'm encountering the above error (No decription found etc..). I don't even remember anymore if I specified the <machine name> OR <machine name>\<Instance Name> for the "Server" when I had it working.
But I tried with both and I get different errors:
<machine name>\<Instance Name> : No decription found etc.
<machine name> :
======================
The ExistsOnSQLServer method has encountered OLE DB error code 0x80004005 (Client unable to establish connection). The SQL statement issued has failed.
(Microsoft Visual Studio)
=======================
For "Protection Level", I have tried different options, but it doesn't seem to matter.
Another thing is that I suspect this may have started happening after I was trying to install VS05 (other components) on top of the default version that was installed along with SQL05. I didn't go ahead with the VS install and canceled it half way through the initial install setup.
Any inputs are appreciated.
Thanks.
|||Sql_Rv,
I have an open support call with M$ for the last week or so about the "can't save package" problem. This problem with saving packages absolutely has something to do with installing VS05 on the same machine that has SQL05 installed. Works without VS05, fails with VS05 installed.
To fix your installation (without a complete wipe of the house-of-cards that is Windows ), I suggest installing VS05 all the way! Then run the VS05 uninstall. This is the only way to get the VS05 install/uninstall program to run and remove the all the bits of VS05 that M$ stashes all over the place - especially the registry. I would hope that an aborted VS05 install would back-out any changes, but given the somewhat buggy state of Win03r2, MMCv3, VS05 and SQL05 tools… Really, I don’t think M$ has it altogether any more, the testers likely do not have initiative to try anything slightly out of line…
Lets see - ALL third party and M$ products like ISA04 that use MMC cause the new MMC v3 to crash on WinR2 - really - what kind of testing is M$ doing? I suppose we are doing the testing for them...
It would be nice if M$ (and other M$ app mfg) would wake up and see the simplicity of installing all executables of an application in ONE directory tree, and have a minimal registry footprint. A manifest of files would be nice also - but no, we get this horrific splat of install logs that lists what files were installed - and the number of registry entries that get added by SQL05 is obscene. Really, it is too much to ask for list of files and their versions needed to maintain a SQL05 installation? Tracking revisions must be a fuzzy concept at M$...
Anyway - M$ support is slow on the testing and the wonderfully informative error message "no description found" goes a long way in pointing to the problem - not.
Question: What version of Windows are you running? Is it a domain controller? Are SQL services running with a domain account?
MikeC
|||Mike,
Thanks for taking the time to respond. I appreciate it.
This is on my dev box which is running XP Pro. No, it is not a domain controller. Yes, the services are running with a domain account that has admin privileges on this box.
btw, to get around this problem, I tried saving it from a different machine and it worked. This is what I did:
box1\2K5 - Unable to save the pkg to this DB from box1.
box2 - Has a 2K5 instance too. I used this to save it to box1\2K5 by doing a save as and specifying box1\2K5 as the SQLServer name - and it saved successfully.
Thanks,
RV
|||I have the same problem.
MS WinXP Pro sp2 (latest patches as of 9.26.2006)
SQL Server 2005
VS2005
error:TITLE: SQL Server Import and Export Wizard The operation could not be completed. ADDITIONAL INFORMATION: The ExistsOnSQLServer method has encountered OLE DB error code 0x80004005 (Client unable to establish connection). The SQL statement issued has failed. BUTTONS: OK
The error is generated when I try to save the SISS package to the SQL server instance mentioned above.
I was able to save the SISS package using the filesystem option.
Is Installing SQL05dev and VS05pro on the same machine supported?
When SQL05dev is installed a SQL05 version of Visual Studio (SQL05-VS) is also installed (called the “SQL Server Business Intelligence Development Studio”). The SQL05-VS installs files into a “C:\Program Files\Microsoft SQL Server\90\Tools\binn\VSShell\Common7\IDE” directory (and other directories - not described here).
When the full version VS05pro is installed it installs/uses files in a “C:\Program Files\Microsoft Visual Studio 8\Common7\IDE” directory.
The number of files in these two directories is different – the directory for VS05pro has (of course) many many more files than the directory for SQL05-VS. On the surface this seems ok since the install of VS05pro should supersede the install of the SQL05-VS and when VS05 is started it utilizes the files from the VS05pro directory and picks up the functions from the SQL05-VS (like SSIS, SSAS, SSRS and such).
But what about the SQL05-VS Common7/IDE directory? In this directory are 64 files that exist in both directores (556 files are not found in the VS05pro Common7/IDE directory). Additionally, there are 10 files that have different versions (mostly having to do with SQL-CE) – newer versions are in the SQL05-VS directory.
I’m confused. Is Microsoft going to support revision changes (Service Packs and such) to both directories? I suppose so, but this introduces possible versioning problems when SQL is updated but VS is not or VS is updated but SQL is not.
I guess I do not understand the rational for not maintaining a single VS directory structure and the problems that this creates. Microsoft is utilizing VS as the IDE for SQL but to not have a really good matching installation layout with the full version of VS is wacky – to say the least. Maybe M$ considers maintaing the versions of 64 files to be unimportant for the correct functioning of VS?
Is Installing SQL05dev and VS05pro on the same machine supported?
MikeC
Installing VS 2005 (and flavor) and SQL 2005 on the same machine is supported.
SQL installs what we call the Premier Partner Edition, which is just the basic IDE with no langauges. SQL then installs its own packages on top of the IDE.
The additional files are SQL specific. The Premier Partner Edition and any VS flavor will install to one location. If you install SQL first, when installing VS, VS will "lock" you to install to a specific directory and won't allow you to install anywhere you want.
That way, you only have one version of the file, its serviced in one place, and is properly ref counted.
|||
QuanT,
You said, "Installing VS 2005 (and flavor) and SQL 2005 on the same machine is supported.”
If this is the case, then I would like to see Microsoft fix the problems with SQL05 when VS and SQL05 are installed on the same machine – *but not to the C: volume*. That is - installing full VS05 (without SQL Express) and SQL05 to a non-C: volume on a freshly formatted/installed version of Windows 2003R2.
You said “If you install SQL first, when installing VS, VS will "lock" you to install to a specific directory and won't allow you to install anywhere you want."
It does not matter which you install first, installing VS to a non-C: volume after SQL is installed to a non-C: volume broke SSIS and the copy db wizard (I did not do any checking beyond these show-stoppers…)
Installing VS first (to a non-C: volume) allows the SQL install to install more components to a non-C: volume, but the problems still arise. Installing in this order should also be supported.
Installing VS to C: and SQL to E: works, but then RS has issues...
It appears that very little SQL05 installation testing was done to anything other than a C: volume - when VS05 is also installed on the same machine - as would be the case on development boxes. On a production db server it is unlikly that I would install the full VS, but who knows, it might be necessary, and should be possible without worry that SQL05 will be broken.
MikeC
Error from create SSIS package (save to server):
===================================
No description found (Microsoft Visual Studio)
Program Location: at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package package, IDTSEvents events, String packagePath, String serverName, String serverUserName, String serverPassword) at Microsoft.DataTransformationServices.Controls.PackageLocationControl.SavePackage(Package package) at Microsoft.DataTransformationServices.Design.Controls.PackageSaveCopyForm.PackageSaveCopyForm_FormClosing(Object sender, FormClosingEventArgs e)
===================================
Error from copy db wizard:
===================================
No description found (Copy Database Wizard)
Program Location: at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package package, IDTSEvents events, String packagePath, String serverName, String
serverUserName, String serverPassword) at Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.SavePackage()
===================================
Thanks for the feedback Mike.
I'm moving this to the SQL Setup alias to get comments from the SQL Team.
|||
Mike,
is your issue resolved? I would like to know what the resolution was if it has been resolved. Iam encountering the same issue now.
My setup is:
1. Installed SQL2000 (default instance)
2. Installed SQL2005 (named instance)
All on C:
I was able to save SSIS packages to the DB until recently using "Save Copy of <pkg> As".
Now I'm encountering the above error (No decription found etc..). I don't even remember anymore if I specified the <machine name> OR <machine name>\<Instance Name> for the "Server" when I had it working.
But I tried with both and I get different errors:
<machine name>\<Instance Name> : No decription found etc.
<machine name> :
======================
The ExistsOnSQLServer method has encountered OLE DB error code 0x80004005 (Client unable to establish connection). The SQL statement issued has failed.
(Microsoft Visual Studio)
=======================
For "Protection Level", I have tried different options, but it doesn't seem to matter.
Another thing is that I suspect this may have started happening after I was trying to install VS05 (other components) on top of the default version that was installed along with SQL05. I didn't go ahead with the VS install and canceled it half way through the initial install setup.
Any inputs are appreciated.
Thanks.
|||Sql_Rv,
I have an open support call with M$ for the last week or so about the "can't save package" problem. This problem with saving packages absolutely has something to do with installing VS05 on the same machine that has SQL05 installed. Works without VS05, fails with VS05 installed.
To fix your installation (without a complete wipe of the house-of-cards that is Windows ), I suggest installing VS05 all the way! Then run the VS05 uninstall. This is the only way to get the VS05 install/uninstall program to run and remove the all the bits of VS05 that M$ stashes all over the place - especially the registry. I would hope that an aborted VS05 install would back-out any changes, but given the somewhat buggy state of Win03r2, MMCv3, VS05 and SQL05 tools… Really, I don’t think M$ has it altogether any more, the testers likely do not have initiative to try anything slightly out of line…
Lets see - ALL third party and M$ products like ISA04 that use MMC cause the new MMC v3 to crash on WinR2 - really - what kind of testing is M$ doing? I suppose we are doing the testing for them...
It would be nice if M$ (and other M$ app mfg) would wake up and see the simplicity of installing all executables of an application in ONE directory tree, and have a minimal registry footprint. A manifest of files would be nice also - but no, we get this horrific splat of install logs that lists what files were installed - and the number of registry entries that get added by SQL05 is obscene. Really, it is too much to ask for list of files and their versions needed to maintain a SQL05 installation? Tracking revisions must be a fuzzy concept at M$...
Anyway - M$ support is slow on the testing and the wonderfully informative error message "no description found" goes a long way in pointing to the problem - not.
Question: What version of Windows are you running? Is it a domain controller? Are SQL services running with a domain account?
MikeC
|||Mike,
Thanks for taking the time to respond. I appreciate it.
This is on my dev box which is running XP Pro. No, it is not a domain controller. Yes, the services are running with a domain account that has admin privileges on this box.
btw, to get around this problem, I tried saving it from a different machine and it worked. This is what I did:
box1\2K5 - Unable to save the pkg to this DB from box1.
box2 - Has a 2K5 instance too. I used this to save it to box1\2K5 by doing a save as and specifying box1\2K5 as the SQLServer name - and it saved successfully.
Thanks,
RV
|||I have the same problem.
MS WinXP Pro sp2 (latest patches as of 9.26.2006)
SQL Server 2005
VS2005
error:TITLE: SQL Server Import and Export Wizard The operation could not be completed. ADDITIONAL INFORMATION: The ExistsOnSQLServer method has encountered OLE DB error code 0x80004005 (Client unable to establish connection). The SQL statement issued has failed. BUTTONS: OK
The error is generated when I try to save the SISS package to the SQL server instance mentioned above.
I was able to save the SISS package using the filesystem option.
Is Installing SQL05dev and VS05pro on the same machine supported?
When SQL05dev is installed a SQL05 version of Visual Studio (SQL05-VS) is also installed (called the “SQL Server Business Intelligence Development Studio”). The SQL05-VS installs files into a “C:\Program Files\Microsoft SQL Server\90\Tools\binn\VSShell\Common7\IDE” directory (and other directories - not described here).
When the full version VS05pro is installed it installs/uses files in a “C:\Program Files\Microsoft Visual Studio 8\Common7\IDE” directory.
The number of files in these two directories is different – the directory for VS05pro has (of course) many many more files than the directory for SQL05-VS. On the surface this seems ok since the install of VS05pro should supersede the install of the SQL05-VS and when VS05 is started it utilizes the files from the VS05pro directory and picks up the functions from the SQL05-VS (like SSIS, SSAS, SSRS and such).
But what about the SQL05-VS Common7/IDE directory? In this directory are 64 files that exist in both directores (556 files are not found in the VS05pro Common7/IDE directory). Additionally, there are 10 files that have different versions (mostly having to do with SQL-CE) – newer versions are in the SQL05-VS directory.
I’m confused. Is Microsoft going to support revision changes (Service Packs and such) to both directories? I suppose so, but this introduces possible versioning problems when SQL is updated but VS is not or VS is updated but SQL is not.
I guess I do not understand the rational for not maintaining a single VS directory structure and the problems that this creates. Microsoft is utilizing VS as the IDE for SQL but to not have a really good matching installation layout with the full version of VS is wacky – to say the least. Maybe M$ considers maintaing the versions of 64 files to be unimportant for the correct functioning of VS?
Is Installing SQL05dev and VS05pro on the same machine supported?
MikeC
Installing VS 2005 (and flavor) and SQL 2005 on the same machine is supported.
SQL installs what we call the Premier Partner Edition, which is just the basic IDE with no langauges. SQL then installs its own packages on top of the IDE.
The additional files are SQL specific. The Premier Partner Edition and any VS flavor will install to one location. If you install SQL first, when installing VS, VS will "lock" you to install to a specific directory and won't allow you to install anywhere you want.
That way, you only have one version of the file, its serviced in one place, and is properly ref counted.
|||
QuanT,
You said, "Installing VS 2005 (and flavor) and SQL 2005 on the same machine is supported.”
If this is the case, then I would like to see Microsoft fix the problems with SQL05 when VS and SQL05 are installed on the same machine – *but not to the C: volume*. That is - installing full VS05 (without SQL Express) and SQL05 to a non-C: volume on a freshly formatted/installed version of Windows 2003R2.
You said “If you install SQL first, when installing VS, VS will "lock" you to install to a specific directory and won't allow you to install anywhere you want."
It does not matter which you install first, installing VS to a non-C: volume after SQL is installed to a non-C: volume broke SSIS and the copy db wizard (I did not do any checking beyond these show-stoppers…)
Installing VS first (to a non-C: volume) allows the SQL install to install more components to a non-C: volume, but the problems still arise. Installing in this order should also be supported.
Installing VS to C: and SQL to E: works, but then RS has issues...
It appears that very little SQL05 installation testing was done to anything other than a C: volume - when VS05 is also installed on the same machine - as would be the case on development boxes. On a production db server it is unlikly that I would install the full VS, but who knows, it might be necessary, and should be possible without worry that SQL05 will be broken.
MikeC
Error from create SSIS package (save to server):
===================================
No description found (Microsoft Visual Studio)
Program Location: at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package package, IDTSEvents events, String packagePath, String serverName, String serverUserName, String serverPassword) at Microsoft.DataTransformationServices.Controls.PackageLocationControl.SavePackage(Package package) at Microsoft.DataTransformationServices.Design.Controls.PackageSaveCopyForm.PackageSaveCopyForm_FormClosing(Object sender, FormClosingEventArgs e)
===================================
Error from copy db wizard:
===================================
No description found (Copy Database Wizard)
Program Location: at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package package, IDTSEvents events, String packagePath, String serverName, String
serverUserName, String serverPassword) at Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.SavePackage()
===================================
Thanks for the feedback Mike.
I'm moving this to the SQL Setup alias to get comments from the SQL Team.
|||
Mike,
is your issue resolved? I would like to know what the resolution was if it has been resolved. Iam encountering the same issue now.
My setup is:
1. Installed SQL2000 (default instance)
2. Installed SQL2005 (named instance)
All on C:
I was able to save SSIS packages to the DB until recently using "Save Copy of <pkg> As".
Now I'm encountering the above error (No decription found etc..). I don't even remember anymore if I specified the <machine name> OR <machine name>\<Instance Name> for the "Server" when I had it working.
But I tried with both and I get different errors:
<machine name>\<Instance Name> : No decription found etc.
<machine name> :
======================
The ExistsOnSQLServer method has encountered OLE DB error code 0x80004005 (Client unable to establish connection). The SQL statement issued has failed.
(Microsoft Visual Studio)
=======================
For "Protection Level", I have tried different options, but it doesn't seem to matter.
Another thing is that I suspect this may have started happening after I was trying to install VS05 (other components) on top of the default version that was installed along with SQL05. I didn't go ahead with the VS install and canceled it half way through the initial install setup.
Any inputs are appreciated.
Thanks.
|||Sql_Rv,
I have an open support call with M$ for the last week or so about the "can't save package" problem. This problem with saving packages absolutely has something to do with installing VS05 on the same machine that has SQL05 installed. Works without VS05, fails with VS05 installed.
To fix your installation (without a complete wipe of the house-of-cards that is Windows ), I suggest installing VS05 all the way! Then run the VS05 uninstall. This is the only way to get the VS05 install/uninstall program to run and remove the all the bits of VS05 that M$ stashes all over the place - especially the registry. I would hope that an aborted VS05 install would back-out any changes, but given the somewhat buggy state of Win03r2, MMCv3, VS05 and SQL05 tools… Really, I don’t think M$ has it altogether any more, the testers likely do not have initiative to try anything slightly out of line…
Lets see - ALL third party and M$ products like ISA04 that use MMC cause the new MMC v3 to crash on WinR2 - really - what kind of testing is M$ doing? I suppose we are doing the testing for them...
It would be nice if M$ (and other M$ app mfg) would wake up and see the simplicity of installing all executables of an application in ONE directory tree, and have a minimal registry footprint. A manifest of files would be nice also - but no, we get this horrific splat of install logs that lists what files were installed - and the number of registry entries that get added by SQL05 is obscene. Really, it is too much to ask for list of files and their versions needed to maintain a SQL05 installation? Tracking revisions must be a fuzzy concept at M$...
Anyway - M$ support is slow on the testing and the wonderfully informative error message "no description found" goes a long way in pointing to the problem - not.
Question: What version of Windows are you running? Is it a domain controller? Are SQL services running with a domain account?
MikeC
|||Mike,
Thanks for taking the time to respond. I appreciate it.
This is on my dev box which is running XP Pro. No, it is not a domain controller. Yes, the services are running with a domain account that has admin privileges on this box.
btw, to get around this problem, I tried saving it from a different machine and it worked. This is what I did:
box1\2K5 - Unable to save the pkg to this DB from box1.
box2 - Has a 2K5 instance too. I used this to save it to box1\2K5 by doing a save as and specifying box1\2K5 as the SQLServer name - and it saved successfully.
Thanks,
RV
|||I have the same problem.
MS WinXP Pro sp2 (latest patches as of 9.26.2006)
SQL Server 2005
VS2005
error:TITLE: SQL Server Import and Export Wizard The operation could not be completed. ADDITIONAL INFORMATION: The ExistsOnSQLServer method has encountered OLE DB error code 0x80004005 (Client unable to establish connection). The SQL statement issued has failed. BUTTONS: OK
The error is generated when I try to save the SISS package to the SQL server instance mentioned above.
I was able to save the SISS package using the filesystem option.
Monday, February 20, 2012
Is Arcserve 2000 backing up my SQL server properly?
I recently installed arcserve small business version for a client who
is running SQL server. It seems that at the beginning of the backup
cycle the files are skipped due to a sharing violation (I mean the
database files). Later during the part when the SQL agent backs up
files it seems to back up fine. Is this normal or is something wrong
here. Below is a log...sorry if it is a little long. Thanks so much
for youe help.
20030701 010009 16 Run Backup Job Scheduled for 7/01/03 at 1:00 AM.
20030701 010009 16 Start Backup Operation. (QUEUE=1, JOB=2)
20030701 010010 16 Overwrite media Monthly2, ID DBA9, sequence #1
20030701 010037 TAPE Tape Engine finished formatting media.(new name:
Monthly2, old name: Monthly2)
20030701 010037 Begin cleaning database.
20030701 010044 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=1, RECS=18130)
20030701 010047 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=2, RECS=11705)
20030701 010048 TAPE Format Successful!
20030701 010048 16 Use media Monthly2, ID 2542, sequence #1
20030701 010054 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=3, RECS=27896)
20030701 010129 16 Source Directory: C:
20030701 010129 16 Back up Session 1 on Media Monthly2
20030701 010129 16 Backed up volume disk quota.
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=4, RECS=151242)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=5, RECS=7)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=6, RECS=12)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=7, RECS=12)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=8, RECS=12)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=9, RECS=12)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=10, RECS=12)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=11, RECS=12)
20030701 010159 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=12, RECS=13291)
20030701 010159 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=13, RECS=225)
20030701 010159 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=14, RECS=123)
20030701 010159 End cleaning database. (CLEANED=222691)
20030701 010233 16 W3404 Unable to open file. (FILE=C:\Documents and
Settings\All Users\Application
Data\Microsoft\Network\Downloader\qmgr0.dat, EC=SHARING VIOLATION)
20030701 010233 16 W3404 Unable to open file. (FILE=C:\Documents and
Settings\All Users\Application
Data\Microsoft\Network\Downloader\qmgr1.dat, EC=SHARING VIOLATION)
20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSDYNAMICSDat.mdf,
EC=SHARING VIOLATION)
20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSDYNAMICSLog.ldf,
EC=SHARING VIOLATION)
20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSSBM01Dat.mdf,
EC=SHARING VIOLATION)
20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSSBM01Log.ldf,
EC=SHARING VIOLATION)
20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSTWODat.mdf,
EC=SHARING VIOLATION)
20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSTWOLog.ldf,
EC=SHARING VIOLATION)
20030701 010601 16 Catalog File Backed Up
20030701 010601 16 Registry Files Backed Up
20030701 010601 16 1,049 Directories 17,088 Files (1,404.55 MB) Backed
Up to Media.
20030701 010601 16 8 Directories/Files Skipped.
20030701 010601 16 1,463.31 MB Written to Media.
20030701 010601 16 Elapsed Time: 4m 30s
20030701 010601 16 Average Throughput: 325.17 MB/min
20030701 010601 16 Number of Errors/Warnings: 0/8
20030701 010611 16 Source Directory: E:
20030701 010611 16 Back up Session 2 on Media Monthly2
20030701 010611 16 Backed up volume disk quota.
20030701 011115 16 Catalog File Backed Up
20030701 011115 16 563 Directories 11,142 Files (1,254.87 MB) Backed
Up to Media.
20030701 011115 16 1,292.68 MB Written to Media.
20030701 011115 16 Elapsed Time: 5m 0s
20030701 011115 16 Average Throughput: 258.53 MB/min
20030701 011201 16 Source Directory: F:
20030701 011201 16 Back up Session 3 on Media Monthly2
20030701 011201 16 Backed up volume disk quota.
20030701 012213 16 Catalog File Backed Up
20030701 012213 16 4,665 Directories 23,262 Files (3,229.25 MB) Backed
Up to Media.
20030701 012213 16 3,320.18 MB Written to Media.
20030701 012213 16 Elapsed Time: 10m 9s
20030701 012213 16 Average Throughput: 327.11 MB/min
20030701 012213 16 Source Directory: Registry
20030701 012213 16 Back up Session 4 on Media Monthly2
20030701 012244 16 Registry Files Backed Up
20030701 012244 16 54,946 Directories 96,295 Files (21.42 MB) Backed
Up to Media.
20030701 012244 16 404.87 MB Written to Media.
20030701 012244 16 Elapsed Time: 28s
20030701 012244 16 Average Throughput: 867.58 MB/min
20030701 012244 16 Source Directory: dbaexchis\First Storage Group
20030701 012244 16 Back up Session 5 on Media Monthly2
20030701 012301 16 1 Databases/Transaction Logs (103.04 MB) Backed Up
to Media.
20030701 012301 16 103.12 MB Written to Media.
20030701 012301 16 Elapsed Time: 15s
20030701 012301 16 Average Throughput: 412.50 MB/min
20030701 012302 16 Source Directory: dbasql@.MSGPSBM\TWO
20030701 012302 16 Back up Session 6 on Media Monthly2
20030701 012311 16 1 Databases/Transaction Logs (90.07 MB) Backed Up
to Media.
20030701 012311 16 90.18 MB Written to Media.
20030701 012311 16 Elapsed Time: 7s
20030701 012311 16 Average Throughput: 773.03 MB/min
20030701 012311 16 Source Directory: dbasql@.MSGPSBM\SBM01
20030701 012311 16 Back up Session 7 on Media Monthly2
20030701 012355 16 1 Databases/Transaction Logs (548.07 MB) Backed Up
to Media.
20030701 012355 16 548.37 MB Written to Media.
20030701 012355 16 Elapsed Time: 42s
20030701 012355 16 Average Throughput: 783.39 MB/min
20030701 012355 16 Source Directory: dbasql@.MSGPSBM\msdb
20030701 012355 16 Back up Session 8 on Media Monthly2
20030701 012357 16 1 Databases/Transaction Logs (2.32 MB) Backed Up to
Media.
20030701 012357 16 2.37 MB Written to Media.
20030701 012357 16 Elapsed Time: 1s
20030701 012357 16 Average Throughput: 142.50 MB/min
20030701 012357 16 Source Directory: dbasql@.MSGPSBM\model
20030701 012357 16 Back up Session 9 on Media Monthly2
20030701 012400 16 1 Databases/Transaction Logs (721 KB) Backed Up to
Media.
20030701 012400 16 768 KB Written to Media.
20030701 012400 16 Elapsed Time: 1s
20030701 012400 16 Average Throughput: 45.00 MB/min
20030701 012400 16 Source Directory: dbasql@.MSGPSBM\master
20030701 012400 16 Back up Session 10 on Media Monthly2
20030701 012407 16 1 Databases/Transaction Logs (10.51 MB) Backed Up
to Media.
20030701 012407 16 10.56 MB Written to Media.
20030701 012407 16 Elapsed Time: 0s
20030701 012407 16 Average Throughput: 633.75 MB/min
20030701 012407 16 Source Directory: dbasql@.MSGPSBM\DYNAMICS
20030701 012407 16 Back up Session 11 on Media Monthly2
20030701 012412 16 1 Databases/Transaction Logs (29.95 MB) Backed Up
to Media.
20030701 012412 16 30.00 MB Written to Media.
20030701 012412 16 Elapsed Time: 3s
20030701 012412 16 Average Throughput: 600.00 MB/min
20030701 012413 16 Source Directory: System State
20030701 012413 16 Back up Session 12 on Media Monthly2
20030701 012413 16 Backing Up Files : Boot and System Protected Files
20030701 012445 16 Backing Up Files : Active Directory
20030701 012448 16 Backing Up Files : SysVol
20030701 012448 16 Backing Up Files : COM+ Class Registration Database
20030701 012448 16 Backing Up Files : Registry
20030701 012455 16 Registry Files Backed Up
20030701 012455 16 91 Directories 1,963 Files (287.99 MB) Backed Up to
Media.
20030701 012455 16 294.56 MB Written to Media.
20030701 012455 16 Elapsed Time: 39s
20030701 012455 16 Average Throughput: 453.17 MB/min
20030701 012455 16 Source Directory: dbaxchg2
20030701 012455 16 Back up Session 13 on Media Monthly2
20030701 012516 16 11 Databases/Transaction Logs (40.19 MB) Backed Up
to Media.
20030701 012516 16 40.50 MB Written to Media.
20030701 012516 16 Elapsed Time: 19s
20030701 012516 16 Average Throughput: 127.89 MB/min
20030701 012516 16 ** Summary for My Computer **
20030701 012516 16 13 Sessions.
20030701 012516 16 61,314 Directories 149,750 Files (6,198.15 MB)
Backed Up to Media.
20030701 012516 16 18 Databases/Transaction Logs (824.89 MB) Backed Up
to Media.
20030701 012516 16 8 Directories/Files Skipped.
20030701 012516 16 7,601.50 MB Written to Media.
20030701 012516 16 Elapsed Time: 22m 14s
20030701 012516 16 Average Throughput: 341.89 MB/min
20030701 012516 16 Number of Errors/Warnings: 0/8
20030701 012519 16 Backup ARCserve Database...
20030701 012520 16 Source Directory: C:\Program
Files\ComputerAssociates\ARCserve\DATABASE
20030701 012520 16 Back up Session 14 on Media Monthly2
20030701 012529 16 Catalog File Backed Up
20030701 012529 16 1 Directories 118 Files (104.17 MB) Backed Up to
Media.
20030701 012529 16 104.62 MB Written to Media.
20030701 012529 16 Elapsed Time: 7s
20030701 012529 16 Average Throughput: 896.78 MB/min
20030701 012529 16 ARCServe Database Backed Up
20030701 012538 [CAT] Monthly2 [ID:2542,SESSION:1] is
merged.(files=17088)
20030701 012542 [CAT] Monthly2 [ID:2542,SESSION:2] is
merged.(files=11142)
20030701 012555 [CAT] Monthly2 [ID:2542,SESSION:3] is
merged.(files=23262)
20030701 012631 16 ** Summary for Job **
20030701 012631 16 14 Sessions.
20030701 012631 16 61,315 Directories 149,868 Files (6,302.33 MB)
Backed Up to Media.
20030701 012631 16 18 Databases/Transaction Logs (824.89 MB) Backed Up
to Media.
20030701 012631 16 8 Directories/Files Skipped.
20030701 012631 16 7,706.12 MB Written to Media.
20030701 012631 16 Elapsed Time: 22m 21s
20030701 012631 16 Average Throughput: 344.79 MB/min
20030701 012631 16 Number of Errors/Warnings: 0/8
20030701 012631 16 Backup Operation Incomplete.
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:4] is
merged.(files=96295)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:5] is merged.(files=5)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:6] is merged.(files=3)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:7] is merged.(files=3)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:8] is merged.(files=3)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:9] is merged.(files=3)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:10] is
merged.(files=3)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:11] is
merged.(files=3)
20030701 012708 [CAT] Monthly2 [ID:2542,SESSION:12] is
merged.(files=1963)
20030701 012708 [CAT] Monthly2 [ID:2542,SESSION:13] is
merged.(files=110)
20030701 012708 [CAT] Monthly2 [ID:2542,SESSION:14] is
merged.(files=118)
20030701 012709 16 Reschedule Backup Job for 7/02/03 at 1:00 AM.You can't normally backup the database files with ArcServe since they are
always in use. I believe they have a way to bypass that but then what good
is backing up a file that is constantly changing. You can't restore the db
using these backups made from Arcserve since they are not consistent. What
you can do is basically one of 2 things. Either use the SQL Server plug-in
for ArcServe to have it issue the equivalent of a sql server backup or don't
even attempt to backup the database files with Arcserve and have it backup
the files generated by the SQL Server backup.
--
Andrew J. Kelly
SQL Server MVP
"Devin G" <devin@.spamhole.com> wrote in message
news:495ba422.0307021902.4a418a32@.posting.google.com...
> I recently installed arcserve small business version for a client who
> is running SQL server. It seems that at the beginning of the backup
> cycle the files are skipped due to a sharing violation (I mean the
> database files). Later during the part when the SQL agent backs up
> files it seems to back up fine. Is this normal or is something wrong
> here. Below is a log...sorry if it is a little long. Thanks so much
> for youe help.
>
> 20030701 010009 16 Run Backup Job Scheduled for 7/01/03 at 1:00 AM.
> 20030701 010009 16 Start Backup Operation. (QUEUE=1, JOB=2)
> 20030701 010010 16 Overwrite media Monthly2, ID DBA9, sequence #1
> 20030701 010037 TAPE Tape Engine finished formatting media.(new name:
> Monthly2, old name: Monthly2)
> 20030701 010037 Begin cleaning database.
> 20030701 010044 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=1, RECS=18130)
> 20030701 010047 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=2, RECS=11705)
> 20030701 010048 TAPE Format Successful!
> 20030701 010048 16 Use media Monthly2, ID 2542, sequence #1
> 20030701 010054 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=3, RECS=27896)
> 20030701 010129 16 Source Directory: C:
> 20030701 010129 16 Back up Session 1 on Media Monthly2
> 20030701 010129 16 Backed up volume disk quota.
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=4, RECS=151242)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=5, RECS=7)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=6, RECS=12)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=7, RECS=12)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=8, RECS=12)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=9, RECS=12)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=10, RECS=12)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=11, RECS=12)
> 20030701 010159 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=12, RECS=13291)
> 20030701 010159 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=13, RECS=225)
> 20030701 010159 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=14, RECS=123)
> 20030701 010159 End cleaning database. (CLEANED=222691)
> 20030701 010233 16 W3404 Unable to open file. (FILE=C:\Documents and
> Settings\All Users\Application
> Data\Microsoft\Network\Downloader\qmgr0.dat, EC=SHARING VIOLATION)
> 20030701 010233 16 W3404 Unable to open file. (FILE=C:\Documents and
> Settings\All Users\Application
> Data\Microsoft\Network\Downloader\qmgr1.dat, EC=SHARING VIOLATION)
> 20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
> Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSDYNAMICSDat.mdf,
> EC=SHARING VIOLATION)
> 20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
> Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSDYNAMICSLog.ldf,
> EC=SHARING VIOLATION)
> 20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
> Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSSBM01Dat.mdf,
> EC=SHARING VIOLATION)
> 20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
> Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSSBM01Log.ldf,
> EC=SHARING VIOLATION)
> 20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
> Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSTWODat.mdf,
> EC=SHARING VIOLATION)
> 20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
> Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSTWOLog.ldf,
> EC=SHARING VIOLATION)
> 20030701 010601 16 Catalog File Backed Up
> 20030701 010601 16 Registry Files Backed Up
> 20030701 010601 16 1,049 Directories 17,088 Files (1,404.55 MB) Backed
> Up to Media.
> 20030701 010601 16 8 Directories/Files Skipped.
> 20030701 010601 16 1,463.31 MB Written to Media.
> 20030701 010601 16 Elapsed Time: 4m 30s
> 20030701 010601 16 Average Throughput: 325.17 MB/min
> 20030701 010601 16 Number of Errors/Warnings: 0/8
> 20030701 010611 16 Source Directory: E:
> 20030701 010611 16 Back up Session 2 on Media Monthly2
> 20030701 010611 16 Backed up volume disk quota.
> 20030701 011115 16 Catalog File Backed Up
> 20030701 011115 16 563 Directories 11,142 Files (1,254.87 MB) Backed
> Up to Media.
> 20030701 011115 16 1,292.68 MB Written to Media.
> 20030701 011115 16 Elapsed Time: 5m 0s
> 20030701 011115 16 Average Throughput: 258.53 MB/min
> 20030701 011201 16 Source Directory: F:
> 20030701 011201 16 Back up Session 3 on Media Monthly2
> 20030701 011201 16 Backed up volume disk quota.
> 20030701 012213 16 Catalog File Backed Up
> 20030701 012213 16 4,665 Directories 23,262 Files (3,229.25 MB) Backed
> Up to Media.
> 20030701 012213 16 3,320.18 MB Written to Media.
> 20030701 012213 16 Elapsed Time: 10m 9s
> 20030701 012213 16 Average Throughput: 327.11 MB/min
> 20030701 012213 16 Source Directory: Registry
> 20030701 012213 16 Back up Session 4 on Media Monthly2
> 20030701 012244 16 Registry Files Backed Up
> 20030701 012244 16 54,946 Directories 96,295 Files (21.42 MB) Backed
> Up to Media.
> 20030701 012244 16 404.87 MB Written to Media.
> 20030701 012244 16 Elapsed Time: 28s
> 20030701 012244 16 Average Throughput: 867.58 MB/min
> 20030701 012244 16 Source Directory: dbaexchis\First Storage Group
> 20030701 012244 16 Back up Session 5 on Media Monthly2
> 20030701 012301 16 1 Databases/Transaction Logs (103.04 MB) Backed Up
> to Media.
> 20030701 012301 16 103.12 MB Written to Media.
> 20030701 012301 16 Elapsed Time: 15s
> 20030701 012301 16 Average Throughput: 412.50 MB/min
> 20030701 012302 16 Source Directory: dbasql@.MSGPSBM\TWO
> 20030701 012302 16 Back up Session 6 on Media Monthly2
> 20030701 012311 16 1 Databases/Transaction Logs (90.07 MB) Backed Up
> to Media.
> 20030701 012311 16 90.18 MB Written to Media.
> 20030701 012311 16 Elapsed Time: 7s
> 20030701 012311 16 Average Throughput: 773.03 MB/min
> 20030701 012311 16 Source Directory: dbasql@.MSGPSBM\SBM01
> 20030701 012311 16 Back up Session 7 on Media Monthly2
> 20030701 012355 16 1 Databases/Transaction Logs (548.07 MB) Backed Up
> to Media.
> 20030701 012355 16 548.37 MB Written to Media.
> 20030701 012355 16 Elapsed Time: 42s
> 20030701 012355 16 Average Throughput: 783.39 MB/min
> 20030701 012355 16 Source Directory: dbasql@.MSGPSBM\msdb
> 20030701 012355 16 Back up Session 8 on Media Monthly2
> 20030701 012357 16 1 Databases/Transaction Logs (2.32 MB) Backed Up to
> Media.
> 20030701 012357 16 2.37 MB Written to Media.
> 20030701 012357 16 Elapsed Time: 1s
> 20030701 012357 16 Average Throughput: 142.50 MB/min
> 20030701 012357 16 Source Directory: dbasql@.MSGPSBM\model
> 20030701 012357 16 Back up Session 9 on Media Monthly2
> 20030701 012400 16 1 Databases/Transaction Logs (721 KB) Backed Up to
> Media.
> 20030701 012400 16 768 KB Written to Media.
> 20030701 012400 16 Elapsed Time: 1s
> 20030701 012400 16 Average Throughput: 45.00 MB/min
> 20030701 012400 16 Source Directory: dbasql@.MSGPSBM\master
> 20030701 012400 16 Back up Session 10 on Media Monthly2
> 20030701 012407 16 1 Databases/Transaction Logs (10.51 MB) Backed Up
> to Media.
> 20030701 012407 16 10.56 MB Written to Media.
> 20030701 012407 16 Elapsed Time: 0s
> 20030701 012407 16 Average Throughput: 633.75 MB/min
> 20030701 012407 16 Source Directory: dbasql@.MSGPSBM\DYNAMICS
> 20030701 012407 16 Back up Session 11 on Media Monthly2
> 20030701 012412 16 1 Databases/Transaction Logs (29.95 MB) Backed Up
> to Media.
> 20030701 012412 16 30.00 MB Written to Media.
> 20030701 012412 16 Elapsed Time: 3s
> 20030701 012412 16 Average Throughput: 600.00 MB/min
> 20030701 012413 16 Source Directory: System State
> 20030701 012413 16 Back up Session 12 on Media Monthly2
> 20030701 012413 16 Backing Up Files : Boot and System Protected Files
> 20030701 012445 16 Backing Up Files : Active Directory
> 20030701 012448 16 Backing Up Files : SysVol
> 20030701 012448 16 Backing Up Files : COM+ Class Registration Database
> 20030701 012448 16 Backing Up Files : Registry
> 20030701 012455 16 Registry Files Backed Up
> 20030701 012455 16 91 Directories 1,963 Files (287.99 MB) Backed Up to
> Media.
> 20030701 012455 16 294.56 MB Written to Media.
> 20030701 012455 16 Elapsed Time: 39s
> 20030701 012455 16 Average Throughput: 453.17 MB/min
> 20030701 012455 16 Source Directory: dbaxchg2
> 20030701 012455 16 Back up Session 13 on Media Monthly2
> 20030701 012516 16 11 Databases/Transaction Logs (40.19 MB) Backed Up
> to Media.
> 20030701 012516 16 40.50 MB Written to Media.
> 20030701 012516 16 Elapsed Time: 19s
> 20030701 012516 16 Average Throughput: 127.89 MB/min
> 20030701 012516 16 ** Summary for My Computer **
> 20030701 012516 16 13 Sessions.
> 20030701 012516 16 61,314 Directories 149,750 Files (6,198.15 MB)
> Backed Up to Media.
> 20030701 012516 16 18 Databases/Transaction Logs (824.89 MB) Backed Up
> to Media.
> 20030701 012516 16 8 Directories/Files Skipped.
> 20030701 012516 16 7,601.50 MB Written to Media.
> 20030701 012516 16 Elapsed Time: 22m 14s
> 20030701 012516 16 Average Throughput: 341.89 MB/min
> 20030701 012516 16 Number of Errors/Warnings: 0/8
> 20030701 012519 16 Backup ARCserve Database...
> 20030701 012520 16 Source Directory: C:\Program
> Files\ComputerAssociates\ARCserve\DATABASE
> 20030701 012520 16 Back up Session 14 on Media Monthly2
> 20030701 012529 16 Catalog File Backed Up
> 20030701 012529 16 1 Directories 118 Files (104.17 MB) Backed Up to
> Media.
> 20030701 012529 16 104.62 MB Written to Media.
> 20030701 012529 16 Elapsed Time: 7s
> 20030701 012529 16 Average Throughput: 896.78 MB/min
> 20030701 012529 16 ARCServe Database Backed Up
> 20030701 012538 [CAT] Monthly2 [ID:2542,SESSION:1] is
> merged.(files=17088)
> 20030701 012542 [CAT] Monthly2 [ID:2542,SESSION:2] is
> merged.(files=11142)
> 20030701 012555 [CAT] Monthly2 [ID:2542,SESSION:3] is
> merged.(files=23262)
> 20030701 012631 16 ** Summary for Job **
> 20030701 012631 16 14 Sessions.
> 20030701 012631 16 61,315 Directories 149,868 Files (6,302.33 MB)
> Backed Up to Media.
> 20030701 012631 16 18 Databases/Transaction Logs (824.89 MB) Backed Up
> to Media.
> 20030701 012631 16 8 Directories/Files Skipped.
> 20030701 012631 16 7,706.12 MB Written to Media.
> 20030701 012631 16 Elapsed Time: 22m 21s
> 20030701 012631 16 Average Throughput: 344.79 MB/min
> 20030701 012631 16 Number of Errors/Warnings: 0/8
> 20030701 012631 16 Backup Operation Incomplete.
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:4] is
> merged.(files=96295)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:5] is merged.(files=5)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:6] is merged.(files=3)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:7] is merged.(files=3)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:8] is merged.(files=3)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:9] is merged.(files=3)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:10] is
> merged.(files=3)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:11] is
> merged.(files=3)
> 20030701 012708 [CAT] Monthly2 [ID:2542,SESSION:12] is
> merged.(files=1963)
> 20030701 012708 [CAT] Monthly2 [ID:2542,SESSION:13] is
> merged.(files=110)
> 20030701 012708 [CAT] Monthly2 [ID:2542,SESSION:14] is
> merged.(files=118)
> 20030701 012709 16 Reschedule Backup Job for 7/02/03 at 1:00 AM.|||Hello,
Arcserver has an Open File Agent, as do most of these large backup software
products. This is supposed to allow the backing up of files that Andrew
says are always in use. It is my experience that this can be a hit and miss
affair and is one that I am not comfortable with. Yes I have been bitten by
it. I always now backup using SQL Server to a .bak file and have Arcserve.*
back that file up.
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
: You can't normally backup the database files with ArcServe since they are
: always in use. I believe they have a way to bypass that but then what
good
: is backing up a file that is constantly changing. You can't restore the
db
: using these backups made from Arcserve since they are not consistent.
What
: you can do is basically one of 2 things. Either use the SQL Server
plug-in
: for ArcServe to have it issue the equivalent of a sql server backup or
don't
: even attempt to backup the database files with Arcserve and have it backup
: the files generated by the SQL Server backup.
-- Microsoft Outlook Express 6.00.2800.1158|||Yes that is what I meant by bypass. Poor choice of word but it will allow
it to backup up the file anyway. That does no one any good since it is in
an inconsistent state database wise.
--
Andrew J. Kelly
SQL Server MVP
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:OK7gauSQDHA.2852@.tk2msftngp13.phx.gbl...
> Hello,
> Arcserver has an Open File Agent, as do most of these large backup
software
> products. This is supposed to allow the backing up of files that Andrew
> says are always in use. It is my experience that this can be a hit and
miss
> affair and is one that I am not comfortable with. Yes I have been bitten
by
> it. I always now backup using SQL Server to a .bak file and have
Arcserve.*
> back that file up.
>
> --
> Allan Mitchell (Microsoft SQL Server MVP)
> MCSE,MCDBA
> www.SQLDTS.com
> I support PASS - the definitive, global community
> for SQL Server professionals - http://www.sqlpass.org
> : You can't normally backup the database files with ArcServe since they
are
> : always in use. I believe they have a way to bypass that but then what
> good
> : is backing up a file that is constantly changing. You can't restore the
> db
> : using these backups made from Arcserve since they are not consistent.
> What
> : you can do is basically one of 2 things. Either use the SQL Server
> plug-in
> : for ArcServe to have it issue the equivalent of a sql server backup or
> don't
> : even attempt to backup the database files with Arcserve and have it
backup
> : the files generated by the SQL Server backup.
> -- Microsoft Outlook Express 6.00.2800.1158
>|||it might behoove you to test the viability of your recovery resources.
"Devin G" <devin@.spamhole.com> wrote in message
news:495ba422.0307031210.57474c7@.posting.google.com...
> From what I think:
> 1) The error messages during the beginning are because Arcserve is
> trying to backup the files on C:. These particular files are skipped
> doe to them being open and in use.
> 2) Later on during the backup I -think- Arcserve is backing up the
> database using the SQL agent which I installed. I can see that in the
> log.
>
> I was just wondering if this looks normal. Has anyone else used
> Arcserve? Is it normal to have the files skipped during the C: but
> then (it looks like) backed up during the SQL agent runs?
> Thanks|||I agree with that assessment but like I said, why bother to have it attempt
to backup those files (in the beginning) if you know they will only fail and
are useless anyway? And as nttp states, it wouldn't be a bad idea to
restore your backups somewhere to see if it's really doing what you hope it
is.
--
Andrew J. Kelly
SQL Server MVP
"Devin G" <devin@.spamhole.com> wrote in message
news:495ba422.0307031210.57474c7@.posting.google.com...
> From what I think:
> 1) The error messages during the beginning are because Arcserve is
> trying to backup the files on C:. These particular files are skipped
> doe to them being open and in use.
> 2) Later on during the backup I -think- Arcserve is backing up the
> database using the SQL agent which I installed. I can see that in the
> log.
>
> I was just wondering if this looks normal. Has anyone else used
> Arcserve? Is it normal to have the files skipped during the C: but
> then (it looks like) backed up during the SQL agent runs?
> Thanks
is running SQL server. It seems that at the beginning of the backup
cycle the files are skipped due to a sharing violation (I mean the
database files). Later during the part when the SQL agent backs up
files it seems to back up fine. Is this normal or is something wrong
here. Below is a log...sorry if it is a little long. Thanks so much
for youe help.
20030701 010009 16 Run Backup Job Scheduled for 7/01/03 at 1:00 AM.
20030701 010009 16 Start Backup Operation. (QUEUE=1, JOB=2)
20030701 010010 16 Overwrite media Monthly2, ID DBA9, sequence #1
20030701 010037 TAPE Tape Engine finished formatting media.(new name:
Monthly2, old name: Monthly2)
20030701 010037 Begin cleaning database.
20030701 010044 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=1, RECS=18130)
20030701 010047 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=2, RECS=11705)
20030701 010048 TAPE Format Successful!
20030701 010048 16 Use media Monthly2, ID 2542, sequence #1
20030701 010054 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=3, RECS=27896)
20030701 010129 16 Source Directory: C:
20030701 010129 16 Back up Session 1 on Media Monthly2
20030701 010129 16 Backed up volume disk quota.
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=4, RECS=151242)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=5, RECS=7)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=6, RECS=12)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=7, RECS=12)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=8, RECS=12)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=9, RECS=12)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=10, RECS=12)
20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=11, RECS=12)
20030701 010159 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=12, RECS=13291)
20030701 010159 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=13, RECS=225)
20030701 010159 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
SES=14, RECS=123)
20030701 010159 End cleaning database. (CLEANED=222691)
20030701 010233 16 W3404 Unable to open file. (FILE=C:\Documents and
Settings\All Users\Application
Data\Microsoft\Network\Downloader\qmgr0.dat, EC=SHARING VIOLATION)
20030701 010233 16 W3404 Unable to open file. (FILE=C:\Documents and
Settings\All Users\Application
Data\Microsoft\Network\Downloader\qmgr1.dat, EC=SHARING VIOLATION)
20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSDYNAMICSDat.mdf,
EC=SHARING VIOLATION)
20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSDYNAMICSLog.ldf,
EC=SHARING VIOLATION)
20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSSBM01Dat.mdf,
EC=SHARING VIOLATION)
20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSSBM01Log.ldf,
EC=SHARING VIOLATION)
20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSTWODat.mdf,
EC=SHARING VIOLATION)
20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSTWOLog.ldf,
EC=SHARING VIOLATION)
20030701 010601 16 Catalog File Backed Up
20030701 010601 16 Registry Files Backed Up
20030701 010601 16 1,049 Directories 17,088 Files (1,404.55 MB) Backed
Up to Media.
20030701 010601 16 8 Directories/Files Skipped.
20030701 010601 16 1,463.31 MB Written to Media.
20030701 010601 16 Elapsed Time: 4m 30s
20030701 010601 16 Average Throughput: 325.17 MB/min
20030701 010601 16 Number of Errors/Warnings: 0/8
20030701 010611 16 Source Directory: E:
20030701 010611 16 Back up Session 2 on Media Monthly2
20030701 010611 16 Backed up volume disk quota.
20030701 011115 16 Catalog File Backed Up
20030701 011115 16 563 Directories 11,142 Files (1,254.87 MB) Backed
Up to Media.
20030701 011115 16 1,292.68 MB Written to Media.
20030701 011115 16 Elapsed Time: 5m 0s
20030701 011115 16 Average Throughput: 258.53 MB/min
20030701 011201 16 Source Directory: F:
20030701 011201 16 Back up Session 3 on Media Monthly2
20030701 011201 16 Backed up volume disk quota.
20030701 012213 16 Catalog File Backed Up
20030701 012213 16 4,665 Directories 23,262 Files (3,229.25 MB) Backed
Up to Media.
20030701 012213 16 3,320.18 MB Written to Media.
20030701 012213 16 Elapsed Time: 10m 9s
20030701 012213 16 Average Throughput: 327.11 MB/min
20030701 012213 16 Source Directory: Registry
20030701 012213 16 Back up Session 4 on Media Monthly2
20030701 012244 16 Registry Files Backed Up
20030701 012244 16 54,946 Directories 96,295 Files (21.42 MB) Backed
Up to Media.
20030701 012244 16 404.87 MB Written to Media.
20030701 012244 16 Elapsed Time: 28s
20030701 012244 16 Average Throughput: 867.58 MB/min
20030701 012244 16 Source Directory: dbaexchis\First Storage Group
20030701 012244 16 Back up Session 5 on Media Monthly2
20030701 012301 16 1 Databases/Transaction Logs (103.04 MB) Backed Up
to Media.
20030701 012301 16 103.12 MB Written to Media.
20030701 012301 16 Elapsed Time: 15s
20030701 012301 16 Average Throughput: 412.50 MB/min
20030701 012302 16 Source Directory: dbasql@.MSGPSBM\TWO
20030701 012302 16 Back up Session 6 on Media Monthly2
20030701 012311 16 1 Databases/Transaction Logs (90.07 MB) Backed Up
to Media.
20030701 012311 16 90.18 MB Written to Media.
20030701 012311 16 Elapsed Time: 7s
20030701 012311 16 Average Throughput: 773.03 MB/min
20030701 012311 16 Source Directory: dbasql@.MSGPSBM\SBM01
20030701 012311 16 Back up Session 7 on Media Monthly2
20030701 012355 16 1 Databases/Transaction Logs (548.07 MB) Backed Up
to Media.
20030701 012355 16 548.37 MB Written to Media.
20030701 012355 16 Elapsed Time: 42s
20030701 012355 16 Average Throughput: 783.39 MB/min
20030701 012355 16 Source Directory: dbasql@.MSGPSBM\msdb
20030701 012355 16 Back up Session 8 on Media Monthly2
20030701 012357 16 1 Databases/Transaction Logs (2.32 MB) Backed Up to
Media.
20030701 012357 16 2.37 MB Written to Media.
20030701 012357 16 Elapsed Time: 1s
20030701 012357 16 Average Throughput: 142.50 MB/min
20030701 012357 16 Source Directory: dbasql@.MSGPSBM\model
20030701 012357 16 Back up Session 9 on Media Monthly2
20030701 012400 16 1 Databases/Transaction Logs (721 KB) Backed Up to
Media.
20030701 012400 16 768 KB Written to Media.
20030701 012400 16 Elapsed Time: 1s
20030701 012400 16 Average Throughput: 45.00 MB/min
20030701 012400 16 Source Directory: dbasql@.MSGPSBM\master
20030701 012400 16 Back up Session 10 on Media Monthly2
20030701 012407 16 1 Databases/Transaction Logs (10.51 MB) Backed Up
to Media.
20030701 012407 16 10.56 MB Written to Media.
20030701 012407 16 Elapsed Time: 0s
20030701 012407 16 Average Throughput: 633.75 MB/min
20030701 012407 16 Source Directory: dbasql@.MSGPSBM\DYNAMICS
20030701 012407 16 Back up Session 11 on Media Monthly2
20030701 012412 16 1 Databases/Transaction Logs (29.95 MB) Backed Up
to Media.
20030701 012412 16 30.00 MB Written to Media.
20030701 012412 16 Elapsed Time: 3s
20030701 012412 16 Average Throughput: 600.00 MB/min
20030701 012413 16 Source Directory: System State
20030701 012413 16 Back up Session 12 on Media Monthly2
20030701 012413 16 Backing Up Files : Boot and System Protected Files
20030701 012445 16 Backing Up Files : Active Directory
20030701 012448 16 Backing Up Files : SysVol
20030701 012448 16 Backing Up Files : COM+ Class Registration Database
20030701 012448 16 Backing Up Files : Registry
20030701 012455 16 Registry Files Backed Up
20030701 012455 16 91 Directories 1,963 Files (287.99 MB) Backed Up to
Media.
20030701 012455 16 294.56 MB Written to Media.
20030701 012455 16 Elapsed Time: 39s
20030701 012455 16 Average Throughput: 453.17 MB/min
20030701 012455 16 Source Directory: dbaxchg2
20030701 012455 16 Back up Session 13 on Media Monthly2
20030701 012516 16 11 Databases/Transaction Logs (40.19 MB) Backed Up
to Media.
20030701 012516 16 40.50 MB Written to Media.
20030701 012516 16 Elapsed Time: 19s
20030701 012516 16 Average Throughput: 127.89 MB/min
20030701 012516 16 ** Summary for My Computer **
20030701 012516 16 13 Sessions.
20030701 012516 16 61,314 Directories 149,750 Files (6,198.15 MB)
Backed Up to Media.
20030701 012516 16 18 Databases/Transaction Logs (824.89 MB) Backed Up
to Media.
20030701 012516 16 8 Directories/Files Skipped.
20030701 012516 16 7,601.50 MB Written to Media.
20030701 012516 16 Elapsed Time: 22m 14s
20030701 012516 16 Average Throughput: 341.89 MB/min
20030701 012516 16 Number of Errors/Warnings: 0/8
20030701 012519 16 Backup ARCserve Database...
20030701 012520 16 Source Directory: C:\Program
Files\ComputerAssociates\ARCserve\DATABASE
20030701 012520 16 Back up Session 14 on Media Monthly2
20030701 012529 16 Catalog File Backed Up
20030701 012529 16 1 Directories 118 Files (104.17 MB) Backed Up to
Media.
20030701 012529 16 104.62 MB Written to Media.
20030701 012529 16 Elapsed Time: 7s
20030701 012529 16 Average Throughput: 896.78 MB/min
20030701 012529 16 ARCServe Database Backed Up
20030701 012538 [CAT] Monthly2 [ID:2542,SESSION:1] is
merged.(files=17088)
20030701 012542 [CAT] Monthly2 [ID:2542,SESSION:2] is
merged.(files=11142)
20030701 012555 [CAT] Monthly2 [ID:2542,SESSION:3] is
merged.(files=23262)
20030701 012631 16 ** Summary for Job **
20030701 012631 16 14 Sessions.
20030701 012631 16 61,315 Directories 149,868 Files (6,302.33 MB)
Backed Up to Media.
20030701 012631 16 18 Databases/Transaction Logs (824.89 MB) Backed Up
to Media.
20030701 012631 16 8 Directories/Files Skipped.
20030701 012631 16 7,706.12 MB Written to Media.
20030701 012631 16 Elapsed Time: 22m 21s
20030701 012631 16 Average Throughput: 344.79 MB/min
20030701 012631 16 Number of Errors/Warnings: 0/8
20030701 012631 16 Backup Operation Incomplete.
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:4] is
merged.(files=96295)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:5] is merged.(files=5)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:6] is merged.(files=3)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:7] is merged.(files=3)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:8] is merged.(files=3)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:9] is merged.(files=3)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:10] is
merged.(files=3)
20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:11] is
merged.(files=3)
20030701 012708 [CAT] Monthly2 [ID:2542,SESSION:12] is
merged.(files=1963)
20030701 012708 [CAT] Monthly2 [ID:2542,SESSION:13] is
merged.(files=110)
20030701 012708 [CAT] Monthly2 [ID:2542,SESSION:14] is
merged.(files=118)
20030701 012709 16 Reschedule Backup Job for 7/02/03 at 1:00 AM.You can't normally backup the database files with ArcServe since they are
always in use. I believe they have a way to bypass that but then what good
is backing up a file that is constantly changing. You can't restore the db
using these backups made from Arcserve since they are not consistent. What
you can do is basically one of 2 things. Either use the SQL Server plug-in
for ArcServe to have it issue the equivalent of a sql server backup or don't
even attempt to backup the database files with Arcserve and have it backup
the files generated by the SQL Server backup.
--
Andrew J. Kelly
SQL Server MVP
"Devin G" <devin@.spamhole.com> wrote in message
news:495ba422.0307021902.4a418a32@.posting.google.com...
> I recently installed arcserve small business version for a client who
> is running SQL server. It seems that at the beginning of the backup
> cycle the files are skipped due to a sharing violation (I mean the
> database files). Later during the part when the SQL agent backs up
> files it seems to back up fine. Is this normal or is something wrong
> here. Below is a log...sorry if it is a little long. Thanks so much
> for youe help.
>
> 20030701 010009 16 Run Backup Job Scheduled for 7/01/03 at 1:00 AM.
> 20030701 010009 16 Start Backup Operation. (QUEUE=1, JOB=2)
> 20030701 010010 16 Overwrite media Monthly2, ID DBA9, sequence #1
> 20030701 010037 TAPE Tape Engine finished formatting media.(new name:
> Monthly2, old name: Monthly2)
> 20030701 010037 Begin cleaning database.
> 20030701 010044 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=1, RECS=18130)
> 20030701 010047 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=2, RECS=11705)
> 20030701 010048 TAPE Format Successful!
> 20030701 010048 16 Use media Monthly2, ID 2542, sequence #1
> 20030701 010054 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=3, RECS=27896)
> 20030701 010129 16 Source Directory: C:
> 20030701 010129 16 Back up Session 1 on Media Monthly2
> 20030701 010129 16 Backed up volume disk quota.
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=4, RECS=151242)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=5, RECS=7)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=6, RECS=12)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=7, RECS=12)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=8, RECS=12)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=9, RECS=12)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=10, RECS=12)
> 20030701 010154 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=11, RECS=12)
> 20030701 010159 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=12, RECS=13291)
> 20030701 010159 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=13, RECS=225)
> 20030701 010159 Session is cleaned. (MEDIA=Monthly2, ID=FFFFDBA9,
> SES=14, RECS=123)
> 20030701 010159 End cleaning database. (CLEANED=222691)
> 20030701 010233 16 W3404 Unable to open file. (FILE=C:\Documents and
> Settings\All Users\Application
> Data\Microsoft\Network\Downloader\qmgr0.dat, EC=SHARING VIOLATION)
> 20030701 010233 16 W3404 Unable to open file. (FILE=C:\Documents and
> Settings\All Users\Application
> Data\Microsoft\Network\Downloader\qmgr1.dat, EC=SHARING VIOLATION)
> 20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
> Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSDYNAMICSDat.mdf,
> EC=SHARING VIOLATION)
> 20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
> Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSDYNAMICSLog.ldf,
> EC=SHARING VIOLATION)
> 20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
> Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSSBM01Dat.mdf,
> EC=SHARING VIOLATION)
> 20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
> Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSSBM01Log.ldf,
> EC=SHARING VIOLATION)
> 20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
> Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSTWODat.mdf,
> EC=SHARING VIOLATION)
> 20030701 010338 16 W3404 Unable to open file. (FILE=C:\Program
> Files\Microsoft SQL Server\MSSQL$MSGPSBM\Data\GPSTWOLog.ldf,
> EC=SHARING VIOLATION)
> 20030701 010601 16 Catalog File Backed Up
> 20030701 010601 16 Registry Files Backed Up
> 20030701 010601 16 1,049 Directories 17,088 Files (1,404.55 MB) Backed
> Up to Media.
> 20030701 010601 16 8 Directories/Files Skipped.
> 20030701 010601 16 1,463.31 MB Written to Media.
> 20030701 010601 16 Elapsed Time: 4m 30s
> 20030701 010601 16 Average Throughput: 325.17 MB/min
> 20030701 010601 16 Number of Errors/Warnings: 0/8
> 20030701 010611 16 Source Directory: E:
> 20030701 010611 16 Back up Session 2 on Media Monthly2
> 20030701 010611 16 Backed up volume disk quota.
> 20030701 011115 16 Catalog File Backed Up
> 20030701 011115 16 563 Directories 11,142 Files (1,254.87 MB) Backed
> Up to Media.
> 20030701 011115 16 1,292.68 MB Written to Media.
> 20030701 011115 16 Elapsed Time: 5m 0s
> 20030701 011115 16 Average Throughput: 258.53 MB/min
> 20030701 011201 16 Source Directory: F:
> 20030701 011201 16 Back up Session 3 on Media Monthly2
> 20030701 011201 16 Backed up volume disk quota.
> 20030701 012213 16 Catalog File Backed Up
> 20030701 012213 16 4,665 Directories 23,262 Files (3,229.25 MB) Backed
> Up to Media.
> 20030701 012213 16 3,320.18 MB Written to Media.
> 20030701 012213 16 Elapsed Time: 10m 9s
> 20030701 012213 16 Average Throughput: 327.11 MB/min
> 20030701 012213 16 Source Directory: Registry
> 20030701 012213 16 Back up Session 4 on Media Monthly2
> 20030701 012244 16 Registry Files Backed Up
> 20030701 012244 16 54,946 Directories 96,295 Files (21.42 MB) Backed
> Up to Media.
> 20030701 012244 16 404.87 MB Written to Media.
> 20030701 012244 16 Elapsed Time: 28s
> 20030701 012244 16 Average Throughput: 867.58 MB/min
> 20030701 012244 16 Source Directory: dbaexchis\First Storage Group
> 20030701 012244 16 Back up Session 5 on Media Monthly2
> 20030701 012301 16 1 Databases/Transaction Logs (103.04 MB) Backed Up
> to Media.
> 20030701 012301 16 103.12 MB Written to Media.
> 20030701 012301 16 Elapsed Time: 15s
> 20030701 012301 16 Average Throughput: 412.50 MB/min
> 20030701 012302 16 Source Directory: dbasql@.MSGPSBM\TWO
> 20030701 012302 16 Back up Session 6 on Media Monthly2
> 20030701 012311 16 1 Databases/Transaction Logs (90.07 MB) Backed Up
> to Media.
> 20030701 012311 16 90.18 MB Written to Media.
> 20030701 012311 16 Elapsed Time: 7s
> 20030701 012311 16 Average Throughput: 773.03 MB/min
> 20030701 012311 16 Source Directory: dbasql@.MSGPSBM\SBM01
> 20030701 012311 16 Back up Session 7 on Media Monthly2
> 20030701 012355 16 1 Databases/Transaction Logs (548.07 MB) Backed Up
> to Media.
> 20030701 012355 16 548.37 MB Written to Media.
> 20030701 012355 16 Elapsed Time: 42s
> 20030701 012355 16 Average Throughput: 783.39 MB/min
> 20030701 012355 16 Source Directory: dbasql@.MSGPSBM\msdb
> 20030701 012355 16 Back up Session 8 on Media Monthly2
> 20030701 012357 16 1 Databases/Transaction Logs (2.32 MB) Backed Up to
> Media.
> 20030701 012357 16 2.37 MB Written to Media.
> 20030701 012357 16 Elapsed Time: 1s
> 20030701 012357 16 Average Throughput: 142.50 MB/min
> 20030701 012357 16 Source Directory: dbasql@.MSGPSBM\model
> 20030701 012357 16 Back up Session 9 on Media Monthly2
> 20030701 012400 16 1 Databases/Transaction Logs (721 KB) Backed Up to
> Media.
> 20030701 012400 16 768 KB Written to Media.
> 20030701 012400 16 Elapsed Time: 1s
> 20030701 012400 16 Average Throughput: 45.00 MB/min
> 20030701 012400 16 Source Directory: dbasql@.MSGPSBM\master
> 20030701 012400 16 Back up Session 10 on Media Monthly2
> 20030701 012407 16 1 Databases/Transaction Logs (10.51 MB) Backed Up
> to Media.
> 20030701 012407 16 10.56 MB Written to Media.
> 20030701 012407 16 Elapsed Time: 0s
> 20030701 012407 16 Average Throughput: 633.75 MB/min
> 20030701 012407 16 Source Directory: dbasql@.MSGPSBM\DYNAMICS
> 20030701 012407 16 Back up Session 11 on Media Monthly2
> 20030701 012412 16 1 Databases/Transaction Logs (29.95 MB) Backed Up
> to Media.
> 20030701 012412 16 30.00 MB Written to Media.
> 20030701 012412 16 Elapsed Time: 3s
> 20030701 012412 16 Average Throughput: 600.00 MB/min
> 20030701 012413 16 Source Directory: System State
> 20030701 012413 16 Back up Session 12 on Media Monthly2
> 20030701 012413 16 Backing Up Files : Boot and System Protected Files
> 20030701 012445 16 Backing Up Files : Active Directory
> 20030701 012448 16 Backing Up Files : SysVol
> 20030701 012448 16 Backing Up Files : COM+ Class Registration Database
> 20030701 012448 16 Backing Up Files : Registry
> 20030701 012455 16 Registry Files Backed Up
> 20030701 012455 16 91 Directories 1,963 Files (287.99 MB) Backed Up to
> Media.
> 20030701 012455 16 294.56 MB Written to Media.
> 20030701 012455 16 Elapsed Time: 39s
> 20030701 012455 16 Average Throughput: 453.17 MB/min
> 20030701 012455 16 Source Directory: dbaxchg2
> 20030701 012455 16 Back up Session 13 on Media Monthly2
> 20030701 012516 16 11 Databases/Transaction Logs (40.19 MB) Backed Up
> to Media.
> 20030701 012516 16 40.50 MB Written to Media.
> 20030701 012516 16 Elapsed Time: 19s
> 20030701 012516 16 Average Throughput: 127.89 MB/min
> 20030701 012516 16 ** Summary for My Computer **
> 20030701 012516 16 13 Sessions.
> 20030701 012516 16 61,314 Directories 149,750 Files (6,198.15 MB)
> Backed Up to Media.
> 20030701 012516 16 18 Databases/Transaction Logs (824.89 MB) Backed Up
> to Media.
> 20030701 012516 16 8 Directories/Files Skipped.
> 20030701 012516 16 7,601.50 MB Written to Media.
> 20030701 012516 16 Elapsed Time: 22m 14s
> 20030701 012516 16 Average Throughput: 341.89 MB/min
> 20030701 012516 16 Number of Errors/Warnings: 0/8
> 20030701 012519 16 Backup ARCserve Database...
> 20030701 012520 16 Source Directory: C:\Program
> Files\ComputerAssociates\ARCserve\DATABASE
> 20030701 012520 16 Back up Session 14 on Media Monthly2
> 20030701 012529 16 Catalog File Backed Up
> 20030701 012529 16 1 Directories 118 Files (104.17 MB) Backed Up to
> Media.
> 20030701 012529 16 104.62 MB Written to Media.
> 20030701 012529 16 Elapsed Time: 7s
> 20030701 012529 16 Average Throughput: 896.78 MB/min
> 20030701 012529 16 ARCServe Database Backed Up
> 20030701 012538 [CAT] Monthly2 [ID:2542,SESSION:1] is
> merged.(files=17088)
> 20030701 012542 [CAT] Monthly2 [ID:2542,SESSION:2] is
> merged.(files=11142)
> 20030701 012555 [CAT] Monthly2 [ID:2542,SESSION:3] is
> merged.(files=23262)
> 20030701 012631 16 ** Summary for Job **
> 20030701 012631 16 14 Sessions.
> 20030701 012631 16 61,315 Directories 149,868 Files (6,302.33 MB)
> Backed Up to Media.
> 20030701 012631 16 18 Databases/Transaction Logs (824.89 MB) Backed Up
> to Media.
> 20030701 012631 16 8 Directories/Files Skipped.
> 20030701 012631 16 7,706.12 MB Written to Media.
> 20030701 012631 16 Elapsed Time: 22m 21s
> 20030701 012631 16 Average Throughput: 344.79 MB/min
> 20030701 012631 16 Number of Errors/Warnings: 0/8
> 20030701 012631 16 Backup Operation Incomplete.
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:4] is
> merged.(files=96295)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:5] is merged.(files=5)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:6] is merged.(files=3)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:7] is merged.(files=3)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:8] is merged.(files=3)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:9] is merged.(files=3)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:10] is
> merged.(files=3)
> 20030701 012702 [CAT] Monthly2 [ID:2542,SESSION:11] is
> merged.(files=3)
> 20030701 012708 [CAT] Monthly2 [ID:2542,SESSION:12] is
> merged.(files=1963)
> 20030701 012708 [CAT] Monthly2 [ID:2542,SESSION:13] is
> merged.(files=110)
> 20030701 012708 [CAT] Monthly2 [ID:2542,SESSION:14] is
> merged.(files=118)
> 20030701 012709 16 Reschedule Backup Job for 7/02/03 at 1:00 AM.|||Hello,
Arcserver has an Open File Agent, as do most of these large backup software
products. This is supposed to allow the backing up of files that Andrew
says are always in use. It is my experience that this can be a hit and miss
affair and is one that I am not comfortable with. Yes I have been bitten by
it. I always now backup using SQL Server to a .bak file and have Arcserve.*
back that file up.
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
: You can't normally backup the database files with ArcServe since they are
: always in use. I believe they have a way to bypass that but then what
good
: is backing up a file that is constantly changing. You can't restore the
db
: using these backups made from Arcserve since they are not consistent.
What
: you can do is basically one of 2 things. Either use the SQL Server
plug-in
: for ArcServe to have it issue the equivalent of a sql server backup or
don't
: even attempt to backup the database files with Arcserve and have it backup
: the files generated by the SQL Server backup.
-- Microsoft Outlook Express 6.00.2800.1158|||Yes that is what I meant by bypass. Poor choice of word but it will allow
it to backup up the file anyway. That does no one any good since it is in
an inconsistent state database wise.
--
Andrew J. Kelly
SQL Server MVP
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:OK7gauSQDHA.2852@.tk2msftngp13.phx.gbl...
> Hello,
> Arcserver has an Open File Agent, as do most of these large backup
software
> products. This is supposed to allow the backing up of files that Andrew
> says are always in use. It is my experience that this can be a hit and
miss
> affair and is one that I am not comfortable with. Yes I have been bitten
by
> it. I always now backup using SQL Server to a .bak file and have
Arcserve.*
> back that file up.
>
> --
> Allan Mitchell (Microsoft SQL Server MVP)
> MCSE,MCDBA
> www.SQLDTS.com
> I support PASS - the definitive, global community
> for SQL Server professionals - http://www.sqlpass.org
> : You can't normally backup the database files with ArcServe since they
are
> : always in use. I believe they have a way to bypass that but then what
> good
> : is backing up a file that is constantly changing. You can't restore the
> db
> : using these backups made from Arcserve since they are not consistent.
> What
> : you can do is basically one of 2 things. Either use the SQL Server
> plug-in
> : for ArcServe to have it issue the equivalent of a sql server backup or
> don't
> : even attempt to backup the database files with Arcserve and have it
backup
> : the files generated by the SQL Server backup.
> -- Microsoft Outlook Express 6.00.2800.1158
>|||it might behoove you to test the viability of your recovery resources.
"Devin G" <devin@.spamhole.com> wrote in message
news:495ba422.0307031210.57474c7@.posting.google.com...
> From what I think:
> 1) The error messages during the beginning are because Arcserve is
> trying to backup the files on C:. These particular files are skipped
> doe to them being open and in use.
> 2) Later on during the backup I -think- Arcserve is backing up the
> database using the SQL agent which I installed. I can see that in the
> log.
>
> I was just wondering if this looks normal. Has anyone else used
> Arcserve? Is it normal to have the files skipped during the C: but
> then (it looks like) backed up during the SQL agent runs?
> Thanks|||I agree with that assessment but like I said, why bother to have it attempt
to backup those files (in the beginning) if you know they will only fail and
are useless anyway? And as nttp states, it wouldn't be a bad idea to
restore your backups somewhere to see if it's really doing what you hope it
is.
--
Andrew J. Kelly
SQL Server MVP
"Devin G" <devin@.spamhole.com> wrote in message
news:495ba422.0307031210.57474c7@.posting.google.com...
> From what I think:
> 1) The error messages during the beginning are because Arcserve is
> trying to backup the files on C:. These particular files are skipped
> doe to them being open and in use.
> 2) Later on during the backup I -think- Arcserve is backing up the
> database using the SQL agent which I installed. I can see that in the
> log.
>
> I was just wondering if this looks normal. Has anyone else used
> Arcserve? Is it normal to have the files skipped during the C: but
> then (it looks like) backed up during the SQL agent runs?
> Thanks
Subscribe to:
Posts (Atom)