Hello,
I have a question I hope can be answered fully.
Some time last year, I attended a Microsoft presentation in Dallas and a sql
server specialist from microsoft (I think his name was srikan) mentioned
during Q&A that SQL Server 2005 has peer-to-peer replication which is a
comparable solution to oracle's real application cluster with some
restriction.
I recently attended another presentation also at Microsoft but this time by
their partner that are suppose to be SQL server experts. This speaker said
that it is not a comparable solution. He gave several reasons and they
seemed to make sense but then again, a microsoft technical specialist said
differently last year.
Did the product change? Who should I listen to? My co-workers say I should
listen to microsoft because they created the product but the other guy seems
to know a lot also and said he used to be an oracle dba. I am confused.
Anybody can help here? I don't want to ask Oracle because they want a lot of
information from me before they will answer and their newsgroup people are
quite unfriendly.
Thank you.
aK.
No, peer-to-peer replication is not a replacement to RAC. Unfortunately,
the TS would be wrong in a literal interpretation. If you look at the basic
data flow, there is some similarity in the solution which disappears when
you start looking a lot deeper.
I don't know a huge amount about RAC, but I understand the basics. With RAC
you are essentially plugging N servers into an Oracle architecture that
access a single database. What you wind up with is theoretically pooling
all of your hardware resources together (memory, processors, network I/O)
which can be basically treated by an application as a single massive server.
They still point to a single database on the backend. You still have to
deal with all of the issues related to changes coming from multiple servers
into a single database which now has to resolve conflicting changes on the
fly and several other implementation related issues.
Peer-to-peer replication is a logical extension to bi-directional
transactional replication. This handles the data layer only. The
replication engine is used to replicate like it says "from everyone - to
everyone". There is ZERO conflict detection or resolution, so your data
changes must be partitioned. If two users were to change the same piece of
data on different servers at the same time, it would create a huge
synchronization issue.
What problem are you trying to solve?
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Angie" <NO_Angie_Kong_SPAM@.hotmail.com> wrote in message
news:ORao5BrMGHA.648@.TK2MSFTNGP14.phx.gbl...
> Hello,
> I have a question I hope can be answered fully.
> Some time last year, I attended a Microsoft presentation in Dallas and a
> sql server specialist from microsoft (I think his name was srikan)
> mentioned during Q&A that SQL Server 2005 has peer-to-peer replication
> which is a comparable solution to oracle's real application cluster with
> some restriction.
> I recently attended another presentation also at Microsoft but this time
> by their partner that are suppose to be SQL server experts. This speaker
> said that it is not a comparable solution. He gave several reasons and
> they seemed to make sense but then again, a microsoft technical specialist
> said differently last year.
> Did the product change? Who should I listen to? My co-workers say I should
> listen to microsoft because they created the product but the other guy
> seems to know a lot also and said he used to be an oracle dba. I am
> confused.
> Anybody can help here? I don't want to ask Oracle because they want a lot
> of information from me before they will answer and their newsgroup people
> are quite unfriendly.
> Thank you.
>
> aK.
>
sql
Showing posts with label application. Show all posts
Showing posts with label application. Show all posts
Friday, March 30, 2012
Peculiar problem with seemingly identical data
Hello,
I have this peculiar problem concerning MS SQL Server.
My company works with an mailing application (ASP) which uses SQL
Server as it's repository. What I want to do is send data directly
from my own application to this SQL Server in order to feed the
mailing application.
To test if this was possible I linked the tables from SQL Server in MS
Access and entered the data. This worked fine and the data was picked
up correctly by the mailing application.
The problem occurs when I send the data from my application (Java
application with JDBC connection). The data is in this case no longer
picked up by the application. The strange thing is that the data which
is entered through Access and the data from the Application look
identical in de database view. The problem also occurs when the data
is send with the tool winSQL and when I view the data in here it still
looks identical.
Even more strange is when I select the record which is not working in
Access and copy it into a new record (only changing the key) it
suddenly works!
Has anyone have an idea how this can be?
Thanks in advance,
Sander Janssen.Sander Janssen (sjanssen@.plex.nl) writes:
> My company works with an mailing application (ASP) which uses SQL
> Server as it's repository. What I want to do is send data directly
> from my own application to this SQL Server in order to feed the
> mailing application.
> To test if this was possible I linked the tables from SQL Server in MS
> Access and entered the data. This worked fine and the data was picked
> up correctly by the mailing application.
> The problem occurs when I send the data from my application (Java
> application with JDBC connection). The data is in this case no longer
> picked up by the application. The strange thing is that the data which
> is entered through Access and the data from the Application look
> identical in de database view. The problem also occurs when the data
> is send with the tool winSQL and when I view the data in here it still
> looks identical.
> Even more strange is when I select the record which is not working in
> Access and copy it into a new record (only changing the key) it
> suddenly works!
I don't have a clue. The thing is, I have no idea by which criterias
your application is picking up data. You need to find this out one
way or another. One way to do this is to use the Profiler to catch
which SQL it is using.
--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Which JDBC Driver and what version of SQL Server?
"Sander Janssen" <sjanssen@.plex.nl> wrote in message
news:e3b8d8ea.0307040443.5bc4a8d@.posting.google.co m...
> Hello,
> I have this peculiar problem concerning MS SQL Server.
> My company works with an mailing application (ASP) which uses SQL
> Server as it's repository. What I want to do is send data directly
> from my own application to this SQL Server in order to feed the
> mailing application.
> To test if this was possible I linked the tables from SQL Server in MS
> Access and entered the data. This worked fine and the data was picked
> up correctly by the mailing application.
> The problem occurs when I send the data from my application (Java
> application with JDBC connection). The data is in this case no longer
> picked up by the application. The strange thing is that the data which
> is entered through Access and the data from the Application look
> identical in de database view. The problem also occurs when the data
> is send with the tool winSQL and when I view the data in here it still
> looks identical.
> Even more strange is when I select the record which is not working in
> Access and copy it into a new record (only changing the key) it
> suddenly works!
> Has anyone have an idea how this can be?
> Thanks in advance,
> Sander Janssen.|||Hello,
I have found the source of the problem. It isn't as peculiar as I
thought at first though. The problem was that I wrote a date to an
identifier field and the characters ":" were the source of the problem
in the mailing application. When I replaced them with underscores it
all works fine!
Thanks for your help anyway!
Sander Janssen.
pdf-files in full-text-search
Hallo, I tryed to add pdf-files that are stored in a image-column to
full-text-search. As mime-type in the "data type column" I used
"application/pdf". So, I can see at the "unique key count" that the
files are read from the index but I can't find anything in the files by
searching with contains(). Whats wrong? Is the data type not the right.
Is there a generally problem with pdf? Thanks in advance, Silvio
Hi Hilary, thanks for your help. I still found the right way to do this
here: http://weblogs.asp.net/wallym/archiv...28/382060.aspx
Now it works fine.
full-text-search. As mime-type in the "data type column" I used
"application/pdf". So, I can see at the "unique key count" that the
files are read from the index but I can't find anything in the files by
searching with contains(). Whats wrong? Is the data type not the right.
Is there a generally problem with pdf? Thanks in advance, Silvio
Hi Hilary, thanks for your help. I still found the right way to do this
here: http://weblogs.asp.net/wallym/archiv...28/382060.aspx
Now it works fine.
PDF Sizes
Hello,
I am using ReportViewer in a web application. When there is a chart as part
of a report and it is exported to PDF the file size is very large for a
single page; typically 10-12 Mb.
I am now supposed to manufacture a report that will be about 50 pages with a
large graph on each page and I don't thing a 500Mb file size is acceptable.
Isn't there a way for the charts to use a vector format instead or at least
a compressed format?
Thanks,
JohnHello John,
Thank you for using Microsoft MSDN newsgroup!
I understand that you'd like to know if charts in report could be
compressed or use a vector format when exporting to PDF. If I'm off-base,
please let me know.
This behavior is a limitation of the product and we have received similar
request from another customer. However, currently there is no option to
compress charts or use a vector format for charts as you want for local
report.
The major difference for PDF rendering for the local report is that PDF
doesn't support compression of data while rendering. So it will take long
time when compared to the one from the server PDF rendering. But this
limitation is only for PDF and for other rendering extensions like Excel
etc don't have difference in behavior from the local and the server reports.
Verifying with our Development Team, I found that resolution is also not a
configurable setting for the PDF renderer. The documentation link which I
sent earlier
incorrectly lists DpiX and DpiY as available Device Information settings
for PDF.
<http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsprog/htm
/rsp_prog_soapapi_dev_8bld.asp>
This documentation was corrected later for RS 2005 version:
<http://msdn2.microsoft.com/en-us/library/ms154682.aspx>
So unfortunately the DpiX and DpiY settings will have no effect when passed
to Render method.
Please rest assured your feedback on this is reported to the proper
channel. In the meantime, I also encourage you submit via the link below so
that product team could hear your sound directly:
http://lab.msdn.microsoft.com/productfeedback/default.aspx
You may want to consider using Excel rendering method but it may not meet
your requriment exactly. Or you may want to consider using a report server
to render the report for you other than using a local report.
If you have any questions or concerns on this, please feel free to let us
know.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.sql
I am using ReportViewer in a web application. When there is a chart as part
of a report and it is exported to PDF the file size is very large for a
single page; typically 10-12 Mb.
I am now supposed to manufacture a report that will be about 50 pages with a
large graph on each page and I don't thing a 500Mb file size is acceptable.
Isn't there a way for the charts to use a vector format instead or at least
a compressed format?
Thanks,
JohnHello John,
Thank you for using Microsoft MSDN newsgroup!
I understand that you'd like to know if charts in report could be
compressed or use a vector format when exporting to PDF. If I'm off-base,
please let me know.
This behavior is a limitation of the product and we have received similar
request from another customer. However, currently there is no option to
compress charts or use a vector format for charts as you want for local
report.
The major difference for PDF rendering for the local report is that PDF
doesn't support compression of data while rendering. So it will take long
time when compared to the one from the server PDF rendering. But this
limitation is only for PDF and for other rendering extensions like Excel
etc don't have difference in behavior from the local and the server reports.
Verifying with our Development Team, I found that resolution is also not a
configurable setting for the PDF renderer. The documentation link which I
sent earlier
incorrectly lists DpiX and DpiY as available Device Information settings
for PDF.
<http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsprog/htm
/rsp_prog_soapapi_dev_8bld.asp>
This documentation was corrected later for RS 2005 version:
<http://msdn2.microsoft.com/en-us/library/ms154682.aspx>
So unfortunately the DpiX and DpiY settings will have no effect when passed
to Render method.
Please rest assured your feedback on this is reported to the proper
channel. In the meantime, I also encourage you submit via the link below so
that product team could hear your sound directly:
http://lab.msdn.microsoft.com/productfeedback/default.aspx
You may want to consider using Excel rendering method but it may not meet
your requriment exactly. Or you may want to consider using a report server
to render the report for you other than using a local report.
If you have any questions or concerns on this, please feel free to let us
know.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.sql
PDF Size with Chart
Hello,
I am using ReportViewer in a web application. When there is a chart as part
of a report and it is exported to PDF the file size is very large for a
single page; typically 10-12 Mb.
I am now supposed to manufacture a report that will be about 50 pages with a
large graph on each page and I don't thing a 500Mb file size is acceptable.
Isn't there a way for the charts to use a vector format instead or at least
a compressed format?
Thanks,
JohnI've noticed a similar strange behavior with PDF and charts with RS 2005.
I've had situations where the PDF download never ends :)
So for charts we have people export to TIFF.
It looks to be a bug with RS 2005.
"JPS" wrote:
> Hello,
> I am using ReportViewer in a web application. When there is a chart as part
> of a report and it is exported to PDF the file size is very large for a
> single page; typically 10-12 Mb.
> I am now supposed to manufacture a report that will be about 50 pages with a
> large graph on each page and I don't thing a 500Mb file size is acceptable.
> Isn't there a way for the charts to use a vector format instead or at least
> a compressed format?
> Thanks,
> John|||I have the same issue. We are creating a report with three charts, and it is
20 MB total file size. We are using local reports in an Asp .Net 2.0 page.
Any help would be greatly appreciated.
Thanks
Sam
"Carmine" wrote:
> I've noticed a similar strange behavior with PDF and charts with RS 2005.
> I've had situations where the PDF download never ends :)
> So for charts we have people export to TIFF.
> It looks to be a bug with RS 2005.
> "JPS" wrote:
> > Hello,
> >
> > I am using ReportViewer in a web application. When there is a chart as part
> > of a report and it is exported to PDF the file size is very large for a
> > single page; typically 10-12 Mb.
> >
> > I am now supposed to manufacture a report that will be about 50 pages with a
> > large graph on each page and I don't thing a 500Mb file size is acceptable.
> >
> > Isn't there a way for the charts to use a vector format instead or at least
> > a compressed format?
> >
> > Thanks,
> > John
I am using ReportViewer in a web application. When there is a chart as part
of a report and it is exported to PDF the file size is very large for a
single page; typically 10-12 Mb.
I am now supposed to manufacture a report that will be about 50 pages with a
large graph on each page and I don't thing a 500Mb file size is acceptable.
Isn't there a way for the charts to use a vector format instead or at least
a compressed format?
Thanks,
JohnI've noticed a similar strange behavior with PDF and charts with RS 2005.
I've had situations where the PDF download never ends :)
So for charts we have people export to TIFF.
It looks to be a bug with RS 2005.
"JPS" wrote:
> Hello,
> I am using ReportViewer in a web application. When there is a chart as part
> of a report and it is exported to PDF the file size is very large for a
> single page; typically 10-12 Mb.
> I am now supposed to manufacture a report that will be about 50 pages with a
> large graph on each page and I don't thing a 500Mb file size is acceptable.
> Isn't there a way for the charts to use a vector format instead or at least
> a compressed format?
> Thanks,
> John|||I have the same issue. We are creating a report with three charts, and it is
20 MB total file size. We are using local reports in an Asp .Net 2.0 page.
Any help would be greatly appreciated.
Thanks
Sam
"Carmine" wrote:
> I've noticed a similar strange behavior with PDF and charts with RS 2005.
> I've had situations where the PDF download never ends :)
> So for charts we have people export to TIFF.
> It looks to be a bug with RS 2005.
> "JPS" wrote:
> > Hello,
> >
> > I am using ReportViewer in a web application. When there is a chart as part
> > of a report and it is exported to PDF the file size is very large for a
> > single page; typically 10-12 Mb.
> >
> > I am now supposed to manufacture a report that will be about 50 pages with a
> > large graph on each page and I don't thing a 500Mb file size is acceptable.
> >
> > Isn't there a way for the charts to use a vector format instead or at least
> > a compressed format?
> >
> > Thanks,
> > John
Wednesday, March 28, 2012
PDF rendering extension not working on SQL RS 2K sp2
I am in the process of migrating apps from SSRS 2K sp1 to SP2 and one of the
application renders to PDF and it is not working.
I thought pdf rendering was missed out from rsserver.config file and added
the line below
<Extension Name="PDF"
type="Microsoft.ReportingServices.Rendering.ImageRenderer.PdfReport,Microsoft.ReportingServices.ImageRendering"/>
...thinking it might help, but still not.
THis is the error msg we are getting whenever we run the report from the
application.
An attempt has been made to use a rendering extension that is not registered
for this report server. --> An attempt has been made to use a rendering
extension that is not registered for this report server. --> An attempt has
been made to use a rendering extension that is not registered for this report
server
When we run the report from reporting service it works...
Can some one help me or point me in how to fix ...
Env: Win2k3 - SQL 2k - SSRS Sp2.
Thanks
- SaravanaAnyone can you reply about this, as I am in a time crunch
regards
- Saravana
"SK" wrote:
> I am in the process of migrating apps from SSRS 2K sp1 to SP2 and one of the
> application renders to PDF and it is not working.
> I thought pdf rendering was missed out from rsserver.config file and added
> the line below
> <Extension Name="PDF"
> type="Microsoft.ReportingServices.Rendering.ImageRenderer.PdfReport,Microsoft.ReportingServices.ImageRendering"/>
> ...thinking it might help, but still not.
> THis is the error msg we are getting whenever we run the report from the
> application.
> An attempt has been made to use a rendering extension that is not registered
> for this report server. --> An attempt has been made to use a rendering
> extension that is not registered for this report server. --> An attempt has
> been made to use a rendering extension that is not registered for this report
> server
> When we run the report from reporting service it works...
> Can some one help me or point me in how to fix ...
> Env: Win2k3 - SQL 2k - SSRS Sp2.
> Thanks
> - Saravana
application renders to PDF and it is not working.
I thought pdf rendering was missed out from rsserver.config file and added
the line below
<Extension Name="PDF"
type="Microsoft.ReportingServices.Rendering.ImageRenderer.PdfReport,Microsoft.ReportingServices.ImageRendering"/>
...thinking it might help, but still not.
THis is the error msg we are getting whenever we run the report from the
application.
An attempt has been made to use a rendering extension that is not registered
for this report server. --> An attempt has been made to use a rendering
extension that is not registered for this report server. --> An attempt has
been made to use a rendering extension that is not registered for this report
server
When we run the report from reporting service it works...
Can some one help me or point me in how to fix ...
Env: Win2k3 - SQL 2k - SSRS Sp2.
Thanks
- SaravanaAnyone can you reply about this, as I am in a time crunch
regards
- Saravana
"SK" wrote:
> I am in the process of migrating apps from SSRS 2K sp1 to SP2 and one of the
> application renders to PDF and it is not working.
> I thought pdf rendering was missed out from rsserver.config file and added
> the line below
> <Extension Name="PDF"
> type="Microsoft.ReportingServices.Rendering.ImageRenderer.PdfReport,Microsoft.ReportingServices.ImageRendering"/>
> ...thinking it might help, but still not.
> THis is the error msg we are getting whenever we run the report from the
> application.
> An attempt has been made to use a rendering extension that is not registered
> for this report server. --> An attempt has been made to use a rendering
> extension that is not registered for this report server. --> An attempt has
> been made to use a rendering extension that is not registered for this report
> server
> When we run the report from reporting service it works...
> Can some one help me or point me in how to fix ...
> Env: Win2k3 - SQL 2k - SSRS Sp2.
> Thanks
> - Saravana
PDF Formatting Problem
Dear All,
I have written a database application in SQL and am using SQL Reporting
Services (for the first time) to generate the reports. I have come across a
problem to which I cannot see a solutions.
As part of the database application we store 'Visit Reports' which sales
people use to record information about customer that they have visited. I
have written a report which should display each record on a seperate page.
However, when someone has written a particularly long report and this spans 2
or more pages the report formats correctly on the screen, but when you export
to pdf you have the header information on 1 page (let's say the top 1/3 of
the page) and the detail of the report moves on to the next page. What I
want to happen is for the report to move on to a new page when appropriate
(i.e. when the 1st page is full).
Has anyone come across this? Is there a solution?
Thanks in advance,
Mike SwannIt looks like your report is either wider than 8½" or taller than 11".
Remember to take into account the body of your report, and the height of
header and footer (if there are any). I keep a safety margin of ½" to 1" to
avoid such issues.
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Mike Swann" <MikeSwann@.discussions.microsoft.com> wrote in message
news:C806740E-EE41-4E99-9F71-4D0610E6B7F2@.microsoft.com...
> Dear All,
> I have written a database application in SQL and am using SQL Reporting
> Services (for the first time) to generate the reports. I have come across
> a
> problem to which I cannot see a solutions.
> As part of the database application we store 'Visit Reports' which sales
> people use to record information about customer that they have visited. I
> have written a report which should display each record on a seperate page.
> However, when someone has written a particularly long report and this
> spans 2
> or more pages the report formats correctly on the screen, but when you
> export
> to pdf you have the header information on 1 page (let's say the top 1/3 of
> the page) and the detail of the report moves on to the next page. What I
> want to happen is for the report to move on to a new page when appropriate
> (i.e. when the 1st page is full).
> Has anyone come across this? Is there a solution?
> Thanks in advance,
> Mike Swann|||Thanks for your response.
However, this is a UK A4 format and that is all correct. It is purely when
the report data forces it on to 2 pages. If there is only enough data for 1
page then it will convert to a pdf perfectly well.
Any other ideas?
Thanks
Mike
"Alain Quesnel" wrote:
> It looks like your report is either wider than 8½" or taller than 11".
> Remember to take into account the body of your report, and the height of
> header and footer (if there are any). I keep a safety margin of ½" to 1" to
> avoid such issues.
>
> Alain Quesnel
> alainsansspam@.logiquel.com
> www.logiquel.com
>
> "Mike Swann" <MikeSwann@.discussions.microsoft.com> wrote in message
> news:C806740E-EE41-4E99-9F71-4D0610E6B7F2@.microsoft.com...
> >
> > Dear All,
> >
> > I have written a database application in SQL and am using SQL Reporting
> > Services (for the first time) to generate the reports. I have come across
> > a
> > problem to which I cannot see a solutions.
> >
> > As part of the database application we store 'Visit Reports' which sales
> > people use to record information about customer that they have visited. I
> > have written a report which should display each record on a seperate page.
> > However, when someone has written a particularly long report and this
> > spans 2
> > or more pages the report formats correctly on the screen, but when you
> > export
> > to pdf you have the header information on 1 page (let's say the top 1/3 of
> > the page) and the detail of the report moves on to the next page. What I
> > want to happen is for the report to move on to a new page when appropriate
> > (i.e. when the 1st page is full).
> >
> > Has anyone come across this? Is there a solution?
> >
> > Thanks in advance,
> >
> > Mike Swann
>|||You say that your header occupies 1/3 of the page. Did you try a smaller
header? Or no header at all?
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Mike Swann" <MikeSwann@.discussions.microsoft.com> wrote in message
news:D41B4154-8BDA-4534-9B60-3619D81E995E@.microsoft.com...
> Thanks for your response.
> However, this is a UK A4 format and that is all correct. It is purely
> when
> the report data forces it on to 2 pages. If there is only enough data for
> 1
> page then it will convert to a pdf perfectly well.
> Any other ideas?
> Thanks
> Mike
>
> "Alain Quesnel" wrote:
>> It looks like your report is either wider than 8½" or taller than 11".
>> Remember to take into account the body of your report, and the height of
>> header and footer (if there are any). I keep a safety margin of ½" to 1"
>> to
>> avoid such issues.
>>
>> Alain Quesnel
>> alainsansspam@.logiquel.com
>> www.logiquel.com
>>
>> "Mike Swann" <MikeSwann@.discussions.microsoft.com> wrote in message
>> news:C806740E-EE41-4E99-9F71-4D0610E6B7F2@.microsoft.com...
>> >
>> > Dear All,
>> >
>> > I have written a database application in SQL and am using SQL Reporting
>> > Services (for the first time) to generate the reports. I have come
>> > across
>> > a
>> > problem to which I cannot see a solutions.
>> >
>> > As part of the database application we store 'Visit Reports' which
>> > sales
>> > people use to record information about customer that they have visited.
>> > I
>> > have written a report which should display each record on a seperate
>> > page.
>> > However, when someone has written a particularly long report and this
>> > spans 2
>> > or more pages the report formats correctly on the screen, but when you
>> > export
>> > to pdf you have the header information on 1 page (let's say the top 1/3
>> > of
>> > the page) and the detail of the report moves on to the next page. What
>> > I
>> > want to happen is for the report to move on to a new page when
>> > appropriate
>> > (i.e. when the 1st page is full).
>> >
>> > Has anyone come across this? Is there a solution?
>> >
>> > Thanks in advance,
>> >
>> > Mike Swann
>>
I have written a database application in SQL and am using SQL Reporting
Services (for the first time) to generate the reports. I have come across a
problem to which I cannot see a solutions.
As part of the database application we store 'Visit Reports' which sales
people use to record information about customer that they have visited. I
have written a report which should display each record on a seperate page.
However, when someone has written a particularly long report and this spans 2
or more pages the report formats correctly on the screen, but when you export
to pdf you have the header information on 1 page (let's say the top 1/3 of
the page) and the detail of the report moves on to the next page. What I
want to happen is for the report to move on to a new page when appropriate
(i.e. when the 1st page is full).
Has anyone come across this? Is there a solution?
Thanks in advance,
Mike SwannIt looks like your report is either wider than 8½" or taller than 11".
Remember to take into account the body of your report, and the height of
header and footer (if there are any). I keep a safety margin of ½" to 1" to
avoid such issues.
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Mike Swann" <MikeSwann@.discussions.microsoft.com> wrote in message
news:C806740E-EE41-4E99-9F71-4D0610E6B7F2@.microsoft.com...
> Dear All,
> I have written a database application in SQL and am using SQL Reporting
> Services (for the first time) to generate the reports. I have come across
> a
> problem to which I cannot see a solutions.
> As part of the database application we store 'Visit Reports' which sales
> people use to record information about customer that they have visited. I
> have written a report which should display each record on a seperate page.
> However, when someone has written a particularly long report and this
> spans 2
> or more pages the report formats correctly on the screen, but when you
> export
> to pdf you have the header information on 1 page (let's say the top 1/3 of
> the page) and the detail of the report moves on to the next page. What I
> want to happen is for the report to move on to a new page when appropriate
> (i.e. when the 1st page is full).
> Has anyone come across this? Is there a solution?
> Thanks in advance,
> Mike Swann|||Thanks for your response.
However, this is a UK A4 format and that is all correct. It is purely when
the report data forces it on to 2 pages. If there is only enough data for 1
page then it will convert to a pdf perfectly well.
Any other ideas?
Thanks
Mike
"Alain Quesnel" wrote:
> It looks like your report is either wider than 8½" or taller than 11".
> Remember to take into account the body of your report, and the height of
> header and footer (if there are any). I keep a safety margin of ½" to 1" to
> avoid such issues.
>
> Alain Quesnel
> alainsansspam@.logiquel.com
> www.logiquel.com
>
> "Mike Swann" <MikeSwann@.discussions.microsoft.com> wrote in message
> news:C806740E-EE41-4E99-9F71-4D0610E6B7F2@.microsoft.com...
> >
> > Dear All,
> >
> > I have written a database application in SQL and am using SQL Reporting
> > Services (for the first time) to generate the reports. I have come across
> > a
> > problem to which I cannot see a solutions.
> >
> > As part of the database application we store 'Visit Reports' which sales
> > people use to record information about customer that they have visited. I
> > have written a report which should display each record on a seperate page.
> > However, when someone has written a particularly long report and this
> > spans 2
> > or more pages the report formats correctly on the screen, but when you
> > export
> > to pdf you have the header information on 1 page (let's say the top 1/3 of
> > the page) and the detail of the report moves on to the next page. What I
> > want to happen is for the report to move on to a new page when appropriate
> > (i.e. when the 1st page is full).
> >
> > Has anyone come across this? Is there a solution?
> >
> > Thanks in advance,
> >
> > Mike Swann
>|||You say that your header occupies 1/3 of the page. Did you try a smaller
header? Or no header at all?
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Mike Swann" <MikeSwann@.discussions.microsoft.com> wrote in message
news:D41B4154-8BDA-4534-9B60-3619D81E995E@.microsoft.com...
> Thanks for your response.
> However, this is a UK A4 format and that is all correct. It is purely
> when
> the report data forces it on to 2 pages. If there is only enough data for
> 1
> page then it will convert to a pdf perfectly well.
> Any other ideas?
> Thanks
> Mike
>
> "Alain Quesnel" wrote:
>> It looks like your report is either wider than 8½" or taller than 11".
>> Remember to take into account the body of your report, and the height of
>> header and footer (if there are any). I keep a safety margin of ½" to 1"
>> to
>> avoid such issues.
>>
>> Alain Quesnel
>> alainsansspam@.logiquel.com
>> www.logiquel.com
>>
>> "Mike Swann" <MikeSwann@.discussions.microsoft.com> wrote in message
>> news:C806740E-EE41-4E99-9F71-4D0610E6B7F2@.microsoft.com...
>> >
>> > Dear All,
>> >
>> > I have written a database application in SQL and am using SQL Reporting
>> > Services (for the first time) to generate the reports. I have come
>> > across
>> > a
>> > problem to which I cannot see a solutions.
>> >
>> > As part of the database application we store 'Visit Reports' which
>> > sales
>> > people use to record information about customer that they have visited.
>> > I
>> > have written a report which should display each record on a seperate
>> > page.
>> > However, when someone has written a particularly long report and this
>> > spans 2
>> > or more pages the report formats correctly on the screen, but when you
>> > export
>> > to pdf you have the header information on 1 page (let's say the top 1/3
>> > of
>> > the page) and the detail of the report moves on to the next page. What
>> > I
>> > want to happen is for the report to move on to a new page when
>> > appropriate
>> > (i.e. when the 1st page is full).
>> >
>> > Has anyone come across this? Is there a solution?
>> >
>> > Thanks in advance,
>> >
>> > Mike Swann
>>
Friday, March 23, 2012
PDF Downloads & ASP
I have a web application (ASP, COM+, SQLServer2K) that uses my own VB COM
components and a Crystal Reports component (a 5mb component) that takes a CR
report that I designed (about 1mb in size), executes it, and exports it as a
PDF file to the server's hard disk ready for download by my users.
Having just come across Reporting Services, it would appear to me that I
could ditch Crystal and go with Reporting Services exclusively. However, in
my browsing I have not come across how to do this with Reporting Services
without using the Report Manager (my users are "anonymous" web users and do
not have access to the server directly) and I can't seem to find any
examples of how to recreate the process I described above.
Questions:
1) Can Reporting Services run a report, and export it as PDF to server hard
drive without user intervention (or using Report Manager)?
2) Can I expect faster processing of reports with Reporting Services
compared to Crystal on the server (my Crystal reports depends entirely on
SPs in SQLServer)?
3) Are there programming examples of using Reporting Services with VB and
ASP, particularly involving PDF export and download?
Thanks for any tips or directions.1) Yes
2) don't know
3) you need to use the web service interface to interact with RS, so you
will need to look for code with uses ASP and Web services then apply what
you learn to the RS web service interface. Most code I have seen assumes
ASP.NET since the web service integration is "trouble free"
hope this helps.
dlr
"Don Miller" <nospam@.nospam.com> wrote in message
news:%234erUYMnEHA.1564@.TK2MSFTNGP09.phx.gbl...
> I have a web application (ASP, COM+, SQLServer2K) that uses my own VB COM
> components and a Crystal Reports component (a 5mb component) that takes a
CR
> report that I designed (about 1mb in size), executes it, and exports it as
a
> PDF file to the server's hard disk ready for download by my users.
> Having just come across Reporting Services, it would appear to me that I
> could ditch Crystal and go with Reporting Services exclusively. However,
in
> my browsing I have not come across how to do this with Reporting Services
> without using the Report Manager (my users are "anonymous" web users and
do
> not have access to the server directly) and I can't seem to find any
> examples of how to recreate the process I described above.
> Questions:
> 1) Can Reporting Services run a report, and export it as PDF to server
hard
> drive without user intervention (or using Report Manager)?
> 2) Can I expect faster processing of reports with Reporting Services
> compared to Crystal on the server (my Crystal reports depends entirely on
> SPs in SQLServer)?
> 3) Are there programming examples of using Reporting Services with VB and
> ASP, particularly involving PDF export and download?
> Thanks for any tips or directions.
>
components and a Crystal Reports component (a 5mb component) that takes a CR
report that I designed (about 1mb in size), executes it, and exports it as a
PDF file to the server's hard disk ready for download by my users.
Having just come across Reporting Services, it would appear to me that I
could ditch Crystal and go with Reporting Services exclusively. However, in
my browsing I have not come across how to do this with Reporting Services
without using the Report Manager (my users are "anonymous" web users and do
not have access to the server directly) and I can't seem to find any
examples of how to recreate the process I described above.
Questions:
1) Can Reporting Services run a report, and export it as PDF to server hard
drive without user intervention (or using Report Manager)?
2) Can I expect faster processing of reports with Reporting Services
compared to Crystal on the server (my Crystal reports depends entirely on
SPs in SQLServer)?
3) Are there programming examples of using Reporting Services with VB and
ASP, particularly involving PDF export and download?
Thanks for any tips or directions.1) Yes
2) don't know
3) you need to use the web service interface to interact with RS, so you
will need to look for code with uses ASP and Web services then apply what
you learn to the RS web service interface. Most code I have seen assumes
ASP.NET since the web service integration is "trouble free"
hope this helps.
dlr
"Don Miller" <nospam@.nospam.com> wrote in message
news:%234erUYMnEHA.1564@.TK2MSFTNGP09.phx.gbl...
> I have a web application (ASP, COM+, SQLServer2K) that uses my own VB COM
> components and a Crystal Reports component (a 5mb component) that takes a
CR
> report that I designed (about 1mb in size), executes it, and exports it as
a
> PDF file to the server's hard disk ready for download by my users.
> Having just come across Reporting Services, it would appear to me that I
> could ditch Crystal and go with Reporting Services exclusively. However,
in
> my browsing I have not come across how to do this with Reporting Services
> without using the Report Manager (my users are "anonymous" web users and
do
> not have access to the server directly) and I can't seem to find any
> examples of how to recreate the process I described above.
> Questions:
> 1) Can Reporting Services run a report, and export it as PDF to server
hard
> drive without user intervention (or using Report Manager)?
> 2) Can I expect faster processing of reports with Reporting Services
> compared to Crystal on the server (my Crystal reports depends entirely on
> SPs in SQLServer)?
> 3) Are there programming examples of using Reporting Services with VB and
> ASP, particularly involving PDF export and download?
> Thanks for any tips or directions.
>
Wednesday, March 21, 2012
Pauses in SQL 2000
I am running SQL 2000 SP3 on a Windows 2003 server. I am
having problems with pauses in my application software. I
put a protocol analyzer on the switch and I am getting no
data error but I am getting a large amount of SQL
retries. It this normal? Has anyone seen this problem
before?
Thanks,
Jason Mobley
Technology Director
NWFL Daily NewsRetries sound like client connection issues. What I would do is try and
isolate a client machine, and see if you could load SQL client tools. Then
you could run SQL Client Network Utiltiy and compare it to SQL Server
Network Utility on the server. Sometimes the TCP/IP sockets port gets
changed from the default port of 1433, or firewalls block it. In that case,
the clients will switch from TCP/IP sockets to Named Pipes, or conceivably
keep trying to connect. I would investigat that. Even though Named Pipes
seems to be a default, I've seen a lot of clients out there default to
TCP/IP sockets, especially when going to ODBC Data Sources in control panel
and configuring a SQL Server System DSN (client configuration on the login
credential screen shows you what is being used for connections as well).
Read this article for information on Named Pipes and TCP/IP sockets
http://msdn.microsoft.com/library/d.../>
1a_7fcj.asp
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Jmobley" <anonymous@.discussions.microsoft.com> wrote in message
news:6e1801c3e75a$3c080fa0$a301280a@.phx.gbl...
having problems with pauses in my application software. I
put a protocol analyzer on the switch and I am getting no
data error but I am getting a large amount of SQL
retries. It this normal? Has anyone seen this problem
before?
Thanks,
Jason Mobley
Technology Director
NWFL Daily NewsRetries sound like client connection issues. What I would do is try and
isolate a client machine, and see if you could load SQL client tools. Then
you could run SQL Client Network Utiltiy and compare it to SQL Server
Network Utility on the server. Sometimes the TCP/IP sockets port gets
changed from the default port of 1433, or firewalls block it. In that case,
the clients will switch from TCP/IP sockets to Named Pipes, or conceivably
keep trying to connect. I would investigat that. Even though Named Pipes
seems to be a default, I've seen a lot of clients out there default to
TCP/IP sockets, especially when going to ODBC Data Sources in control panel
and configuring a SQL Server System DSN (client configuration on the login
credential screen shows you what is being used for connections as well).
Read this article for information on Named Pipes and TCP/IP sockets
http://msdn.microsoft.com/library/d.../>
1a_7fcj.asp
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Jmobley" <anonymous@.discussions.microsoft.com> wrote in message
news:6e1801c3e75a$3c080fa0$a301280a@.phx.gbl...
quote:
> I am running SQL 2000 SP3 on a Windows 2003 server. I am
> having problems with pauses in my application software. I
> put a protocol analyzer on the switch and I am getting no
> data error but I am getting a large amount of SQL
> retries. It this normal? Has anyone seen this problem
> before?
> Thanks,
> Jason Mobley
> Technology Director
> NWFL Daily News
>
Tuesday, March 20, 2012
Patching SQLServer/MSDE
Patching SQLServer/MSDE
We are developing a desktop application that will use an MSDE database. The
data in the DB we deploy cannot be read by users, or administrators of the b
ox or other SQL Server admins. To accomplish this, we have learned we would
have to install a separate
instance of SQLServer/MSDE on the user's PC (or, alternately, encrypt the da
tabase).
The downside to a separate instance is we would be responsible to apply any
SQL Server patches to our instance. Our software is given to our customers,
and we have no control over their machines, so we will have to issue servic
e patches for our software
that contain the SQL Server patches as they come out.
My question is this: Obviously, it will be difficult for us to get patches o
f our software out there immediately after each SQL Server patch is released
my Microsoft. Are there threats that SQL Server remedy that can possibly ha
ve an adverse effect on sof
tware/hardware outside of the our database that is using the SQL Server inst
ance? I'm wondering about our liability if say, we release our version of a
patch 1-2 months after Microsoft releases their patch. I know our database
may be threatened, but is
there the possibility the user's machines/network would also be threatened i
f certain patches are not installed in a timely matter? I understand how th
is would be a major issue if we were talking about patches to IIS, but not
so sure about SQL Server.
Any thoughts on this are greatly appreciated.
Thanks!MSDE can be configured to listen only on Shared Memory. This will limit
your exposure from
external machines. So, other machines won't be able to connect to your
instance of MSDE, since
it's not listening on TCP or Named Pipes. Only local connections would
succeed.
MBSA 1.2 can be used to scan the local machine to see if it needs any SQL
related security fixes.
This could be documented in your application notes.
http://www.microsoft.com/technet/se...s/mbsahome.mspx
You can also find out Best Practices on the web ;
http://www.microsoft.com/technet/pr...n/sp3sec00.mspx
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
We are developing a desktop application that will use an MSDE database. The
data in the DB we deploy cannot be read by users, or administrators of the b
ox or other SQL Server admins. To accomplish this, we have learned we would
have to install a separate
instance of SQLServer/MSDE on the user's PC (or, alternately, encrypt the da
tabase).
The downside to a separate instance is we would be responsible to apply any
SQL Server patches to our instance. Our software is given to our customers,
and we have no control over their machines, so we will have to issue servic
e patches for our software
that contain the SQL Server patches as they come out.
My question is this: Obviously, it will be difficult for us to get patches o
f our software out there immediately after each SQL Server patch is released
my Microsoft. Are there threats that SQL Server remedy that can possibly ha
ve an adverse effect on sof
tware/hardware outside of the our database that is using the SQL Server inst
ance? I'm wondering about our liability if say, we release our version of a
patch 1-2 months after Microsoft releases their patch. I know our database
may be threatened, but is
there the possibility the user's machines/network would also be threatened i
f certain patches are not installed in a timely matter? I understand how th
is would be a major issue if we were talking about patches to IIS, but not
so sure about SQL Server.
Any thoughts on this are greatly appreciated.
Thanks!MSDE can be configured to listen only on Shared Memory. This will limit
your exposure from
external machines. So, other machines won't be able to connect to your
instance of MSDE, since
it's not listening on TCP or Named Pipes. Only local connections would
succeed.
MBSA 1.2 can be used to scan the local machine to see if it needs any SQL
related security fixes.
This could be documented in your application notes.
http://www.microsoft.com/technet/se...s/mbsahome.mspx
You can also find out Best Practices on the web ;
http://www.microsoft.com/technet/pr...n/sp3sec00.mspx
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Monday, March 12, 2012
patch application procedure
Hi,
I am having an mssql server with sp3. It is in sql cluster
(NT) as well as it participates in replication (merge). My
comany is very paranoid about doing things and all the
more there is no testing environment. Could any one please
explain how to apply SP4 for this server? We need to
consider the problematic conditions and disaster recovery
as well. My recovery mode is set to full.
james bond...-- james bond wrote: --
> Hi,
>> I am having an mssql server with sp3. It is in sql cluster
> (NT) as well as it participates in replication (merge). My
> company is very paranoid about doing things and all the
> more there is no testing environment. Could any one please
> explain how to apply SP4 for this server? We need to
> consider the problematic conditions and disaster recovery
> as well. My recovery mode is set to full.
--
Hi James Bond,
The best source of information for a service pack install is the README.htm of the service pack itself.
Hope this helps,
-Eric Cárdenas
SQL Server support
I am having an mssql server with sp3. It is in sql cluster
(NT) as well as it participates in replication (merge). My
comany is very paranoid about doing things and all the
more there is no testing environment. Could any one please
explain how to apply SP4 for this server? We need to
consider the problematic conditions and disaster recovery
as well. My recovery mode is set to full.
james bond...-- james bond wrote: --
> Hi,
>> I am having an mssql server with sp3. It is in sql cluster
> (NT) as well as it participates in replication (merge). My
> company is very paranoid about doing things and all the
> more there is no testing environment. Could any one please
> explain how to apply SP4 for this server? We need to
> consider the problematic conditions and disaster recovery
> as well. My recovery mode is set to full.
--
Hi James Bond,
The best source of information for a service pack install is the README.htm of the service pack itself.
Hope this helps,
-Eric Cárdenas
SQL Server support
Friday, March 9, 2012
Password question
Morning,
Yesterday I got a call from a developer, telling me that the MSSQL Login
(for a application) that I set up for him on ServerA was not letting him
login. This exact same MSSQL Login was also set up on ServerB and it works
fine. After, a bit of time, of looking into it I stumbled on the problem and
fix. The fix was the password length for the SQL Server login account.
According to BOL, the password can be from 1 to 128 & alpha-numeric. The
password was a 19 alpha-numeric character password. This worked with no
problems on ServerB but failed on ServerA.
ServerB is a Windows 2000 server while ServerA is NT4 SP6.
So, I'm thinking that even though this was a MSSQL login and not a OS login,
the OS layer is playing a role in the authentication process. Does anyone
know if this is so and what are the limitations of NT4 password length?
Thanks for you time,I forgot to add, both are SQL2000 SP3.
"JoeyDBA" <JoeyDBA@.yahoo.com> wrote in message
news:uQErEJmbEHA.716@.TK2MSFTNGP11.phx.gbl...
> Morning,
> Yesterday I got a call from a developer, telling me that the MSSQL Login
> (for a application) that I set up for him on ServerA was not letting him
> login. This exact same MSSQL Login was also set up on ServerB and it works
> fine. After, a bit of time, of looking into it I stumbled on the problem
and
> fix. The fix was the password length for the SQL Server login account.
> According to BOL, the password can be from 1 to 128 & alpha-numeric. The
> password was a 19 alpha-numeric character password. This worked with no
> problems on ServerB but failed on ServerA.
> ServerB is a Windows 2000 server while ServerA is NT4 SP6.
> So, I'm thinking that even though this was a MSSQL login and not a OS
login,
> the OS layer is playing a role in the authentication process. Does anyone
> know if this is so and what are the limitations of NT4 password length?
> Thanks for you time,
>|||If it's a SQL login account we don't interact with the OS.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||As Kevin already pointed out, a SQL Login doesn't interact
with the OS.
One possibility, If the server uses a case-sensitive
collation, then your passwords are case sensitive as well.
-Sue
On Tue, 20 Jul 2004 09:02:59 -0500, "JoeyDBA"
<JoeyDBA@.yahoo.com> wrote:
>Morning,
>Yesterday I got a call from a developer, telling me that the MSSQL Login
>(for a application) that I set up for him on ServerA was not letting him
>login. This exact same MSSQL Login was also set up on ServerB and it works
>fine. After, a bit of time, of looking into it I stumbled on the problem an
d
>fix. The fix was the password length for the SQL Server login account.
>According to BOL, the password can be from 1 to 128 & alpha-numeric. The
>password was a 19 alpha-numeric character password. This worked with no
>problems on ServerB but failed on ServerA.
>ServerB is a Windows 2000 server while ServerA is NT4 SP6.
>So, I'm thinking that even though this was a MSSQL login and not a OS login
,
>the OS layer is playing a role in the authentication process. Does anyone
>know if this is so and what are the limitations of NT4 password length?
>Thanks for you time,
>|||ok - thanks for the feed back. I'll go back and play with it again.
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:8SC7MkobEHA.2924@.cpmsftngxa06.phx.gbl...
> If it's a SQL login account we don't interact with the OS.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
Yesterday I got a call from a developer, telling me that the MSSQL Login
(for a application) that I set up for him on ServerA was not letting him
login. This exact same MSSQL Login was also set up on ServerB and it works
fine. After, a bit of time, of looking into it I stumbled on the problem and
fix. The fix was the password length for the SQL Server login account.
According to BOL, the password can be from 1 to 128 & alpha-numeric. The
password was a 19 alpha-numeric character password. This worked with no
problems on ServerB but failed on ServerA.
ServerB is a Windows 2000 server while ServerA is NT4 SP6.
So, I'm thinking that even though this was a MSSQL login and not a OS login,
the OS layer is playing a role in the authentication process. Does anyone
know if this is so and what are the limitations of NT4 password length?
Thanks for you time,I forgot to add, both are SQL2000 SP3.
"JoeyDBA" <JoeyDBA@.yahoo.com> wrote in message
news:uQErEJmbEHA.716@.TK2MSFTNGP11.phx.gbl...
> Morning,
> Yesterday I got a call from a developer, telling me that the MSSQL Login
> (for a application) that I set up for him on ServerA was not letting him
> login. This exact same MSSQL Login was also set up on ServerB and it works
> fine. After, a bit of time, of looking into it I stumbled on the problem
and
> fix. The fix was the password length for the SQL Server login account.
> According to BOL, the password can be from 1 to 128 & alpha-numeric. The
> password was a 19 alpha-numeric character password. This worked with no
> problems on ServerB but failed on ServerA.
> ServerB is a Windows 2000 server while ServerA is NT4 SP6.
> So, I'm thinking that even though this was a MSSQL login and not a OS
login,
> the OS layer is playing a role in the authentication process. Does anyone
> know if this is so and what are the limitations of NT4 password length?
> Thanks for you time,
>|||If it's a SQL login account we don't interact with the OS.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||As Kevin already pointed out, a SQL Login doesn't interact
with the OS.
One possibility, If the server uses a case-sensitive
collation, then your passwords are case sensitive as well.
-Sue
On Tue, 20 Jul 2004 09:02:59 -0500, "JoeyDBA"
<JoeyDBA@.yahoo.com> wrote:
>Morning,
>Yesterday I got a call from a developer, telling me that the MSSQL Login
>(for a application) that I set up for him on ServerA was not letting him
>login. This exact same MSSQL Login was also set up on ServerB and it works
>fine. After, a bit of time, of looking into it I stumbled on the problem an
d
>fix. The fix was the password length for the SQL Server login account.
>According to BOL, the password can be from 1 to 128 & alpha-numeric. The
>password was a 19 alpha-numeric character password. This worked with no
>problems on ServerB but failed on ServerA.
>ServerB is a Windows 2000 server while ServerA is NT4 SP6.
>So, I'm thinking that even though this was a MSSQL login and not a OS login
,
>the OS layer is playing a role in the authentication process. Does anyone
>know if this is so and what are the limitations of NT4 password length?
>Thanks for you time,
>|||ok - thanks for the feed back. I'll go back and play with it again.
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:8SC7MkobEHA.2924@.cpmsftngxa06.phx.gbl...
> If it's a SQL login account we don't interact with the OS.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
Password protection
Basic, I know.....
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Password protection
Basic, I know.....
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".
Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>
|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".
Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>
|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Password protection
Basic, I know.....
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Password Protect SQL SERVER
We have a database that we distribute for our application
to customers. We add users to a user table to allow
access to the web application only. How can I protect the
database with a secret password that only we know and the
customer can only access the data and use the database
but cannot get to the database using EM or Query Analyser
unless he knwos the password.
Help is appreciated.
I am new to all this so if some one could please guide me
to the right direction.
Thansk a lot.If they own the server and are sa then you can't. sa can see or do
everything on the server.
Andrew J. Kelly
SQL Server MVP
"HP" <anonymous@.discussions.microsoft.com> wrote in message
news:a26901c3eb2c$e9d5d7e0$a601280a@.phx.gbl...
user in the user table which will let them get to the
application if a valid user.
If they plan on buying sql server on thir own and putting
in our database is their a way we can stop them from
reading the database and egtting to its structure by
password protecting the database on the msde or by
encrypting the database.
can see or do
message
on to their box as the local admin they are essentially sa. You can remove
that account but that won't really stop someone from getting at it if they
want and have rights to the physical machine. The real answer here has
always been to make sure you have a good copywrite, NDA etc to cover this
area. There are some 3rd party tools to encrypt the db but it can be a real
hassle and in the long run I am not sure how effective it is. Take a look
on google for past posts regarding encryption and sql server for more
details.
Andrew J. Kelly
SQL Server MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:a63401c3eb5b$e253f450$a601280a@.phx.gbl...[QUOTE]
> We are the sa. We give to the customer MSDE with an added
> user in the user table which will let them get to the
> application if a valid user.
> If they plan on buying sql server on thir own and putting
> in our database is their a way we can stop them from
> reading the database and egtting to its structure by
> password protecting the database on the msde or by
> encrypting the database.
>
> can see or do
> message
> application
> the
> the
> Analyser
> me|||It is a serious weakness in MSSQL. There is no answer as far as we know.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:u25zg#16DHA.2472@.TK2MSFTNGP10.phx.gbl...
> By default there is a local NT admin account that is also sa. If they log
> on to their box as the local admin they are essentially sa. You can
remove
> that account but that won't really stop someone from getting at it if they
> want and have rights to the physical machine. The real answer here has
> always been to make sure you have a good copywrite, NDA etc to cover this
> area. There are some 3rd party tools to encrypt the db but it can be a
real
> hassle and in the long run I am not sure how effective it is. Take a look
> on google for past posts regarding encryption and sql server for more
> details.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> <anonymous@.discussions.microsoft.com> wrote in message
> news:a63401c3eb5b$e253f450$a601280a@.phx.gbl...
>
to customers. We add users to a user table to allow
access to the web application only. How can I protect the
database with a secret password that only we know and the
customer can only access the data and use the database
but cannot get to the database using EM or Query Analyser
unless he knwos the password.
Help is appreciated.
I am new to all this so if some one could please guide me
to the right direction.
Thansk a lot.If they own the server and are sa then you can't. sa can see or do
everything on the server.
Andrew J. Kelly
SQL Server MVP
"HP" <anonymous@.discussions.microsoft.com> wrote in message
news:a26901c3eb2c$e9d5d7e0$a601280a@.phx.gbl...
quote:|||We are the sa. We give to the customer MSDE with an added
> We have a database that we distribute for our application
> to customers. We add users to a user table to allow
> access to the web application only. How can I protect the
> database with a secret password that only we know and the
> customer can only access the data and use the database
> but cannot get to the database using EM or Query Analyser
> unless he knwos the password.
> Help is appreciated.
> I am new to all this so if some one could please guide me
> to the right direction.
> Thansk a lot.
user in the user table which will let them get to the
application if a valid user.
If they plan on buying sql server on thir own and putting
in our database is their a way we can stop them from
reading the database and egtting to its structure by
password protecting the database on the msde or by
encrypting the database.
quote:
>--Original Message--
>If they own the server and are sa then you can't. sa
can see or do
quote:
>everything on the server.
>--
>Andrew J. Kelly
>SQL Server MVP
>
>"HP" <anonymous@.discussions.microsoft.com> wrote in
message
quote:|||By default there is a local NT admin account that is also sa. If they log
>news:a26901c3eb2c$e9d5d7e0$a601280a@.phx.gbl...
application[QUOTE]
the[QUOTE]
the[QUOTE]
Analyser[QUOTE]
me[QUOTE]
>
>.
>
on to their box as the local admin they are essentially sa. You can remove
that account but that won't really stop someone from getting at it if they
want and have rights to the physical machine. The real answer here has
always been to make sure you have a good copywrite, NDA etc to cover this
area. There are some 3rd party tools to encrypt the db but it can be a real
hassle and in the long run I am not sure how effective it is. Take a look
on google for past posts regarding encryption and sql server for more
details.
Andrew J. Kelly
SQL Server MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:a63401c3eb5b$e253f450$a601280a@.phx.gbl...[QUOTE]
> We are the sa. We give to the customer MSDE with an added
> user in the user table which will let them get to the
> application if a valid user.
> If they plan on buying sql server on thir own and putting
> in our database is their a way we can stop them from
> reading the database and egtting to its structure by
> password protecting the database on the msde or by
> encrypting the database.
>
> can see or do
> message
> application
> the
> the
> Analyser
> me|||It is a serious weakness in MSSQL. There is no answer as far as we know.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:u25zg#16DHA.2472@.TK2MSFTNGP10.phx.gbl...
> By default there is a local NT admin account that is also sa. If they log
> on to their box as the local admin they are essentially sa. You can
remove
> that account but that won't really stop someone from getting at it if they
> want and have rights to the physical machine. The real answer here has
> always been to make sure you have a good copywrite, NDA etc to cover this
> area. There are some 3rd party tools to encrypt the db but it can be a
real
> hassle and in the long run I am not sure how effective it is. Take a look
> on google for past posts regarding encryption and sql server for more
> details.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> <anonymous@.discussions.microsoft.com> wrote in message
> news:a63401c3eb5b$e253f450$a601280a@.phx.gbl...
>
Wednesday, March 7, 2012
password encryption
I have an Access .adp application and I need to store the passwords encrypted. I see that there are unsupported functions pwdencrypt() and pwdcompare() in SQL server 2K.
Are there any other functions or methods in SQL Server 2000 that could be called that would provide this capability?Are there any other functions or methods in SQL Server 2000 that could be called that would provide this capability?
SQL Server 2000 encryption is pretty weak. 2005 is supposed to address this. In the meantime, you might consider this link:
http://www.sqlservercentral.com/columnists/mcoles/freeencryption.asp
(you may have to register, but registration is free).
Alternatively, you could use the Micrsoft Crypto API (capicom.dll) or the .Net Encryption utilities (don't have more specific references on these).
Regards,
hmscott
Are there any other functions or methods in SQL Server 2000 that could be called that would provide this capability?Are there any other functions or methods in SQL Server 2000 that could be called that would provide this capability?
SQL Server 2000 encryption is pretty weak. 2005 is supposed to address this. In the meantime, you might consider this link:
http://www.sqlservercentral.com/columnists/mcoles/freeencryption.asp
(you may have to register, but registration is free).
Alternatively, you could use the Micrsoft Crypto API (capicom.dll) or the .Net Encryption utilities (don't have more specific references on these).
Regards,
hmscott
Monday, February 20, 2012
Passing status back from Command line application to SQL Job
Hi,
I have created a job in SQL Server 2005 in which one of the step executes a .NET console application which is created in .NET to update some status to database before the next step. i need some help in sending some status back to sql job when i come accross any problem in the console application for ex when there is a exception i need to send some status to the job, so the job gets failed permanently. i tried few other methods of updating some temporary status database with this error information and have another intermediate step in the job to check for the status... it worked but i dont like doing it. please let me know if there is any other method to do this.
Thanks in advance
Hariharan
Are you doing anything with SSIS, or is this a SQL Server Agent question only?|||I'ts in SSIS as one of the step.|||
Hari Haran wrote:
I'ts in SSIS as one of the step.
Please provide more details then... As it reads, it sounds like it has nothing to do with SSIS.
Thanks,
Phil|||
To make the to step fail, just ensure the applicaton returns a suitable exit code. Take a closer look at the Job Step dialog and note of the "Process exit code of a successful cvommand:" option. Match this to you exist code as required. If this is the SSIS task after all, then look at the properties SuccessValue and FailTaskIfRetrnCodeIsNotSuccessValue.
You have set an exit code? If not see -
Environment.Exit Method (System)
(http://msdn2.microsoft.com/en-us/library/system.environment.exit.aspx)
Passing status back from Command line application to SQL Job
Hi,
I have created a job in SQL Server 2005 in which one of the step executes a .NET console application which is created in .NET to update some status to database before the next step. i need some help in sending some status back to sql job when i come accross any problem in the console application for ex when there is a exception i need to send some status to the job, so the job gets failed permanently. i tried few other methods of updating some temporary status database with this error information and have another intermediate step in the job to check for the status... it worked but i dont like doing it. please let me know if there is any other method to do this.
Thanks in advance
Hariharan
Are you doing anything with SSIS, or is this a SQL Server Agent question only?|||I'ts in SSIS as one of the step.|||
I'ts in SSIS as one of the step.
Please provide more details then... As it reads, it sounds like it has nothing to do with SSIS.
Thanks,
Phil|||
To make the to step fail, just ensure the applicaton returns a suitable exit code. Take a closer look at the Job Step dialog and note of the "Process exit code of a successful cvommand:" option. Match this to you exist code as required. If this is the SSIS task after all, then look at the properties SuccessValue and FailTaskIfRetrnCodeIsNotSuccessValue.
You have set an exit code? If not see -
Environment.Exit Method (System)
(http://msdn2.microsoft.com/en-us/library/system.environment.exit.aspx)
Passing settings
In my .NET application, I have my report control Zoom set to Page Width
(rc:Zoom=Page Width). This works fine for the first report that appears,
but when I click a link in this report to navigate to another, the zoom
resets to 100%.
Is there a way to get my Zoom to stay what I've set it to? Do I have to do
this in a config file rather than in .NET?
Thanks,
MelissaYes, we too would like to have all of our reports come up in page width
instead of 100%, is there a way to do this in report manager? maybe a setting
in the config file?
"Melissa" wrote:
> In my .NET application, I have my report control Zoom set to Page Width
> (rc:Zoom=Page Width). This works fine for the first report that appears,
> but when I click a link in this report to navigate to another, the zoom
> resets to 100%.
> Is there a way to get my Zoom to stay what I've set it to? Do I have to do
> this in a config file rather than in .NET?
>
> Thanks,
> Melissa
>
>
(rc:Zoom=Page Width). This works fine for the first report that appears,
but when I click a link in this report to navigate to another, the zoom
resets to 100%.
Is there a way to get my Zoom to stay what I've set it to? Do I have to do
this in a config file rather than in .NET?
Thanks,
MelissaYes, we too would like to have all of our reports come up in page width
instead of 100%, is there a way to do this in report manager? maybe a setting
in the config file?
"Melissa" wrote:
> In my .NET application, I have my report control Zoom set to Page Width
> (rc:Zoom=Page Width). This works fine for the first report that appears,
> but when I click a link in this report to navigate to another, the zoom
> resets to 100%.
> Is there a way to get my Zoom to stay what I've set it to? Do I have to do
> this in a config file rather than in .NET?
>
> Thanks,
> Melissa
>
>
Subscribe to:
Comments (Atom)