Showing posts with label local. Show all posts
Showing posts with label local. Show all posts

Friday, March 30, 2012

Mirroring and replication

Hi MSSQL friend,

We have a SQL2005 server which contains some replicated databases. We use merge replication and the publications are all local.

In order to make the server failsafe we need some kind of mirroring. Is this possible with replication?

Any ideas how to accomplish a failsafe scenario with replication?

Sincerely Edward

You can start by searching SQL Server Books Online, I searched for "replication mirroring" and found this:

Replication and Database Mirroring - http://msdn2.microsoft.com/en-us/library/ms151799.aspx

|||Thanks Greg!sql

Friday, March 23, 2012

Minimum rights for a user to run SQL Server service?

Hi fellows
I was just wondering what the minimum rights a local user
must have to be able to run the MSSQLserver service.
Have been using a user that is administrator on the server
but now i would like to know what the minimum requirments
are for running MSSQLServer service are?
Absolut minimum :-)
Thanks in advance
Risun"Risun" <risun@.wmdata.com> wrote in message
news:0c0d01c39196$5ec6e1c0$a001280a@.phx.gbl...
> I was just wondering what the minimum rights a local user
> must have to be able to run the MSSQLserver service.
> Have been using a user that is administrator on the server
> but now i would like to know what the minimum requirments
> are for running MSSQLServer service are?
> Absolut minimum :-)
You could run the MSSQLServer service account as LocalSystem, no user
account required...
This article does a good job of outlining the account requirements to
properly lock down SQL Server server.
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn
ol/sql/maintain/security/sp3sec/SP3SEC01.ASP
Steve|||If you go to SQL Server download and download Books On Line SP3. This will
tell you what rights the account needs. Search for "Setting up Windows
Services Accounts" and you will fin all the info you need.
--
Barry McAuslin
Look inside your SQL Server files with SQL File Explorer.
Go to http://www.sqlfe.com for more information.
"Risun" <risun@.wmdata.com> wrote in message
news:0c0d01c39196$5ec6e1c0$a001280a@.phx.gbl...
> Hi fellows
> I was just wondering what the minimum rights a local user
> must have to be able to run the MSSQLserver service.
> Have been using a user that is administrator on the server
> but now i would like to know what the minimum requirments
> are for running MSSQLServer service are?
> Absolut minimum :-)
> Thanks in advance
> Risunsql

Wednesday, March 21, 2012

Minimum level of rights for a SQL Server DBA.

