What would be the minumum hardware (and software) requirements to have
SQL client on 10 of our contractors' computer with a maximum database
size of 5GB?
Thank you very much
mike
The client machines can be pretty wimpy because the server process the T-SQL
and just returns the results the clients.
At a minimum I would want a PIII running Win2k with 256MB RAM.
Keith
"Mike" <mj1sql@.yahoo.com> wrote in message
news:9a55bd2d.0410070814.5589c64e@.posting.google.c om...
> What would be the minumum hardware (and software) requirements to have
> SQL client on 10 of our contractors' computer with a maximum database
> size of 5GB?
> Thank you very much
> mike
Showing posts with label software. Show all posts
Showing posts with label software. Show all posts
Wednesday, March 21, 2012
Minimum Hardware Requirement Warning
Hi all, we have released a shrink-wrapped software package that uses SQL Server Express as it's backend. I am currently tracking down an issue to do with SQL Server Express not installing correctly, and at the end of a lot of investigation I have come to the conclusion that it is a CPU problem.
The CPU is not "PII Compatible" enough for SQL Express. It appears as though the Cache prefetching instructions are the most likely culprit, but I was just wondering why the SQL Server Installer allows the user to continue with only a warning about the minimum hardware requirement not being met?
It seems to me that a lot of time and pain would be saved if the installer just said "Sorry, but you have no hope in hell of running SQL Server... go out and buy yourself a real machine" instead of allowing the user to continue all the way through the install and finally crash out at the final step.
Hey Scott,
Yeah, it turns out that the cache prefetching is required and we're not checking for it up front. I've filed a request to add that check for the next version of the product.
-Jeffrey.
|||Thanks, that would be a great help.|||Sorry, signed in with the wrong passport.
This will be a great help, thanks.
Wednesday, March 7, 2012
Migration from v7 to 2000 Q
We use a custom application written by a software company that are no longer
trading.
The back-end of the application runs on SQL7. We are currently implementing
a small business server 2003 system with SQL 2000. I would therefore like to
move the backend onto SQL 2000 (small biz).
I have tried to migrate to the database using the backup option on sql7 and
then restore on sql2000.
The problem I have come across is although it copies the data, it doesn't
copy the stored procs and views over. For this reason (I assume) the front
end stops working. When you run the application it stops asking for the
location of a view.
Is it possible to migrate the stored procs and views? What are my chances of
success. Sorry for the vagueness of the question, but SQL server admin
really isn't my thing. If you need more info please let me know.
TIA,
H
H,
Backup/Restore detach/attach both copy everything in the database including
views and stored procedures. Do you not see the views and stored procedures
in Enterprise Manager when you move from 7 --> 2000? Who owns these views
and stored procedures i.e., dbo?
HTH
Jerry
"H" <walesforthegr@.ndslam.com> wrote in message
news:O$$5AHQyFHA.3812@.TK2MSFTNGP09.phx.gbl...
> We use a custom application written by a software company that are no
> longer trading.
> The back-end of the application runs on SQL7. We are currently
> implementing a small business server 2003 system with SQL 2000. I would
> therefore like to move the backend onto SQL 2000 (small biz).
> I have tried to migrate to the database using the backup option on sql7
> and then restore on sql2000.
> The problem I have come across is although it copies the data, it doesn't
> copy the stored procs and views over. For this reason (I assume) the front
> end stops working. When you run the application it stops asking for the
> location of a view.
> Is it possible to migrate the stored procs and views? What are my chances
> of success. Sorry for the vagueness of the question, but SQL server admin
> really isn't my thing. If you need more info please let me know.
> TIA,
> H
>
|||Take a look at the Copy Database Wizard which should help pick up objects,
such as Stored Procedures, stored in the Master database.
Hal Berenson, President
PredictableIT, LLC
"H" <walesforthegr@.ndslam.com> wrote in message
news:O$$5AHQyFHA.3812@.TK2MSFTNGP09.phx.gbl...
> We use a custom application written by a software company that are no
> longer trading.
> The back-end of the application runs on SQL7. We are currently
> implementing a small business server 2003 system with SQL 2000. I would
> therefore like to move the backend onto SQL 2000 (small biz).
> I have tried to migrate to the database using the backup option on sql7
> and then restore on sql2000.
> The problem I have come across is although it copies the data, it doesn't
> copy the stored procs and views over. For this reason (I assume) the front
> end stops working. When you run the application it stops asking for the
> location of a view.
> Is it possible to migrate the stored procs and views? What are my chances
> of success. Sorry for the vagueness of the question, but SQL server admin
> really isn't my thing. If you need more info please let me know.
> TIA,
> H
>
trading.
The back-end of the application runs on SQL7. We are currently implementing
a small business server 2003 system with SQL 2000. I would therefore like to
move the backend onto SQL 2000 (small biz).
I have tried to migrate to the database using the backup option on sql7 and
then restore on sql2000.
The problem I have come across is although it copies the data, it doesn't
copy the stored procs and views over. For this reason (I assume) the front
end stops working. When you run the application it stops asking for the
location of a view.
Is it possible to migrate the stored procs and views? What are my chances of
success. Sorry for the vagueness of the question, but SQL server admin
really isn't my thing. If you need more info please let me know.
TIA,
H
H,
Backup/Restore detach/attach both copy everything in the database including
views and stored procedures. Do you not see the views and stored procedures
in Enterprise Manager when you move from 7 --> 2000? Who owns these views
and stored procedures i.e., dbo?
HTH
Jerry
"H" <walesforthegr@.ndslam.com> wrote in message
news:O$$5AHQyFHA.3812@.TK2MSFTNGP09.phx.gbl...
> We use a custom application written by a software company that are no
> longer trading.
> The back-end of the application runs on SQL7. We are currently
> implementing a small business server 2003 system with SQL 2000. I would
> therefore like to move the backend onto SQL 2000 (small biz).
> I have tried to migrate to the database using the backup option on sql7
> and then restore on sql2000.
> The problem I have come across is although it copies the data, it doesn't
> copy the stored procs and views over. For this reason (I assume) the front
> end stops working. When you run the application it stops asking for the
> location of a view.
> Is it possible to migrate the stored procs and views? What are my chances
> of success. Sorry for the vagueness of the question, but SQL server admin
> really isn't my thing. If you need more info please let me know.
> TIA,
> H
>
|||Take a look at the Copy Database Wizard which should help pick up objects,
such as Stored Procedures, stored in the Master database.
Hal Berenson, President
PredictableIT, LLC
"H" <walesforthegr@.ndslam.com> wrote in message
news:O$$5AHQyFHA.3812@.TK2MSFTNGP09.phx.gbl...
> We use a custom application written by a software company that are no
> longer trading.
> The back-end of the application runs on SQL7. We are currently
> implementing a small business server 2003 system with SQL 2000. I would
> therefore like to move the backend onto SQL 2000 (small biz).
> I have tried to migrate to the database using the backup option on sql7
> and then restore on sql2000.
> The problem I have come across is although it copies the data, it doesn't
> copy the stored procs and views over. For this reason (I assume) the front
> end stops working. When you run the application it stops asking for the
> location of a view.
> Is it possible to migrate the stored procs and views? What are my chances
> of success. Sorry for the vagueness of the question, but SQL server admin
> really isn't my thing. If you need more info please let me know.
> TIA,
> H
>
Migration from v7 to 2000 Q
We use a custom application written by a software company that are no longer
trading.
The back-end of the application runs on SQL7. We are currently implementing
a small business server 2003 system with SQL 2000. I would therefore like to
move the backend onto SQL 2000 (small biz).
I have tried to migrate to the database using the backup option on sql7 and
then restore on sql2000.
The problem I have come across is although it copies the data, it doesn't
copy the stored procs and views over. For this reason (I assume) the front
end stops working. When you run the application it stops asking for the
location of a view.
Is it possible to migrate the stored procs and views? What are my chances of
success. Sorry for the vagueness of the question, but SQL server admin
really isn't my thing. If you need more info please let me know.
TIA,
HH,
Backup/Restore detach/attach both copy everything in the database including
views and stored procedures. Do you not see the views and stored procedures
in Enterprise Manager when you move from 7 --> 2000? Who owns these views
and stored procedures i.e., dbo?
HTH
Jerry
"H" <walesforthegr@.ndslam.com> wrote in message
news:O$$5AHQyFHA.3812@.TK2MSFTNGP09.phx.gbl...
> We use a custom application written by a software company that are no
> longer trading.
> The back-end of the application runs on SQL7. We are currently
> implementing a small business server 2003 system with SQL 2000. I would
> therefore like to move the backend onto SQL 2000 (small biz).
> I have tried to migrate to the database using the backup option on sql7
> and then restore on sql2000.
> The problem I have come across is although it copies the data, it doesn't
> copy the stored procs and views over. For this reason (I assume) the front
> end stops working. When you run the application it stops asking for the
> location of a view.
> Is it possible to migrate the stored procs and views? What are my chances
> of success. Sorry for the vagueness of the question, but SQL server admin
> really isn't my thing. If you need more info please let me know.
> TIA,
> H
>|||Take a look at the Copy Database Wizard which should help pick up objects,
such as Stored Procedures, stored in the Master database.
--
Hal Berenson, President
PredictableIT, LLC
"H" <walesforthegr@.ndslam.com> wrote in message
news:O$$5AHQyFHA.3812@.TK2MSFTNGP09.phx.gbl...
> We use a custom application written by a software company that are no
> longer trading.
> The back-end of the application runs on SQL7. We are currently
> implementing a small business server 2003 system with SQL 2000. I would
> therefore like to move the backend onto SQL 2000 (small biz).
> I have tried to migrate to the database using the backup option on sql7
> and then restore on sql2000.
> The problem I have come across is although it copies the data, it doesn't
> copy the stored procs and views over. For this reason (I assume) the front
> end stops working. When you run the application it stops asking for the
> location of a view.
> Is it possible to migrate the stored procs and views? What are my chances
> of success. Sorry for the vagueness of the question, but SQL server admin
> really isn't my thing. If you need more info please let me know.
> TIA,
> H
>
trading.
The back-end of the application runs on SQL7. We are currently implementing
a small business server 2003 system with SQL 2000. I would therefore like to
move the backend onto SQL 2000 (small biz).
I have tried to migrate to the database using the backup option on sql7 and
then restore on sql2000.
The problem I have come across is although it copies the data, it doesn't
copy the stored procs and views over. For this reason (I assume) the front
end stops working. When you run the application it stops asking for the
location of a view.
Is it possible to migrate the stored procs and views? What are my chances of
success. Sorry for the vagueness of the question, but SQL server admin
really isn't my thing. If you need more info please let me know.
TIA,
HH,
Backup/Restore detach/attach both copy everything in the database including
views and stored procedures. Do you not see the views and stored procedures
in Enterprise Manager when you move from 7 --> 2000? Who owns these views
and stored procedures i.e., dbo?
HTH
Jerry
"H" <walesforthegr@.ndslam.com> wrote in message
news:O$$5AHQyFHA.3812@.TK2MSFTNGP09.phx.gbl...
> We use a custom application written by a software company that are no
> longer trading.
> The back-end of the application runs on SQL7. We are currently
> implementing a small business server 2003 system with SQL 2000. I would
> therefore like to move the backend onto SQL 2000 (small biz).
> I have tried to migrate to the database using the backup option on sql7
> and then restore on sql2000.
> The problem I have come across is although it copies the data, it doesn't
> copy the stored procs and views over. For this reason (I assume) the front
> end stops working. When you run the application it stops asking for the
> location of a view.
> Is it possible to migrate the stored procs and views? What are my chances
> of success. Sorry for the vagueness of the question, but SQL server admin
> really isn't my thing. If you need more info please let me know.
> TIA,
> H
>|||Take a look at the Copy Database Wizard which should help pick up objects,
such as Stored Procedures, stored in the Master database.
--
Hal Berenson, President
PredictableIT, LLC
"H" <walesforthegr@.ndslam.com> wrote in message
news:O$$5AHQyFHA.3812@.TK2MSFTNGP09.phx.gbl...
> We use a custom application written by a software company that are no
> longer trading.
> The back-end of the application runs on SQL7. We are currently
> implementing a small business server 2003 system with SQL 2000. I would
> therefore like to move the backend onto SQL 2000 (small biz).
> I have tried to migrate to the database using the backup option on sql7
> and then restore on sql2000.
> The problem I have come across is although it copies the data, it doesn't
> copy the stored procs and views over. For this reason (I assume) the front
> end stops working. When you run the application it stops asking for the
> location of a view.
> Is it possible to migrate the stored procs and views? What are my chances
> of success. Sorry for the vagueness of the question, but SQL server admin
> really isn't my thing. If you need more info please let me know.
> TIA,
> H
>
Migration from v7 to 2000 Q
We use a custom application written by a software company that are no longer
trading.
The back-end of the application runs on SQL7. We are currently implementing
a small business server 2003 system with SQL 2000. I would therefore like to
move the backend onto SQL 2000 (small biz).
I have tried to migrate to the database using the backup option on sql7 and
then restore on sql2000.
The problem I have come across is although it copies the data, it doesn't
copy the stored procs and views over. For this reason (I assume) the front
end stops working. When you run the application it stops asking for the
location of a view.
Is it possible to migrate the stored procs and views? What are my chances of
success. Sorry for the vagueness of the question, but SQL server admin
really isn't my thing. If you need more info please let me know.
TIA,
HH,
Backup/Restore detach/attach both copy everything in the database including
views and stored procedures. Do you not see the views and stored procedures
in Enterprise Manager when you move from 7 --> 2000? Who owns these views
and stored procedures i.e., dbo?
HTH
Jerry
"H" <walesforthegr@.ndslam.com> wrote in message
news:O$$5AHQyFHA.3812@.TK2MSFTNGP09.phx.gbl...
> We use a custom application written by a software company that are no
> longer trading.
> The back-end of the application runs on SQL7. We are currently
> implementing a small business server 2003 system with SQL 2000. I would
> therefore like to move the backend onto SQL 2000 (small biz).
> I have tried to migrate to the database using the backup option on sql7
> and then restore on sql2000.
> The problem I have come across is although it copies the data, it doesn't
> copy the stored procs and views over. For this reason (I assume) the front
> end stops working. When you run the application it stops asking for the
> location of a view.
> Is it possible to migrate the stored procs and views? What are my chances
> of success. Sorry for the vagueness of the question, but SQL server admin
> really isn't my thing. If you need more info please let me know.
> TIA,
> H
>|||Take a look at the Copy Database Wizard which should help pick up objects,
such as Stored Procedures, stored in the Master database.
Hal Berenson, President
PredictableIT, LLC
"H" <walesforthegr@.ndslam.com> wrote in message
news:O$$5AHQyFHA.3812@.TK2MSFTNGP09.phx.gbl...
> We use a custom application written by a software company that are no
> longer trading.
> The back-end of the application runs on SQL7. We are currently
> implementing a small business server 2003 system with SQL 2000. I would
> therefore like to move the backend onto SQL 2000 (small biz).
> I have tried to migrate to the database using the backup option on sql7
> and then restore on sql2000.
> The problem I have come across is although it copies the data, it doesn't
> copy the stored procs and views over. For this reason (I assume) the front
> end stops working. When you run the application it stops asking for the
> location of a view.
> Is it possible to migrate the stored procs and views? What are my chances
> of success. Sorry for the vagueness of the question, but SQL server admin
> really isn't my thing. If you need more info please let me know.
> TIA,
> H
>
trading.
The back-end of the application runs on SQL7. We are currently implementing
a small business server 2003 system with SQL 2000. I would therefore like to
move the backend onto SQL 2000 (small biz).
I have tried to migrate to the database using the backup option on sql7 and
then restore on sql2000.
The problem I have come across is although it copies the data, it doesn't
copy the stored procs and views over. For this reason (I assume) the front
end stops working. When you run the application it stops asking for the
location of a view.
Is it possible to migrate the stored procs and views? What are my chances of
success. Sorry for the vagueness of the question, but SQL server admin
really isn't my thing. If you need more info please let me know.
TIA,
HH,
Backup/Restore detach/attach both copy everything in the database including
views and stored procedures. Do you not see the views and stored procedures
in Enterprise Manager when you move from 7 --> 2000? Who owns these views
and stored procedures i.e., dbo?
HTH
Jerry
"H" <walesforthegr@.ndslam.com> wrote in message
news:O$$5AHQyFHA.3812@.TK2MSFTNGP09.phx.gbl...
> We use a custom application written by a software company that are no
> longer trading.
> The back-end of the application runs on SQL7. We are currently
> implementing a small business server 2003 system with SQL 2000. I would
> therefore like to move the backend onto SQL 2000 (small biz).
> I have tried to migrate to the database using the backup option on sql7
> and then restore on sql2000.
> The problem I have come across is although it copies the data, it doesn't
> copy the stored procs and views over. For this reason (I assume) the front
> end stops working. When you run the application it stops asking for the
> location of a view.
> Is it possible to migrate the stored procs and views? What are my chances
> of success. Sorry for the vagueness of the question, but SQL server admin
> really isn't my thing. If you need more info please let me know.
> TIA,
> H
>|||Take a look at the Copy Database Wizard which should help pick up objects,
such as Stored Procedures, stored in the Master database.
Hal Berenson, President
PredictableIT, LLC
"H" <walesforthegr@.ndslam.com> wrote in message
news:O$$5AHQyFHA.3812@.TK2MSFTNGP09.phx.gbl...
> We use a custom application written by a software company that are no
> longer trading.
> The back-end of the application runs on SQL7. We are currently
> implementing a small business server 2003 system with SQL 2000. I would
> therefore like to move the backend onto SQL 2000 (small biz).
> I have tried to migrate to the database using the backup option on sql7
> and then restore on sql2000.
> The problem I have come across is although it copies the data, it doesn't
> copy the stored procs and views over. For this reason (I assume) the front
> end stops working. When you run the application it stops asking for the
> location of a view.
> Is it possible to migrate the stored procs and views? What are my chances
> of success. Sorry for the vagueness of the question, but SQL server admin
> really isn't my thing. If you need more info please let me know.
> TIA,
> H
>
Monday, February 20, 2012
Migrating to Report Services
Or rather, migrating to local reports using the Microsoft Report
Services.
We are in the process of planning the next generation of our software,
and among other things we are contemplating which reporting platform
we will use.
Until now we have been using Crystal Report, but it seems to be
getting more and more heavy to work with, plus it is a rather hefty
investment, well it can be.
First a little history:
- Our software will be running on anything from a stand-alone PC with
no connection to the surrounding world, to large-scale "enterprise"
networks with several dozens of clients. As a result our reporting
platform must be able to handle this.
Originally Crystal Report handled this very nicely, in that regard
that we simply installed the runtime libraries on each PC with our
software and a bunch of report files locally. This is model our
customers are used to.
Now I have decided to check out Reporting Services, but I have a bit
of a difficult time wrapping my mind around the concept. Some things
seem very nice and elegant, but others seem somewhat less so. For one
thing, the reports seem a little too simple and no where nearly as
powerful as Crystal Reports.
Now, our database is usually called the same regardless of the
customer, and of course, the layout of the database is always the same
(some customers may have a few custom tables, etc). But internally we
may have any number of databases that is named differently (customer
backups, test databases etc). So I need a way of being able to set the
database "on-the-fly".
What (I think) I need:
- A way of designing local reports and setting the data source at
runtime.
- I do not want to use the web server exclusively.
- Initially I want local reports, but the central reporting server can
be an option.
- I want to be able to mix tabular/matrix and chart reports.
- I want to be able to show group headers and footers, as well as page
headers and footers.
- I want to have full access to all tables in the database, and not
being restricted once I select on table, or entity.
Basically, I want to use the Reporting Service, but I don't want to
loose the freedom in data selection that Crystal Report gives me.According to your description, you need to use both SQL Server Reporting
Services and local report tool, which is bundled with VS2005/8 (VS2003 is
bundled with CrystalReport.NET as local report tool, while VS2005/8 come
with both CrystalReport.NET and MS report tool).
More comments inline.
"ThomasD" <tho.due@.gmail.com> wrote in message
news:4de6bed8-f6bc-4188-afd5-93ac01d49398@.8g2000hse.googlegroups.com...
> Or rather, migrating to local reports using the Microsoft Report
> Services.
> We are in the process of planning the next generation of our software,
> and among other things we are contemplating which reporting platform
> we will use.
> Until now we have been using Crystal Report, but it seems to be
> getting more and more heavy to work with, plus it is a rather hefty
> investment, well it can be.
> First a little history:
> - Our software will be running on anything from a stand-alone PC with
> no connection to the surrounding world, to large-scale "enterprise"
> networks with several dozens of clients. As a result our reporting
> platform must be able to handle this.
> Originally Crystal Report handled this very nicely, in that regard
> that we simply installed the runtime libraries on each PC with our
> software and a bunch of report files locally. This is model our
> customers are used to.
> Now I have decided to check out Reporting Services, but I have a bit
> of a difficult time wrapping my mind around the concept. Some things
> seem very nice and elegant, but others seem somewhat less so. For one
> thing, the reports seem a little too simple and no where nearly as
> powerful as Crystal Reports.
> Now, our database is usually called the same regardless of the
> customer, and of course, the layout of the database is always the same
> (some customers may have a few custom tables, etc). But internally we
> may have any number of databases that is named differently (customer
> backups, test databases etc). So I need a way of being able to set the
> database "on-the-fly".
> What (I think) I need:
> - A way of designing local reports and setting the data source at
> runtime.
If you have VS2005/8, you can do local report with either CrystalReport.NET
or MS report tool. By "Local". If you use SQL Server RS, I'd use MS report
tool in VS for local report, because the report viewer control can render
both local report and report from SQL Server RS. So, you app can seemlessly
dispaly report either from local report or from SQL Server RS without user
knowing the difference.
> - I do not want to use the web server exclusively.
> - Initially I want local reports, but the central reporting server can
> be an option.
> - I want to be able to mix tabular/matrix and chart reports.
> - I want to be able to show group headers and footers, as well as page
> headers and footers.
MS local report is a bit not as fancy as RS report can be.
> - I want to have full access to all tables in the database, and not
> being restricted once I select on table, or entity.
That has little to do with reporting, local or server.
> Basically, I want to use the Reporting Service, but I don't want to
> loose the freedom in data selection that Crystal Report gives me.
Do not know what "Data selection freedom" means here.
With local report, you can connect to whatever data source. If needed, you
can use code do trasform anything into a DataSet/Table of your desired
schema and use it as the report source, I'd think it is complete freedom.
With SQL Server RS, if the report data is difficult to access by reqular
queries, or the data source is not conventinal database, you can write your
own Data Processing Extensions sitting between the reporting processor and
data source. Of course, this requires lots of coding.|||> According to your description, you need to use both SQL Server Reporting
> Services and local report tool, which is bundled with VS2005/8 (VS2003 is
> bundled with CrystalReport.NET as local report tool, while VS2005/8 come
> with both CrystalReport.NET and MS report tool).
We use VS2008. I would like keep the option of using the report server
open, but my primary concern is local reports.
> More comments inline.
Cool. :)
> > - A way of designing local reports and setting the data source at
> > runtime.
> If you have VS2005/8, you can do local report with either CrystalReport.NET
> or MS report tool. By "Local". If you use SQL Server RS, I'd use MS report
> tool in VS for local report, because the report viewer control can render
> both local report and report from SQL Server RS. So, you app can seemlessly
> dispaly report either from local report or from SQL Server RS without user
> knowing the difference.
I finally managed to actually get the report designer working (it is
not easy to handle, when you are used to using Crystal Reports). It
looks very promising, however as it turns out, I have to supply the
data source "manually" when using the report locally. That is fine,
not a problem. However, I would like to use the SQL embedded in the
report, but that seems to be somewhat difficult to get at. So far I
have managed to get it by using XPath, but I can't help thinking that
there must be an easier way.
> MS local report is a bit not as fancy as RS report can be.
True, but I AM making progress in understanding the limitations and
differences.
> > - I want to have full access to all tables in the database, and not
> > being restricted once I select on table, or entity.
> That has little to do with reporting, local or server.
Well, after I "discovered" the report designer in Sql Server Business
Intelligence Development Studio (what a mouthful), I see that. Now I
just need to get a handle on the embedded SQL.
> > Basically, I want to use the Reporting Service, but I don't want to
> > loose the freedom in data selection that Crystal Report gives me.
> Do not know what "Data selection freedom" means here.
SQL. I don't want to be relying on some obscure model. Direct SQL
input is my preferred method of pulling data. Crystal Reports can do
both, and after discover the report designer in BI studio it looks
very promising.
> With local report, you can connect to whatever data source. If needed, you
> can use code do trasform anything into a DataSet/Table of your desired
> schema and use it as the report source, I'd think it is complete freedom.
> With SQL Server RS, if the report data is difficult to access by reqular
> queries, or the data source is not conventinal database, you can write your
> own Data Processing Extensions sitting between the reporting processor and
> data source. Of course, this requires lots of coding.
Coding doesn't scare me, I wouldn't be a software developer otherwise
*grin*
Regards,
Thomas
Services.
We are in the process of planning the next generation of our software,
and among other things we are contemplating which reporting platform
we will use.
Until now we have been using Crystal Report, but it seems to be
getting more and more heavy to work with, plus it is a rather hefty
investment, well it can be.
First a little history:
- Our software will be running on anything from a stand-alone PC with
no connection to the surrounding world, to large-scale "enterprise"
networks with several dozens of clients. As a result our reporting
platform must be able to handle this.
Originally Crystal Report handled this very nicely, in that regard
that we simply installed the runtime libraries on each PC with our
software and a bunch of report files locally. This is model our
customers are used to.
Now I have decided to check out Reporting Services, but I have a bit
of a difficult time wrapping my mind around the concept. Some things
seem very nice and elegant, but others seem somewhat less so. For one
thing, the reports seem a little too simple and no where nearly as
powerful as Crystal Reports.
Now, our database is usually called the same regardless of the
customer, and of course, the layout of the database is always the same
(some customers may have a few custom tables, etc). But internally we
may have any number of databases that is named differently (customer
backups, test databases etc). So I need a way of being able to set the
database "on-the-fly".
What (I think) I need:
- A way of designing local reports and setting the data source at
runtime.
- I do not want to use the web server exclusively.
- Initially I want local reports, but the central reporting server can
be an option.
- I want to be able to mix tabular/matrix and chart reports.
- I want to be able to show group headers and footers, as well as page
headers and footers.
- I want to have full access to all tables in the database, and not
being restricted once I select on table, or entity.
Basically, I want to use the Reporting Service, but I don't want to
loose the freedom in data selection that Crystal Report gives me.According to your description, you need to use both SQL Server Reporting
Services and local report tool, which is bundled with VS2005/8 (VS2003 is
bundled with CrystalReport.NET as local report tool, while VS2005/8 come
with both CrystalReport.NET and MS report tool).
More comments inline.
"ThomasD" <tho.due@.gmail.com> wrote in message
news:4de6bed8-f6bc-4188-afd5-93ac01d49398@.8g2000hse.googlegroups.com...
> Or rather, migrating to local reports using the Microsoft Report
> Services.
> We are in the process of planning the next generation of our software,
> and among other things we are contemplating which reporting platform
> we will use.
> Until now we have been using Crystal Report, but it seems to be
> getting more and more heavy to work with, plus it is a rather hefty
> investment, well it can be.
> First a little history:
> - Our software will be running on anything from a stand-alone PC with
> no connection to the surrounding world, to large-scale "enterprise"
> networks with several dozens of clients. As a result our reporting
> platform must be able to handle this.
> Originally Crystal Report handled this very nicely, in that regard
> that we simply installed the runtime libraries on each PC with our
> software and a bunch of report files locally. This is model our
> customers are used to.
> Now I have decided to check out Reporting Services, but I have a bit
> of a difficult time wrapping my mind around the concept. Some things
> seem very nice and elegant, but others seem somewhat less so. For one
> thing, the reports seem a little too simple and no where nearly as
> powerful as Crystal Reports.
> Now, our database is usually called the same regardless of the
> customer, and of course, the layout of the database is always the same
> (some customers may have a few custom tables, etc). But internally we
> may have any number of databases that is named differently (customer
> backups, test databases etc). So I need a way of being able to set the
> database "on-the-fly".
> What (I think) I need:
> - A way of designing local reports and setting the data source at
> runtime.
If you have VS2005/8, you can do local report with either CrystalReport.NET
or MS report tool. By "Local". If you use SQL Server RS, I'd use MS report
tool in VS for local report, because the report viewer control can render
both local report and report from SQL Server RS. So, you app can seemlessly
dispaly report either from local report or from SQL Server RS without user
knowing the difference.
> - I do not want to use the web server exclusively.
> - Initially I want local reports, but the central reporting server can
> be an option.
> - I want to be able to mix tabular/matrix and chart reports.
> - I want to be able to show group headers and footers, as well as page
> headers and footers.
MS local report is a bit not as fancy as RS report can be.
> - I want to have full access to all tables in the database, and not
> being restricted once I select on table, or entity.
That has little to do with reporting, local or server.
> Basically, I want to use the Reporting Service, but I don't want to
> loose the freedom in data selection that Crystal Report gives me.
Do not know what "Data selection freedom" means here.
With local report, you can connect to whatever data source. If needed, you
can use code do trasform anything into a DataSet/Table of your desired
schema and use it as the report source, I'd think it is complete freedom.
With SQL Server RS, if the report data is difficult to access by reqular
queries, or the data source is not conventinal database, you can write your
own Data Processing Extensions sitting between the reporting processor and
data source. Of course, this requires lots of coding.|||> According to your description, you need to use both SQL Server Reporting
> Services and local report tool, which is bundled with VS2005/8 (VS2003 is
> bundled with CrystalReport.NET as local report tool, while VS2005/8 come
> with both CrystalReport.NET and MS report tool).
We use VS2008. I would like keep the option of using the report server
open, but my primary concern is local reports.
> More comments inline.
Cool. :)
> > - A way of designing local reports and setting the data source at
> > runtime.
> If you have VS2005/8, you can do local report with either CrystalReport.NET
> or MS report tool. By "Local". If you use SQL Server RS, I'd use MS report
> tool in VS for local report, because the report viewer control can render
> both local report and report from SQL Server RS. So, you app can seemlessly
> dispaly report either from local report or from SQL Server RS without user
> knowing the difference.
I finally managed to actually get the report designer working (it is
not easy to handle, when you are used to using Crystal Reports). It
looks very promising, however as it turns out, I have to supply the
data source "manually" when using the report locally. That is fine,
not a problem. However, I would like to use the SQL embedded in the
report, but that seems to be somewhat difficult to get at. So far I
have managed to get it by using XPath, but I can't help thinking that
there must be an easier way.
> MS local report is a bit not as fancy as RS report can be.
True, but I AM making progress in understanding the limitations and
differences.
> > - I want to have full access to all tables in the database, and not
> > being restricted once I select on table, or entity.
> That has little to do with reporting, local or server.
Well, after I "discovered" the report designer in Sql Server Business
Intelligence Development Studio (what a mouthful), I see that. Now I
just need to get a handle on the embedded SQL.
> > Basically, I want to use the Reporting Service, but I don't want to
> > loose the freedom in data selection that Crystal Report gives me.
> Do not know what "Data selection freedom" means here.
SQL. I don't want to be relying on some obscure model. Direct SQL
input is my preferred method of pulling data. Crystal Reports can do
both, and after discover the report designer in BI studio it looks
very promising.
> With local report, you can connect to whatever data source. If needed, you
> can use code do trasform anything into a DataSet/Table of your desired
> schema and use it as the report source, I'd think it is complete freedom.
> With SQL Server RS, if the report data is difficult to access by reqular
> queries, or the data source is not conventinal database, you can write your
> own Data Processing Extensions sitting between the reporting processor and
> data source. Of course, this requires lots of coding.
Coding doesn't scare me, I wouldn't be a software developer otherwise
*grin*
Regards,
Thomas
Subscribe to:
Posts (Atom)