Showing posts with label apparently. Show all posts
Showing posts with label apparently. Show all posts

Friday, March 30, 2012

Newbie question on Reporting Services

The shop I work in is new to SQL Server and this fall we are installing
Sql Server 2005 with Reporting Services. Apparently the application the
database will support will use Reporting Services. A question is
arising on whether the created report(s) is considered a database
object. That is, if one creates and saves off a report in Test, is this
report migrated to production or is the same object in the same
location simply used by production?
Many thanks in advance.
GerryYou deploy reports to the server. If you have a test server and a
development server, the best is to deploy it to test and then when you are
ready, deploy it to production. Reporting services stores the report
metadata in the database. RS is an asp.net application that heavily uses the
database for its object/metadata storage, scheduling etc.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<datapro01@.yahoo.com> wrote in message
news:1156342425.017659.314250@.74g2000cwt.googlegroups.com...
> The shop I work in is new to SQL Server and this fall we are installing
> Sql Server 2005 with Reporting Services. Apparently the application the
> database will support will use Reporting Services. A question is
> arising on whether the created report(s) is considered a database
> object. That is, if one creates and saves off a report in Test, is this
> report migrated to production or is the same object in the same
> location simply used by production?
>
> Many thanks in advance.
> Gerry
>|||Thanks Bruce
Bruce L-C [MVP] wrote:
> You deploy reports to the server. If you have a test server and a
> development server, the best is to deploy it to test and then when you are
> ready, deploy it to production. Reporting services stores the report
> metadata in the database. RS is an asp.net application that heavily uses the
> database for its object/metadata storage, scheduling etc.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> <datapro01@.yahoo.com> wrote in message
> news:1156342425.017659.314250@.74g2000cwt.googlegroups.com...
> > The shop I work in is new to SQL Server and this fall we are installing
> > Sql Server 2005 with Reporting Services. Apparently the application the
> > database will support will use Reporting Services. A question is
> > arising on whether the created report(s) is considered a database
> > object. That is, if one creates and saves off a report in Test, is this
> > report migrated to production or is the same object in the same
> > location simply used by production?
> >
> >
> > Many thanks in advance.
> > Gerry
> >

Monday, March 19, 2012

Newbie needs help with SQL 2000

I currently use Dreamweaver MX, ASP, MS Access & VBScript - but apparently I
need to get something more stable -

I have been told that the best option would be MS SQL2000 - however, I
really don't know where to start.

Can anybody point me in the right direction of a "simple" step by step
tutorial to get me started with this.

Thanks guys!Paul wrote:

> I currently use Dreamweaver MX, ASP, MS Access & VBScript - but apparently I
> need to get something more stable -
> I have been told that the best option would be MS SQL2000 - however, I
> really don't know where to start.
> Can anybody point me in the right direction of a "simple" step by step
> tutorial to get me started with this.
> Thanks guys!

What makes you think that the data storage is the cause of the stability
problems? What types of problems are you having? Honestly, given that
mix of web code, I'd bet $1 that the stability issues reside in the code
and not in your database. Before you make the drastic and expensive
switch to SQL server, I recommend you do some additional research into
your problem.

Zach|||Hi Zach

Thanks for the reply

Basically, we have had a few problems with the database going corrupt on us
as well as the speed issue-

As I only want to develop the website ive been told that I only need to get
the Microsoft Desktop Engine (rather than the Server package itself), or I
could manage it via MS Access (ODBC)

Is this correct?

Thanks again

"Zach Wells" <individual_news@.nibsworld.com> wrote in message
news:2gc868F12nd1U1@.uni-berlin.de...
> Paul wrote:
> > I currently use Dreamweaver MX, ASP, MS Access & VBScript - but
apparently I
> > need to get something more stable -
> > I have been told that the best option would be MS SQL2000 - however, I
> > really don't know where to start.
> > Can anybody point me in the right direction of a "simple" step by step
> > tutorial to get me started with this.
> > Thanks guys!
> What makes you think that the data storage is the cause of the stability
> problems? What types of problems are you having? Honestly, given that
> mix of web code, I'd bet $1 that the stability issues reside in the code
> and not in your database. Before you make the drastic and expensive
> switch to SQL server, I recommend you do some additional research into
> your problem.
> Zach|||Paul wrote:

> Hi Zach
> Thanks for the reply
> Basically, we have had a few problems with the database going corrupt on us
> as well as the speed issue-
> As I only want to develop the website ive been told that I only need to get
> the Microsoft Desktop Engine (rather than the Server package itself), or I
> could manage it via MS Access (ODBC)
> Is this correct?
> Thanks again

Yes, MSDE would be a cheaper alternative. I honestly don't know a whole
lot about it so I don't know what kind of licensing issues you'll run
into when using it for a web back-end.

Zach