Previously, DBAs in our company used to have local machine administrator
access on the SQL Server boxes. As part of tightening server security, those
rights have been taken away from DBAs (in some cases they have been added to
'Power Users' group).
In order to install SQL Server, the account need to be a local machine
administrator (that's given otherwise installation gives error).
But, what type of minimal rights should be given to DBAs on the server
resources to let that person function properly?
When I am talking about resources, I mean rights to write to specific
directories like
* SQL Server programs/tools
* Common DLLs (in C:\Program files\common files...)
* Local backup directories
* Directory for snapshot/transactional replication transfer data.
And right to execute programs/utilities on the server like
* Perfmon (for system tuning/performance monitoring)
* Services (starting/stopping MSSQLSERVER/SQL Agent esp. if there are
dependencies).
Is there anything that is not needed here or, alternatively, is there
anything that I missed?
Another dimension of this issue is the OS login access that is needed to run
the SQL Server services (needed for remote backups and replication).
Any help will be greatly appreciated!
Regards,
MZeeshan
At my last company, I didnt have admin rights... just SA. 90% of the time
it was fine. The other 10% it sucked. Common things I needed someone to hold
my hand on were:
1. Service restarts.
2. Hotfix/ service packs.
3. Set up stuff like Log Shipping where directory access is needed.
4. Wanting to just see how much disk space I had left on my backup drive.
5. Replication Snapshot.
I know you already mentioned alot of these. The problem is that when the DBA
needs these things, alot of time he needs them NOW. Not once he can have
someone come to his desk and log in as Admin. But like I said, 90% of the
time it was fine and I actually would prefer it. SA is usually good enough.
Any less than SA and a DBA cant get his work done.
"MZeeshan" <mzeeshan@.community.nospam> wrote in message
news:CD58C09D-1874-46A3-AA05-344727CA35F3@.microsoft.com...
> Previously, DBAs in our company used to have local machine administrator
> access on the SQL Server boxes. As part of tightening server security,
> those
> rights have been taken away from DBAs (in some cases they have been added
> to
> 'Power Users' group).
> In order to install SQL Server, the account need to be a local machine
> administrator (that's given otherwise installation gives error).
> But, what type of minimal rights should be given to DBAs on the server
> resources to let that person function properly?
> When I am talking about resources, I mean rights to write to specific
> directories like
> * SQL Server programs/tools
> * Common DLLs (in C:\Program files\common files...)
> * Local backup directories
> * Directory for snapshot/transactional replication transfer data.
> And right to execute programs/utilities on the server like
> * Perfmon (for system tuning/performance monitoring)
> * Services (starting/stopping MSSQLSERVER/SQL Agent esp. if there are
> dependencies).
> Is there anything that is not needed here or, alternatively, is there
> anything that I missed?
> Another dimension of this issue is the OS login access that is needed to
> run
> the SQL Server services (needed for remote backups and replication).
> Any help will be greatly appreciated!
> --
> Regards,
> MZeeshan
>
|||Thanks!
Anyone? any other ideas?
Regards,
MZeeshan
"ChrisR" wrote:

> At my last company, I didnt have admin rights... just SA. 90% of the time
> it was fine. The other 10% it sucked. Common things I needed someone to hold
> my hand on were:
> 1. Service restarts.
> 2. Hotfix/ service packs.
> 3. Set up stuff like Log Shipping where directory access is needed.
> 4. Wanting to just see how much disk space I had left on my backup drive.
> 5. Replication Snapshot.
> I know you already mentioned alot of these. The problem is that when the DBA
> needs these things, alot of time he needs them NOW. Not once he can have
> someone come to his desk and log in as Admin. But like I said, 90% of the
> time it was fine and I actually would prefer it. SA is usually good enough.
> Any less than SA and a DBA cant get his work done.
>
> "MZeeshan" <mzeeshan@.community.nospam> wrote in message
> news:CD58C09D-1874-46A3-AA05-344727CA35F3@.microsoft.com...
>
>
|||Hi MZeeshan,
If you need OS login access that is needed to run the SQL Server services
(needed for remote backups and replication). I think give DBA local
administrator privilege is necessary.
BTW, you are recommanded using the tools below to ensure the security of
your product server.
Best Practices Analyzer Tool for Microsoft SQL Server 2000 1.0
http://www.microsoft.com/downloads/d...=en&familyid=B
352EB1F-D3CA-44EE-893E-9E07339C1F22&displaylang=en
Since this is a consultation type issue, you can contact Advisory Services
(AS) . Microsoft Advisory Services provides short-term advice and guidance
for problems not covered by Problem Resolution Service as well as requests
for consultative assistance for design, development and deployment issues.
You may call this number to get Advisory Services: (800) 936-5200.
Sincerely yours,
Michael Cheng
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.

Minimum level of rights for a SQL Server DBA.

Previously, DBAs in our company used to have local machine administrator
access on the SQL Server boxes. As part of tightening server security, those
rights have been taken away from DBAs (in some cases they have been added to
'Power Users' group).
In order to install SQL Server, the account need to be a local machine
administrator (that's given otherwise installation gives error).
But, what type of minimal rights should be given to DBAs on the server
resources to let that person function properly?
When I am talking about resources, I mean rights to write to specific
directories like
* SQL Server programs/tools
* Common DLLs (in C:\Program files\common files...)
* Local backup directories
* Directory for snapshot/transactional replication transfer data.
And right to execute programs/utilities on the server like
* Perfmon (for system tuning/performance monitoring)
* Services (starting/stopping MSSQLSERVER/SQL Agent esp. if there are
dependencies).
Is there anything that is not needed here or, alternatively, is there
anything that I missed?
Another dimension of this issue is the OS login access that is needed to run
the SQL Server services (needed for remote backups and replication).
Any help will be greatly appreciated!
--
Regards,
MZeeshanAt my last company, I didnt have admin rights... just SA. 90% of the time
it was fine. The other 10% it sucked. Common things I needed someone to hold
my hand on were:
1. Service restarts.
2. Hotfix/ service packs.
3. Set up stuff like Log Shipping where directory access is needed.
4. Wanting to just see how much disk space I had left on my backup drive.
5. Replication Snapshot.
I know you already mentioned alot of these. The problem is that when the DBA
needs these things, alot of time he needs them NOW. Not once he can have
someone come to his desk and log in as Admin. But like I said, 90% of the
time it was fine and I actually would prefer it. SA is usually good enough.
Any less than SA and a DBA cant get his work done.
"MZeeshan" <mzeeshan@.community.nospam> wrote in message
news:CD58C09D-1874-46A3-AA05-344727CA35F3@.microsoft.com...
> Previously, DBAs in our company used to have local machine administrator
> access on the SQL Server boxes. As part of tightening server security,
> those
> rights have been taken away from DBAs (in some cases they have been added
> to
> 'Power Users' group).
> In order to install SQL Server, the account need to be a local machine
> administrator (that's given otherwise installation gives error).
> But, what type of minimal rights should be given to DBAs on the server
> resources to let that person function properly?
> When I am talking about resources, I mean rights to write to specific
> directories like
> * SQL Server programs/tools
> * Common DLLs (in C:\Program files\common files...)
> * Local backup directories
> * Directory for snapshot/transactional replication transfer data.
> And right to execute programs/utilities on the server like
> * Perfmon (for system tuning/performance monitoring)
> * Services (starting/stopping MSSQLSERVER/SQL Agent esp. if there are
> dependencies).
> Is there anything that is not needed here or, alternatively, is there
> anything that I missed?
> Another dimension of this issue is the OS login access that is needed to
> run
> the SQL Server services (needed for remote backups and replication).
> Any help will be greatly appreciated!
> --
> Regards,
> MZeeshan
>|||Thanks!
Anyone? any other ideas?
--
Regards,
MZeeshan
"ChrisR" wrote:
> At my last company, I didnt have admin rights... just SA. 90% of the time
> it was fine. The other 10% it sucked. Common things I needed someone to hold
> my hand on were:
> 1. Service restarts.
> 2. Hotfix/ service packs.
> 3. Set up stuff like Log Shipping where directory access is needed.
> 4. Wanting to just see how much disk space I had left on my backup drive.
> 5. Replication Snapshot.
> I know you already mentioned alot of these. The problem is that when the DBA
> needs these things, alot of time he needs them NOW. Not once he can have
> someone come to his desk and log in as Admin. But like I said, 90% of the
> time it was fine and I actually would prefer it. SA is usually good enough.
> Any less than SA and a DBA cant get his work done.
>
> "MZeeshan" <mzeeshan@.community.nospam> wrote in message
> news:CD58C09D-1874-46A3-AA05-344727CA35F3@.microsoft.com...
> > Previously, DBAs in our company used to have local machine administrator
> > access on the SQL Server boxes. As part of tightening server security,
> > those
> > rights have been taken away from DBAs (in some cases they have been added
> > to
> > 'Power Users' group).
> >
> > In order to install SQL Server, the account need to be a local machine
> > administrator (that's given otherwise installation gives error).
> >
> > But, what type of minimal rights should be given to DBAs on the server
> > resources to let that person function properly?
> >
> > When I am talking about resources, I mean rights to write to specific
> > directories like
> > * SQL Server programs/tools
> > * Common DLLs (in C:\Program files\common files...)
> > * Local backup directories
> > * Directory for snapshot/transactional replication transfer data.
> >
> > And right to execute programs/utilities on the server like
> >
> > * Perfmon (for system tuning/performance monitoring)
> > * Services (starting/stopping MSSQLSERVER/SQL Agent esp. if there are
> > dependencies).
> >
> > Is there anything that is not needed here or, alternatively, is there
> > anything that I missed?
> >
> > Another dimension of this issue is the OS login access that is needed to
> > run
> > the SQL Server services (needed for remote backups and replication).
> >
> > Any help will be greatly appreciated!
> >
> > --
> > Regards,
> > MZeeshan
> >
>
>|||Hi MZeeshan,
If you need OS login access that is needed to run the SQL Server services
(needed for remote backups and replication). I think give DBA local
administrator privilege is necessary.
BTW, you are recommanded using the tools below to ensure the security of
your product server.
Best Practices Analyzer Tool for Microsoft SQL Server 2000 1.0
http://www.microsoft.com/downloads/details.aspx?displayla%20ng=en&familyid=B
352EB1F-D3CA-44EE-893E-9E07339C1F22&displaylang=en
Since this is a consultation type issue, you can contact Advisory Services
(AS) . Microsoft Advisory Services provides short-term advice and guidance
for problems not covered by Problem Resolution Service as well as requests
for consultative assistance for design, development and deployment issues.
You may call this number to get Advisory Services: (800) 936-5200.
Sincerely yours,
Michael Cheng
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.

Minimum level of rights for a SQL Server DBA.

Previously, DBAs in our company used to have local machine administrator
access on the SQL Server boxes. As part of tightening server security, those
rights have been taken away from DBAs (in some cases they have been added to
'Power Users' group).
In order to install SQL Server, the account need to be a local machine
administrator (that's given otherwise installation gives error).
But, what type of minimal rights should be given to DBAs on the server
resources to let that person function properly?
When I am talking about resources, I mean rights to write to specific
directories like
* SQL Server programs/tools
* Common DLLs (in C:\Program files\common files...)
* Local backup directories
* Directory for snapshot/transactional replication transfer data.
And right to execute programs/utilities on the server like
* Perfmon (for system tuning/performance monitoring)
* Services (starting/stopping MSSQLSERVER/SQL Agent esp. if there are
dependencies).
Is there anything that is not needed here or, alternatively, is there
anything that I missed?
Another dimension of this issue is the OS login access that is needed to run
the SQL Server services (needed for remote backups and replication).
Any help will be greatly appreciated!
Regards,
MZeeshanAt my last company, I didnt have admin rights... just SA. 90% of the time
it was fine. The other 10% it sucked. Common things I needed someone to hold
my hand on were:
1. Service restarts.
2. Hotfix/ service packs.
3. Set up stuff like Log Shipping where directory access is needed.
4. Wanting to just see how much disk space I had left on my backup drive.
5. Replication Snapshot.
I know you already mentioned alot of these. The problem is that when the DBA
needs these things, alot of time he needs them NOW. Not once he can have
someone come to his desk and log in as Admin. But like I said, 90% of the
time it was fine and I actually would prefer it. SA is usually good enough.
Any less than SA and a DBA cant get his work done.
"MZeeshan" <mzeeshan@.community.nospam> wrote in message
news:CD58C09D-1874-46A3-AA05-344727CA35F3@.microsoft.com...
> Previously, DBAs in our company used to have local machine administrator
> access on the SQL Server boxes. As part of tightening server security,
> those
> rights have been taken away from DBAs (in some cases they have been added
> to
> 'Power Users' group).
> In order to install SQL Server, the account need to be a local machine
> administrator (that's given otherwise installation gives error).
> But, what type of minimal rights should be given to DBAs on the server
> resources to let that person function properly?
> When I am talking about resources, I mean rights to write to specific
> directories like
> * SQL Server programs/tools
> * Common DLLs (in C:\Program files\common files...)
> * Local backup directories
> * Directory for snapshot/transactional replication transfer data.
> And right to execute programs/utilities on the server like
> * Perfmon (for system tuning/performance monitoring)
> * Services (starting/stopping MSSQLSERVER/SQL Agent esp. if there are
> dependencies).
> Is there anything that is not needed here or, alternatively, is there
> anything that I missed?
> Another dimension of this issue is the OS login access that is needed to
> run
> the SQL Server services (needed for remote backups and replication).
> Any help will be greatly appreciated!
> --
> Regards,
> MZeeshan
>|||Thanks!
Anyone? any other ideas?
--
Regards,
MZeeshan
"ChrisR" wrote:

> At my last company, I didnt have admin rights... just SA. 90% of the time
> it was fine. The other 10% it sucked. Common things I needed someone to ho
ld
> my hand on were:
> 1. Service restarts.
> 2. Hotfix/ service packs.
> 3. Set up stuff like Log Shipping where directory access is needed.
> 4. Wanting to just see how much disk space I had left on my backup drive.
> 5. Replication Snapshot.
> I know you already mentioned alot of these. The problem is that when the D
BA
> needs these things, alot of time he needs them NOW. Not once he can have
> someone come to his desk and log in as Admin. But like I said, 90% of the
> time it was fine and I actually would prefer it. SA is usually good enough
.
> Any less than SA and a DBA cant get his work done.
>
> "MZeeshan" <mzeeshan@.community.nospam> wrote in message
> news:CD58C09D-1874-46A3-AA05-344727CA35F3@.microsoft.com...
>
>|||Hi MZeeshan,
If you need OS login access that is needed to run the SQL Server services
(needed for remote backups and replication). I think give DBA local
administrator privilege is necessary.
BTW, you are recommanded using the tools below to ensure the security of
your product server.
Best Practices Analyzer Tool for Microsoft SQL Server 2000 1.0
http://www.microsoft.com/downloads/...g=en&familyid=B
352EB1F-D3CA-44EE-893E-9E07339C1F22&displaylang=en
Since this is a consultation type issue, you can contact Advisory Services
(AS) . Microsoft Advisory Services provides short-term advice and guidance
for problems not covered by Problem Resolution Service as well as requests
for consultative assistance for design, development and deployment issues.
You may call this number to get Advisory Services: (800) 936-5200.
Sincerely yours,
Michael Cheng
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.

Friday, March 9, 2012

Migration to sql server on network for access database

hi,

I migrated the Northwind database using SQL Migration Assistant for Access. it worked fine and I was able to link the access forms to Local machine SQL Server 2005 and it worked fine.

Now i want to link the same Northwind access database to Another Server on the network.

When i try to run the wizard again, it won't migrate the user objects like tables to server, it will just create a database and that is it.

it will give me this error too.

No User objects were selected.

any idea,

Thanks,


Fahim

Since you have already migrated to your local SQL Server, you could use the Import/Export Wizard to move the tables to a different SQL Server.

In the Object Explorer, right-click on the database, select [Task..], and then click on Export Data...

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