Showing posts with label services. Show all posts
Showing posts with label services. Show all posts

Thursday, March 29, 2012

Determine what version of RS is insalled

How do you determine what version of Reporting Services is installed int the DB and Web server ( I have the DB on a different server than the Web server)

Thanks

Try typing
http://localhost/Reportserver

Determine what ver/SP is installed for Reporting Services

How can you tell what version of Reporting Services is installed?Just run the url http://localhost/ReportServer or
http://<hostname>/ReportServer|||That is where to look, however I didn't know what the numbers meant. I
found this in another thread:
base install = 743
sp1 = 878
sp2 = 1042|||If you run the url. at the bottom it will display the version information
like following
Microsoft SQL Server Reporting Services Version 8.00.1038.00sql

Tuesday, March 27, 2012

Determine service pack version of Analysis Services using AMO

Hi,

Our product uses features that require Analysis Services SP2 to be installed. How can I tell if an Analysis Services server is running SP2 or higher using Analysis Services Management Objects (AMO)? I'm not concerned about the Operating System service pack edition, I'm concerned about the SP version of Analysis Services.

Thanks.

Figured it out. Use the Version property off the Server object.

Server svr = new Server();

svr.Connect(serverName);

Version minASVersion = new Version(MIN_AS_SERVICES_VERSION);

Version serverVersion = new Version(svr.Version);

if (serverVersion < minASVersion)

{

// error

}

|||

You can get this using ADOMD too:

http://geekswithblogs.net/darrengosbell/archive/2007/07/14/SSAS-Detecting-the-version-of-SSAS-on-a-given-server.aspx

sql

Sunday, March 25, 2012

Determine Edition in Reporting Services 2000

This may be a simple question, but I need to determine which edition of
Reporting Services I have installed on my SQL Server 2000 server. I have
already confirmed that I am running Enterprise Edition for SQL Server itself,
but cannot find anything that will give me version/edition information for
Reporting Services.
Any help would be greatly appreciated.
Daniel InmanNow I feel stupid. All you need to do is go into Add/Remove programs.
"Daniel Inman" wrote:
> This may be a simple question, but I need to determine which edition of
> Reporting Services I have installed on my SQL Server 2000 server. I have
> already confirmed that I am running Enterprise Edition for SQL Server itself,
> but cannot find anything that will give me version/edition information for
> Reporting Services.
> Any help would be greatly appreciated.
> Daniel Inman
>|||An even simpler alternative is to go to the following url:
http://rsservername/reportserver/
Of course, replace "rsservername" with the real name of your Reporting
Services Server. You'll see the version number at the bottom of that
screen.
Daniel Inman wrote:
> Now I feel stupid. All you need to do is go into Add/Remove programs.
> "Daniel Inman" wrote:
> > This may be a simple question, but I need to determine which edition of
> > Reporting Services I have installed on my SQL Server 2000 server. I have
> > already confirmed that I am running Enterprise Edition for SQL Server itself,
> > but cannot find anything that will give me version/edition information for
> > Reporting Services.
> >
> > Any help would be greatly appreciated.
> >
> > Daniel Inman
> >sql

Sunday, March 11, 2012

detaching db and stopping services

Is the state of SQL Server 2000 files the same:
1) when you detach them (run sp_detach-db); and
2) when you stop all SQL Server services, particularly MSSQL$SQL2000 ?
In other words, when you stop the service, are the db files utomatically
put in the detached state, as if you had run sp_detach-db on them ?
If not, what is the difference between the files when the service is
stopped, and when they are in the detached state ?
Thanks
-- MikeNo, they are not the same.
sp_detach_db ensures that your files can be attached.
Simply grabbing the files from a stopped instance will not guarantee that
you can recover them.
Are you trying to implement a backup routine? Do you want 100% availability
during the backups? Look into the Transact-SQL BACKUP command. Information
and examples can be found within Books Online (within the SQL Server program
group).
--
Keith
"MikeF" <mrf@.sent.com> wrote in message
news:uSyKDRsfEHA.1356@.TK2MSFTNGP09.phx.gbl...
> Is the state of SQL Server 2000 files the same:
> 1) when you detach them (run sp_detach-db); and
> 2) when you stop all SQL Server services, particularly MSSQL$SQL2000 ?
> In other words, when you stop the service, are the db files utomatically
> put in the detached state, as if you had run sp_detach-db on them ?
> If not, what is the difference between the files when the service is
> stopped, and when they are in the detached state ?
> Thanks
> -- Mike
>|||I do not think the state MUST be the same... When you detach a file, there
can be no in-process transactions.
I believe that stopping the service is more 'rude'... I don't think it waits
for transactions to complete. Stopping the service through SEM or the
Service manager does wait, stopping through control panel services or net
stop does not...
Even if the state were the same, remember that detach removes all references
from master as well..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"MikeF" <mrf@.sent.com> wrote in message
news:uSyKDRsfEHA.1356@.TK2MSFTNGP09.phx.gbl...
> Is the state of SQL Server 2000 files the same:
> 1) when you detach them (run sp_detach-db); and
> 2) when you stop all SQL Server services, particularly MSSQL$SQL2000 ?
> In other words, when you stop the service, are the db files utomatically
> put in the detached state, as if you had run sp_detach-db on them ?
> If not, what is the difference between the files when the service is
> stopped, and when they are in the detached state ?
> Thanks
> -- Mike
>|||When you detach a database, a checkpoint happens in the database. That means
that all changed that have been made to datapages but that haven't been
written to the data file yet, are written to disk. All these changes are of
course already in the transaction log.
Shutting down SQL Services should perform a check point as well, but IIRC
the documentation in Books Online (see SHUTDOWN) is not complete at this
point. If the server or service fails, you will in most cases not have a
properly check pointed data file, and you will need the transaction log to
recover your database.
It is definitely recommended that if you want to attach a database to
another server, that you use sp_detachdb.
--
Jacco Schalkwijk
SQL Server MVP
"MikeF" <mrf@.sent.com> wrote in message
news:uSyKDRsfEHA.1356@.TK2MSFTNGP09.phx.gbl...
> Is the state of SQL Server 2000 files the same:
> 1) when you detach them (run sp_detach-db); and
> 2) when you stop all SQL Server services, particularly MSSQL$SQL2000 ?
> In other words, when you stop the service, are the db files utomatically
> put in the detached state, as if you had run sp_detach-db on them ?
> If not, what is the difference between the files when the service is
> stopped, and when they are in the detached state ?
> Thanks
> -- Mike
>|||Wayne Snyder wrote:
> I do not think the state MUST be the same... When you detach a file, there
> can be no in-process transactions.
> I believe that stopping the service is more 'rude'... I don't think it waits
> for transactions to complete. Stopping the service through SEM or the
> Service manager does wait, stopping through control panel services or net
> stop does not...
> Even if the state were the same, remember that detach removes all references
> from master as well..
>
Thanks Wayne, that is very interesting.
Are you saying that IF the service MSSQL$SQL2000 is stopped using SQL
Server Service Manager, then the db files ARE in exactly the same state
as if they were detached using sp_detach_db '
I would appreciate your confirming this.
-- Mike|||Jacco Schalkwijk wrote:
> When you detach a database, a checkpoint happens in the database. That means
> that all changed that have been made to datapages but that haven't been
> written to the data file yet, are written to disk. All these changes are of
> course already in the transaction log.
> Shutting down SQL Services should perform a check point as well, but IIRC
> the documentation in Books Online (see SHUTDOWN) is not complete at this
> point. If the server or service fails, you will in most cases not have a
> properly check pointed data file, and you will need the transaction log to
> recover your database.
> It is definitely recommended that if you want to attach a database to
> another server, that you use sp_detachdb.
>
Thanks Jacco. What do you think of Wayne's point that if the service
MSSQL$SQL2000 is stopped using SQL Server Service Manager, then the db
files ARE in exactly the same state as if they were detached using
sp_detach_db '
I understand that using sp_detach_db is the proper way to do it, and we
are doing it that way, but this is a peculiar configuration I am trying
to work with and I need to know if using SQL Server Service Manager to
stop the service is actually the same as using sp_detach_db, like Wayne
suggests.
Many thanks for your time.
-- Mike|||Keith Kratochvil wrote:
> No, they are not the same.
> sp_detach_db ensures that your files can be attached.
> Simply grabbing the files from a stopped instance will not guarantee that
> you can recover them.
> Are you trying to implement a backup routine? Do you want 100% availability
> during the backups? Look into the Transact-SQL BACKUP command. Information
> and examples can be found within Books Online (within the SQL Server program
> group).
>
Thanks Keith. What do you think of Wayne's point that if the service
MSSQL$SQL2000 is stopped using SQL Server Service Manager, then the db
files ARE in exactly the same state as if they were detached using
sp_detach_db '
I am not doing a backup routine (or at least, I am the recommended way
using sp_detach_db) but I am working with a peculiar configuration with
some odd restraints, and and I need to know if using SQL Server Service
Manager to stop the service is actually the same as using sp_detach_db,
like Wayne suggests.
Many thanks for your time.
-- Mike|||I believe the safest option is to issue sp_detach_db.
I have read a few posts within the newsgroups along the lines of "I did not
detach my database (I copied the mdf and ldf files when the services were
stopped) and now I cannot attach my database. Help!"
I know that it should be possible to attach databases that have not been
explicitly detached, but if I wanted to make sure that I could recover
(attach) my databases I would issue a detach statement first.
--
Keith
"MikeF" <mrf@.sent.com> wrote in message
news:%23R1$2CufEHA.904@.TK2MSFTNGP09.phx.gbl...
> Keith Kratochvil wrote:
> > No, they are not the same.
> > sp_detach_db ensures that your files can be attached.
> > Simply grabbing the files from a stopped instance will not guarantee
that
> > you can recover them.
> >
> > Are you trying to implement a backup routine? Do you want 100%
availability
> > during the backups? Look into the Transact-SQL BACKUP command.
Information
> > and examples can be found within Books Online (within the SQL Server
program
> > group).
> >
> Thanks Keith. What do you think of Wayne's point that if the service
> MSSQL$SQL2000 is stopped using SQL Server Service Manager, then the db
> files ARE in exactly the same state as if they were detached using
> sp_detach_db '
> I am not doing a backup routine (or at least, I am the recommended way
> using sp_detach_db) but I am working with a peculiar configuration with
> some odd restraints, and and I need to know if using SQL Server Service
> Manager to stop the service is actually the same as using sp_detach_db,
> like Wayne suggests.
> Many thanks for your time.
> -- Mike
>|||Practically speaking shutting down the database (in whatever way) and using
sp_detach_db are NOT the same. Theoretically they more or less should be the
same, but attaching databases that haven't been explicitly detached has been
a hit-and-miss experience for a lot of users.
--
Jacco Schalkwijk
SQL Server MVP
"MikeF" <mrf@.sent.com> wrote in message
news:%23nPAyBufEHA.904@.TK2MSFTNGP09.phx.gbl...
> Jacco Schalkwijk wrote:
>> When you detach a database, a checkpoint happens in the database. That
>> means that all changed that have been made to datapages but that haven't
>> been written to the data file yet, are written to disk. All these changes
>> are of course already in the transaction log.
>> Shutting down SQL Services should perform a check point as well, but IIRC
>> the documentation in Books Online (see SHUTDOWN) is not complete at this
>> point. If the server or service fails, you will in most cases not have a
>> properly check pointed data file, and you will need the transaction log
>> to recover your database.
>> It is definitely recommended that if you want to attach a database to
>> another server, that you use sp_detachdb.
> Thanks Jacco. What do you think of Wayne's point that if the service
> MSSQL$SQL2000 is stopped using SQL Server Service Manager, then the db
> files ARE in exactly the same state as if they were detached using
> sp_detach_db '
> I understand that using sp_detach_db is the proper way to do it, and we
> are doing it that way, but this is a peculiar configuration I am trying to
> work with and I need to know if using SQL Server Service Manager to stop
> the service is actually the same as using sp_detach_db, like Wayne
> suggests.
> Many thanks for your time.
> -- Mike
>|||IMO, it doesn't matter what anyone of us say (no disrespect to anyone here, I'm just making a point). What
matter is what the documentation say. And the documentation say that you are guaranteed to be able to attach a
db only if you detached it first. (Look up BOL for exact wording.)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"MikeF" <mrf@.sent.com> wrote in message news:%23nPAyBufEHA.904@.TK2MSFTNGP09.phx.gbl...
> Jacco Schalkwijk wrote:
> > When you detach a database, a checkpoint happens in the database. That means
> > that all changed that have been made to datapages but that haven't been
> > written to the data file yet, are written to disk. All these changes are of
> > course already in the transaction log.
> >
> > Shutting down SQL Services should perform a check point as well, but IIRC
> > the documentation in Books Online (see SHUTDOWN) is not complete at this
> > point. If the server or service fails, you will in most cases not have a
> > properly check pointed data file, and you will need the transaction log to
> > recover your database.
> >
> > It is definitely recommended that if you want to attach a database to
> > another server, that you use sp_detachdb.
> >
> Thanks Jacco. What do you think of Wayne's point that if the service
> MSSQL$SQL2000 is stopped using SQL Server Service Manager, then the db
> files ARE in exactly the same state as if they were detached using
> sp_detach_db '
> I understand that using sp_detach_db is the proper way to do it, and we
> are doing it that way, but this is a peculiar configuration I am trying
> to work with and I need to know if using SQL Server Service Manager to
> stop the service is actually the same as using sp_detach_db, like Wayne
> suggests.
> Many thanks for your time.
> -- Mike
>|||MikeF,
I absolutely agree with all of the other posters... It was not my intention
to suggest that shutting down the service by any means is a replacement for
a proper detach...
It is possible that on some occasions you can attach a db file from a
properly shutdown server... However it is risky at best, and something you
try when you have no other alternative...
I though you were just in trouble, and had no options...
Sorry for the mini-controversy...if you INTEND to attach a database, then
ALWAYS properly detach, and NEVER assume that the shutdown is good enough -
it might be, and it might not be...!
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OUlgeXvfEHA.2848@.TK2MSFTNGP10.phx.gbl...
> IMO, it doesn't matter what anyone of us say (no disrespect to anyone
here, I'm just making a point). What
> matter is what the documentation say. And the documentation say that you
are guaranteed to be able to attach a
> db only if you detached it first. (Look up BOL for exact wording.)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "MikeF" <mrf@.sent.com> wrote in message
news:%23nPAyBufEHA.904@.TK2MSFTNGP09.phx.gbl...
> > Jacco Schalkwijk wrote:
> >
> > > When you detach a database, a checkpoint happens in the database. That
means
> > > that all changed that have been made to datapages but that haven't
been
> > > written to the data file yet, are written to disk. All these changes
are of
> > > course already in the transaction log.
> > >
> > > Shutting down SQL Services should perform a check point as well, but
IIRC
> > > the documentation in Books Online (see SHUTDOWN) is not complete at
this
> > > point. If the server or service fails, you will in most cases not have
a
> > > properly check pointed data file, and you will need the transaction
log to
> > > recover your database.
> > >
> > > It is definitely recommended that if you want to attach a database to
> > > another server, that you use sp_detachdb.
> > >
> >
> > Thanks Jacco. What do you think of Wayne's point that if the service
> > MSSQL$SQL2000 is stopped using SQL Server Service Manager, then the db
> > files ARE in exactly the same state as if they were detached using
> > sp_detach_db '
> >
> > I understand that using sp_detach_db is the proper way to do it, and we
> > are doing it that way, but this is a peculiar configuration I am trying
> > to work with and I need to know if using SQL Server Service Manager to
> > stop the service is actually the same as using sp_detach_db, like Wayne
> > suggests.
> >
> > Many thanks for your time.
> >
> > -- Mike
> >
>|||In article <u8crS8sfEHA.2028@.tk2msftngp13.phx.gbl>,
jacco.please.reply@.to.newsgroups.mvps.org.invalid says...
> When you detach a database, a checkpoint happens in the database. That means
> that all changed that have been made to datapages but that haven't been
> written to the data file yet, are written to disk. All these changes are of
> course already in the transaction log.
> Shutting down SQL Services should perform a check point as well, but IIRC
> the documentation in Books Online (see SHUTDOWN) is not complete at this
> point. If the server or service fails, you will in most cases not have a
> properly check pointed data file, and you will need the transaction log to
> recover your database.
> It is definitely recommended that if you want to attach a database to
> another server, that you use sp_detachdb.
What about my case:
I have a standby server that I constantly restore logs to. If I detach
the database in order to back it up, it gets recovered when I re-attach
and the log synchronization gets broken. The database never has any
transactions other than the ones that come in from the production
server's logs as I just use it for large custom queries. Every night I
stop the service, add the data and log to a zip and restart the service.
Isn't this effectively a backup?|||I am confused. Why not backup your live (production) database? After all,
you are almost there with your log-shipping routines? All you need to do is
backup the file(s) created by that process and you should have your database
backup.
--
Keith
"Brad" <brad@.seesigifthere.com> wrote in message
news:MPG.1b83f83cb16eeba0989692@.news...
> In article <u8crS8sfEHA.2028@.tk2msftngp13.phx.gbl>,
> jacco.please.reply@.to.newsgroups.mvps.org.invalid says...
> > When you detach a database, a checkpoint happens in the database. That
means
> > that all changed that have been made to datapages but that haven't been
> > written to the data file yet, are written to disk. All these changes are
of
> > course already in the transaction log.
> >
> > Shutting down SQL Services should perform a check point as well, but
IIRC
> > the documentation in Books Online (see SHUTDOWN) is not complete at this
> > point. If the server or service fails, you will in most cases not have a
> > properly check pointed data file, and you will need the transaction log
to
> > recover your database.
> >
> > It is definitely recommended that if you want to attach a database to
> > another server, that you use sp_detachdb.
> What about my case:
> I have a standby server that I constantly restore logs to. If I detach
> the database in order to back it up, it gets recovered when I re-attach
> and the log synchronization gets broken. The database never has any
> transactions other than the ones that come in from the production
> server's logs as I just use it for large custom queries. Every night I
> stop the service, add the data and log to a zip and restart the service.
> Isn't this effectively a backup?|||In article <uUkfvT7fEHA.1428@.TK2MSFTNGP10.phx.gbl>,
sqlguy.back2u@.comcast.net says...
> I am confused. Why not backup your live (production) database? After all,
> you are almost there with your log-shipping routines? All you need to do is
> backup the file(s) created by that process and you should have your database
> backup.
My standby server is only connected by a T1 and I have about 2GB of log
per day (DB size=50GB). In two weeks of log shipping I have already
blown the standby database once. I basically want a backup of the local
copy (standby) that I can go back to if it gets corrupted. I already
backup the production database, but keep the copy at the datacenter.
I can't backup the standby database through SQL server because it is in
read-only mode. I can't detach and re-attach because it will recover
the database on the re-attach.|||Understood. I was assuming that the two servers were in the same building
connected by a fast network. That assumption was incorrect!
I suggest that you email your wish/request to the SQL Server development
team. sqlwish@.microsoft.com They might not respond to you, but they do
read the emails and our suggestions can make a difference!
--
Keith
"Brad" <brad@.seesigifthere.com> wrote in message
news:MPG.1b8402b4afd7ebef989694@.news...
> In article <uUkfvT7fEHA.1428@.TK2MSFTNGP10.phx.gbl>,
> sqlguy.back2u@.comcast.net says...
> > I am confused. Why not backup your live (production) database? After
all,
> > you are almost there with your log-shipping routines? All you need to
do is
> > backup the file(s) created by that process and you should have your
database
> > backup.
> My standby server is only connected by a T1 and I have about 2GB of log
> per day (DB size=50GB). In two weeks of log shipping I have already
> blown the standby database once. I basically want a backup of the local
> copy (standby) that I can go back to if it gets corrupted. I already
> backup the production database, but keep the copy at the datacenter.
> I can't backup the standby database through SQL server because it is in
> read-only mode. I can't detach and re-attach because it will recover
> the database on the re-attach.|||In that case I would consider your options such as "It will probably work, but it isn't guaranteed".
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Brad" <brad@.seesigifthere.com> wrote in message news:MPG.1b8402b4afd7ebef989694@.news...
> In article <uUkfvT7fEHA.1428@.TK2MSFTNGP10.phx.gbl>,
> sqlguy.back2u@.comcast.net says...
> > I am confused. Why not backup your live (production) database? After all,
> > you are almost there with your log-shipping routines? All you need to do is
> > backup the file(s) created by that process and you should have your database
> > backup.
> My standby server is only connected by a T1 and I have about 2GB of log
> per day (DB size=50GB). In two weeks of log shipping I have already
> blown the standby database once. I basically want a backup of the local
> copy (standby) that I can go back to if it gets corrupted. I already
> backup the production database, but keep the copy at the datacenter.
> I can't backup the standby database through SQL server because it is in
> read-only mode. I can't detach and re-attach because it will recover
> the database on the re-attach.|||That should have been "the attach option" instead of "options".
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
news:ea6AWAKgEHA.3416@.TK2MSFTNGP09.phx.gbl...
> In that case I would consider your options such as "It will probably work, but it isn't guaranteed".
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Brad" <brad@.seesigifthere.com> wrote in message news:MPG.1b8402b4afd7ebef989694@.news...
> > In article <uUkfvT7fEHA.1428@.TK2MSFTNGP10.phx.gbl>,
> > sqlguy.back2u@.comcast.net says...
> > > I am confused. Why not backup your live (production) database? After all,
> > > you are almost there with your log-shipping routines? All you need to do is
> > > backup the file(s) created by that process and you should have your database
> > > backup.
> >
> > My standby server is only connected by a T1 and I have about 2GB of log
> > per day (DB size=50GB). In two weeks of log shipping I have already
> > blown the standby database once. I basically want a backup of the local
> > copy (standby) that I can go back to if it gets corrupted. I already
> > backup the production database, but keep the copy at the datacenter.
> >
> > I can't backup the standby database through SQL server because it is in
> > read-only mode. I can't detach and re-attach because it will recover
> > the database on the re-attach.
>

detaching db and stopping services

Is the state of SQL Server 2000 files the same:
1) when you detach them (run sp_detach-db); and
2) when you stop all SQL Server services, particularly MSSQL$SQL2000 ?
In other words, when you stop the service, are the db files utomatically
put in the detached state, as if you had run sp_detach-db on them ?
If not, what is the difference between the files when the service is
stopped, and when they are in the detached state ?
Thanks
-- Mike
No, they are not the same.
sp_detach_db ensures that your files can be attached.
Simply grabbing the files from a stopped instance will not guarantee that
you can recover them.
Are you trying to implement a backup routine? Do you want 100% availability
during the backups? Look into the Transact-SQL BACKUP command. Information
and examples can be found within Books Online (within the SQL Server program
group).
Keith
"MikeF" <mrf@.sent.com> wrote in message
news:uSyKDRsfEHA.1356@.TK2MSFTNGP09.phx.gbl...
> Is the state of SQL Server 2000 files the same:
> 1) when you detach them (run sp_detach-db); and
> 2) when you stop all SQL Server services, particularly MSSQL$SQL2000 ?
> In other words, when you stop the service, are the db files utomatically
> put in the detached state, as if you had run sp_detach-db on them ?
> If not, what is the difference between the files when the service is
> stopped, and when they are in the detached state ?
> Thanks
> -- Mike
>
|||I do not think the state MUST be the same... When you detach a file, there
can be no in-process transactions.
I believe that stopping the service is more 'rude'... I don't think it waits
for transactions to complete. Stopping the service through SEM or the
Service manager does wait, stopping through control panel services or net
stop does not...
Even if the state were the same, remember that detach removes all references
from master as well..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"MikeF" <mrf@.sent.com> wrote in message
news:uSyKDRsfEHA.1356@.TK2MSFTNGP09.phx.gbl...
> Is the state of SQL Server 2000 files the same:
> 1) when you detach them (run sp_detach-db); and
> 2) when you stop all SQL Server services, particularly MSSQL$SQL2000 ?
> In other words, when you stop the service, are the db files utomatically
> put in the detached state, as if you had run sp_detach-db on them ?
> If not, what is the difference between the files when the service is
> stopped, and when they are in the detached state ?
> Thanks
> -- Mike
>
|||When you detach a database, a checkpoint happens in the database. That means
that all changed that have been made to datapages but that haven't been
written to the data file yet, are written to disk. All these changes are of
course already in the transaction log.
Shutting down SQL Services should perform a check point as well, but IIRC
the documentation in Books Online (see SHUTDOWN) is not complete at this
point. If the server or service fails, you will in most cases not have a
properly check pointed data file, and you will need the transaction log to
recover your database.
It is definitely recommended that if you want to attach a database to
another server, that you use sp_detachdb.
Jacco Schalkwijk
SQL Server MVP
"MikeF" <mrf@.sent.com> wrote in message
news:uSyKDRsfEHA.1356@.TK2MSFTNGP09.phx.gbl...
> Is the state of SQL Server 2000 files the same:
> 1) when you detach them (run sp_detach-db); and
> 2) when you stop all SQL Server services, particularly MSSQL$SQL2000 ?
> In other words, when you stop the service, are the db files utomatically
> put in the detached state, as if you had run sp_detach-db on them ?
> If not, what is the difference between the files when the service is
> stopped, and when they are in the detached state ?
> Thanks
> -- Mike
>
|||Wayne Snyder wrote:

> I do not think the state MUST be the same... When you detach a file, there
> can be no in-process transactions.
> I believe that stopping the service is more 'rude'... I don't think it waits
> for transactions to complete. Stopping the service through SEM or the
> Service manager does wait, stopping through control panel services or net
> stop does not...
> Even if the state were the same, remember that detach removes all references
> from master as well..
>
Thanks Wayne, that is very interesting.
Are you saying that IF the service MSSQL$SQL2000 is stopped using SQL
Server Service Manager, then the db files ARE in exactly the same state
as if they were detached using sp_detach_db ?
I would appreciate your confirming this.
-- Mike
|||Jacco Schalkwijk wrote:

> When you detach a database, a checkpoint happens in the database. That means
> that all changed that have been made to datapages but that haven't been
> written to the data file yet, are written to disk. All these changes are of
> course already in the transaction log.
> Shutting down SQL Services should perform a check point as well, but IIRC
> the documentation in Books Online (see SHUTDOWN) is not complete at this
> point. If the server or service fails, you will in most cases not have a
> properly check pointed data file, and you will need the transaction log to
> recover your database.
> It is definitely recommended that if you want to attach a database to
> another server, that you use sp_detachdb.
>
Thanks Jacco. What do you think of Wayne's point that if the service
MSSQL$SQL2000 is stopped using SQL Server Service Manager, then the db
files ARE in exactly the same state as if they were detached using
sp_detach_db ?
I understand that using sp_detach_db is the proper way to do it, and we
are doing it that way, but this is a peculiar configuration I am trying
to work with and I need to know if using SQL Server Service Manager to
stop the service is actually the same as using sp_detach_db, like Wayne
suggests.
Many thanks for your time.
-- Mike
|||Keith Kratochvil wrote:

> No, they are not the same.
> sp_detach_db ensures that your files can be attached.
> Simply grabbing the files from a stopped instance will not guarantee that
> you can recover them.
> Are you trying to implement a backup routine? Do you want 100% availability
> during the backups? Look into the Transact-SQL BACKUP command. Information
> and examples can be found within Books Online (within the SQL Server program
> group).
>
Thanks Keith. What do you think of Wayne's point that if the service
MSSQL$SQL2000 is stopped using SQL Server Service Manager, then the db
files ARE in exactly the same state as if they were detached using
sp_detach_db ?
I am not doing a backup routine (or at least, I am the recommended way
using sp_detach_db) but I am working with a peculiar configuration with
some odd restraints, and and I need to know if using SQL Server Service
Manager to stop the service is actually the same as using sp_detach_db,
like Wayne suggests.
Many thanks for your time.
-- Mike
|||I believe the safest option is to issue sp_detach_db.
I have read a few posts within the newsgroups along the lines of "I did not
detach my database (I copied the mdf and ldf files when the services were
stopped) and now I cannot attach my database. Help!"
I know that it should be possible to attach databases that have not been
explicitly detached, but if I wanted to make sure that I could recover
(attach) my databases I would issue a detach statement first.
Keith
"MikeF" <mrf@.sent.com> wrote in message
news:%23R1$2CufEHA.904@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Keith Kratochvil wrote:
that[vbcol=seagreen]
availability[vbcol=seagreen]
Information[vbcol=seagreen]
program
> Thanks Keith. What do you think of Wayne's point that if the service
> MSSQL$SQL2000 is stopped using SQL Server Service Manager, then the db
> files ARE in exactly the same state as if they were detached using
> sp_detach_db ?
> I am not doing a backup routine (or at least, I am the recommended way
> using sp_detach_db) but I am working with a peculiar configuration with
> some odd restraints, and and I need to know if using SQL Server Service
> Manager to stop the service is actually the same as using sp_detach_db,
> like Wayne suggests.
> Many thanks for your time.
> -- Mike
>
|||Practically speaking shutting down the database (in whatever way) and using
sp_detach_db are NOT the same. Theoretically they more or less should be the
same, but attaching databases that haven't been explicitly detached has been
a hit-and-miss experience for a lot of users.
Jacco Schalkwijk
SQL Server MVP
"MikeF" <mrf@.sent.com> wrote in message
news:%23nPAyBufEHA.904@.TK2MSFTNGP09.phx.gbl...
> Jacco Schalkwijk wrote:
>
> Thanks Jacco. What do you think of Wayne's point that if the service
> MSSQL$SQL2000 is stopped using SQL Server Service Manager, then the db
> files ARE in exactly the same state as if they were detached using
> sp_detach_db ?
> I understand that using sp_detach_db is the proper way to do it, and we
> are doing it that way, but this is a peculiar configuration I am trying to
> work with and I need to know if using SQL Server Service Manager to stop
> the service is actually the same as using sp_detach_db, like Wayne
> suggests.
> Many thanks for your time.
> -- Mike
>
|||IMO, it doesn't matter what anyone of us say (no disrespect to anyone here, I'm just making a point). What
matter is what the documentation say. And the documentation say that you are guaranteed to be able to attach a
db only if you detached it first. (Look up BOL for exact wording.)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"MikeF" <mrf@.sent.com> wrote in message news:%23nPAyBufEHA.904@.TK2MSFTNGP09.phx.gbl...
> Jacco Schalkwijk wrote:
>
> Thanks Jacco. What do you think of Wayne's point that if the service
> MSSQL$SQL2000 is stopped using SQL Server Service Manager, then the db
> files ARE in exactly the same state as if they were detached using
> sp_detach_db ?
> I understand that using sp_detach_db is the proper way to do it, and we
> are doing it that way, but this is a peculiar configuration I am trying
> to work with and I need to know if using SQL Server Service Manager to
> stop the service is actually the same as using sp_detach_db, like Wayne
> suggests.
> Many thanks for your time.
> -- Mike
>

detaching db and stopping services

Is the state of SQL Server 2000 files the same:
1) when you detach them (run sp_detach-db); and
2) when you stop all SQL Server services, particularly MSSQL$SQL2000 ?
In other words, when you stop the service, are the db files utomatically
put in the detached state, as if you had run sp_detach-db on them ?
If not, what is the difference between the files when the service is
stopped, and when they are in the detached state ?
Thanks
-- MikeNo, they are not the same.
sp_detach_db ensures that your files can be attached.
Simply grabbing the files from a stopped instance will not guarantee that
you can recover them.
Are you trying to implement a backup routine? Do you want 100% availability
during the backups? Look into the Transact-SQL BACKUP command. Information
and examples can be found within Books Online (within the SQL Server program
group).
Keith
"MikeF" <mrf@.sent.com> wrote in message
news:uSyKDRsfEHA.1356@.TK2MSFTNGP09.phx.gbl...
> Is the state of SQL Server 2000 files the same:
> 1) when you detach them (run sp_detach-db); and
> 2) when you stop all SQL Server services, particularly MSSQL$SQL2000 ?
> In other words, when you stop the service, are the db files utomatically
> put in the detached state, as if you had run sp_detach-db on them ?
> If not, what is the difference between the files when the service is
> stopped, and when they are in the detached state ?
> Thanks
> -- Mike
>|||I do not think the state MUST be the same... When you detach a file, there
can be no in-process transactions.
I believe that stopping the service is more 'rude'... I don't think it waits
for transactions to complete. Stopping the service through SEM or the
Service manager does wait, stopping through control panel services or net
stop does not...
Even if the state were the same, remember that detach removes all references
from master as well..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"MikeF" <mrf@.sent.com> wrote in message
news:uSyKDRsfEHA.1356@.TK2MSFTNGP09.phx.gbl...
> Is the state of SQL Server 2000 files the same:
> 1) when you detach them (run sp_detach-db); and
> 2) when you stop all SQL Server services, particularly MSSQL$SQL2000 ?
> In other words, when you stop the service, are the db files utomatically
> put in the detached state, as if you had run sp_detach-db on them ?
> If not, what is the difference between the files when the service is
> stopped, and when they are in the detached state ?
> Thanks
> -- Mike
>|||When you detach a database, a checkpoint happens in the database. That means
that all changed that have been made to datapages but that haven't been
written to the data file yet, are written to disk. All these changes are of
course already in the transaction log.
Shutting down SQL Services should perform a check point as well, but IIRC
the documentation in Books Online (see SHUTDOWN) is not complete at this
point. If the server or service fails, you will in most cases not have a
properly check pointed data file, and you will need the transaction log to
recover your database.
It is definitely recommended that if you want to attach a database to
another server, that you use sp_detachdb.
Jacco Schalkwijk
SQL Server MVP
"MikeF" <mrf@.sent.com> wrote in message
news:uSyKDRsfEHA.1356@.TK2MSFTNGP09.phx.gbl...
> Is the state of SQL Server 2000 files the same:
> 1) when you detach them (run sp_detach-db); and
> 2) when you stop all SQL Server services, particularly MSSQL$SQL2000 ?
> In other words, when you stop the service, are the db files utomatically
> put in the detached state, as if you had run sp_detach-db on them ?
> If not, what is the difference between the files when the service is
> stopped, and when they are in the detached state ?
> Thanks
> -- Mike
>|||Wayne Snyder wrote:

> I do not think the state MUST be the same... When you detach a file, the
re
> can be no in-process transactions.
> I believe that stopping the service is more 'rude'... I don't think it wai
ts
> for transactions to complete. Stopping the service through SEM or the
> Service manager does wait, stopping through control panel services or net
> stop does not...
> Even if the state were the same, remember that detach removes all referenc
es
> from master as well..
>
Thanks Wayne, that is very interesting.
Are you saying that IF the service MSSQL$SQL2000 is stopped using SQL
Server Service Manager, then the db files ARE in exactly the same state
as if they were detached using sp_detach_db '
I would appreciate your confirming this.
-- Mike|||Jacco Schalkwijk wrote:

> When you detach a database, a checkpoint happens in the database. That mea
ns
> that all changed that have been made to datapages but that haven't been
> written to the data file yet, are written to disk. All these changes are o
f
> course already in the transaction log.
> Shutting down SQL Services should perform a check point as well, but IIRC
> the documentation in Books Online (see SHUTDOWN) is not complete at this
> point. If the server or service fails, you will in most cases not have a
> properly check pointed data file, and you will need the transaction log to
> recover your database.
> It is definitely recommended that if you want to attach a database to
> another server, that you use sp_detachdb.
>
Thanks Jacco. What do you think of Wayne's point that if the service
MSSQL$SQL2000 is stopped using SQL Server Service Manager, then the db
files ARE in exactly the same state as if they were detached using
sp_detach_db '
I understand that using sp_detach_db is the proper way to do it, and we
are doing it that way, but this is a peculiar configuration I am trying
to work with and I need to know if using SQL Server Service Manager to
stop the service is actually the same as using sp_detach_db, like Wayne
suggests.
Many thanks for your time.
-- Mike|||Keith Kratochvil wrote:

> No, they are not the same.
> sp_detach_db ensures that your files can be attached.
> Simply grabbing the files from a stopped instance will not guarantee that
> you can recover them.
> Are you trying to implement a backup routine? Do you want 100% availabili
ty
> during the backups? Look into the Transact-SQL BACKUP command. Informati
on
> and examples can be found within Books Online (within the SQL Server progr
am
> group).
>
Thanks Keith. What do you think of Wayne's point that if the service
MSSQL$SQL2000 is stopped using SQL Server Service Manager, then the db
files ARE in exactly the same state as if they were detached using
sp_detach_db '
I am not doing a backup routine (or at least, I am the recommended way
using sp_detach_db) but I am working with a peculiar configuration with
some odd restraints, and and I need to know if using SQL Server Service
Manager to stop the service is actually the same as using sp_detach_db,
like Wayne suggests.
Many thanks for your time.
-- Mike|||I believe the safest option is to issue sp_detach_db.
I have read a few posts within the newsgroups along the lines of "I did not
detach my database (I copied the mdf and ldf files when the services were
stopped) and now I cannot attach my database. Help!"
I know that it should be possible to attach databases that have not been
explicitly detached, but if I wanted to make sure that I could recover
(attach) my databases I would issue a detach statement first.
Keith
"MikeF" <mrf@.sent.com> wrote in message
news:%23R1$2CufEHA.904@.TK2MSFTNGP09.phx.gbl...
> Keith Kratochvil wrote:
>
that[vbcol=seagreen]
availability[vbcol=seagreen]
Information[vbcol=seagreen]
program[vbcol=seagreen]
> Thanks Keith. What do you think of Wayne's point that if the service
> MSSQL$SQL2000 is stopped using SQL Server Service Manager, then the db
> files ARE in exactly the same state as if they were detached using
> sp_detach_db '
> I am not doing a backup routine (or at least, I am the recommended way
> using sp_detach_db) but I am working with a peculiar configuration with
> some odd restraints, and and I need to know if using SQL Server Service
> Manager to stop the service is actually the same as using sp_detach_db,
> like Wayne suggests.
> Many thanks for your time.
> -- Mike
>|||Practically speaking shutting down the database (in whatever way) and using
sp_detach_db are NOT the same. Theoretically they more or less should be the
same, but attaching databases that haven't been explicitly detached has been
a hit-and-miss experience for a lot of users.
Jacco Schalkwijk
SQL Server MVP
"MikeF" <mrf@.sent.com> wrote in message
news:%23nPAyBufEHA.904@.TK2MSFTNGP09.phx.gbl...
> Jacco Schalkwijk wrote:
>
> Thanks Jacco. What do you think of Wayne's point that if the service
> MSSQL$SQL2000 is stopped using SQL Server Service Manager, then the db
> files ARE in exactly the same state as if they were detached using
> sp_detach_db '
> I understand that using sp_detach_db is the proper way to do it, and we
> are doing it that way, but this is a peculiar configuration I am trying to
> work with and I need to know if using SQL Server Service Manager to stop
> the service is actually the same as using sp_detach_db, like Wayne
> suggests.
> Many thanks for your time.
> -- Mike
>|||IMO, it doesn't matter what anyone of us say (no disrespect to anyone here,
I'm just making a point). What
matter is what the documentation say. And the documentation say that you are
guaranteed to be able to attach a
db only if you detached it first. (Look up BOL for exact wording.)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"MikeF" <mrf@.sent.com> wrote in message news:%23nPAyBufEHA.904@.TK2MSFTNGP09.phx.gbl...[vbcol
=seagreen]
> Jacco Schalkwijk wrote:
>
> Thanks Jacco. What do you think of Wayne's point that if the service
> MSSQL$SQL2000 is stopped using SQL Server Service Manager, then the db
> files ARE in exactly the same state as if they were detached using
> sp_detach_db '
> I understand that using sp_detach_db is the proper way to do it, and we
> are doing it that way, but this is a peculiar configuration I am trying
> to work with and I need to know if using SQL Server Service Manager to
> stop the service is actually the same as using sp_detach_db, like Wayne
> suggests.
> Many thanks for your time.
> -- Mike
>[/vbcol]

Wednesday, March 7, 2012

Designing SQL2K RS reports using VS 2005 Express

Anyone:
Is it possible to install the SQL Server 2000 Reporting Services design
component for Visual Studio 2003 into Visual Studio 2005 Express to design
reports that will be deployed to Reporting Services running on SQL Server
2000? Thank you in advance for your time.No, this is not possible. RS 2000 Report Designer requires VS 2003.
--
Albert Yen
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Nikolai Sonin" <NikolaiSonin@.discussions.microsoft.com> wrote in message
news:B5728FFD-6C1A-4C59-A3A7-C415C4436DFD@.microsoft.com...
> Anyone:
> Is it possible to install the SQL Server 2000 Reporting Services
> design
> component for Visual Studio 2003 into Visual Studio 2005 Express to design
> reports that will be deployed to Reporting Services running on SQL Server
> 2000? Thank you in advance for your time.|||I have an MSDN subscription and just installed both SQL Server 2005 Beta
tools and Visual Studio 2005 Beta 2 - I'm assuming:
1.) That SQL Server 2005 has a Report Designer
2.) That the SQL Server 2005 Report Designer will plug into Visual
Studio 2005
3.) That the SQL Server 2005 Report Designer inside of Visual Studio
2005 will work on SQL Server 2000 Databases
4.) That there is some way of importing reports designed in SQL Server
2000 Report Designer into the SQL Server 2005 Report Designer.
Could you tell me which of these are true?
"Albert Yen [MSFT]" wrote:
> No, this is not possible. RS 2000 Report Designer requires VS 2003.
> --
> Albert Yen
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Nikolai Sonin" <NikolaiSonin@.discussions.microsoft.com> wrote in message
> news:B5728FFD-6C1A-4C59-A3A7-C415C4436DFD@.microsoft.com...
> > Anyone:
> > Is it possible to install the SQL Server 2000 Reporting Services
> > design
> > component for Visual Studio 2003 into Visual Studio 2005 Express to design
> > reports that will be deployed to Reporting Services running on SQL Server
> > 2000? Thank you in advance for your time.
>
>

Designing reports without Visual Studio .NET 2003

I'm really interested in Reporting Services, but I can't seem to find any
documentation on how to write reports and utilize it without Visual Studio
.NET 2003. Is there any way to do that?
--
Chris Shipley
HSI System Administrator
CAFCA, Inc.
Hartford, CT
http://www.cafca.org
chriss@.crtct.orgHere is some information.
http://www.ReportingServicesFAQ.com/ow.asp?ReportingWithoutVisualStudio
Chris Shipley wrote:
> I'm really interested in Reporting Services, but I can't seem to find any
> documentation on how to write reports and utilize it without Visual Studio
> .NET 2003. Is there any way to do that?
> --
> Chris Shipley
> HSI System Administrator
> CAFCA, Inc.
> Hartford, CT
> http://www.cafca.org
> chriss@.crtct.org
>|||Microsoft also have a sample app for creating RDL.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsamples/htm/rss_tutorials_v1_02ua.asp
Combine this with the sample code for accessing the reporting services web
servic
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsamples/htm/rss_sampleapps_v1_002q.asp
With these two set of examples you can write a program to create rdl,
publish it to the web service and view it within an application. The
complexity will be trying to generate more complex reports as the sample
provided on msdn only generates simple rdl. Easiest way I found to start
writing code to generate more complex rdl was to use the sample RDL program
to generate a report, load this report in vs.net and make some changes then
compare the modified rdl with your original and retro-fit the changes in to
the code. With a lot of time (and hair pulling) you can ultimately generate
fairly complex RDL.
Hope this helps,
Richard
"Jerry" wrote:
> Here is some information.
> http://www.ReportingServicesFAQ.com/ow.asp?ReportingWithoutVisualStudio
>
> Chris Shipley wrote:
> > I'm really interested in Reporting Services, but I can't seem to find any
> > documentation on how to write reports and utilize it without Visual Studio
> > .NET 2003. Is there any way to do that?
> >
> > --
> > Chris Shipley
> > HSI System Administrator
> > CAFCA, Inc.
> > Hartford, CT
> > http://www.cafca.org
> > chriss@.crtct.org
> >
> >
>|||Hey, thanks for that! See, I have this huge database (1.3+ gb) with over
500 users, but there's no good reporting tool for them. I'm looking for a
way to give them a visual report writing tool, perhaps on the web secured
through SSL. But if they have to use VS.NET to create a report, its not
very cost effective.
Anyone out there know of any resources I can look at to achieve my
objective? I'd utilize SQL Reporting Services, but I don't have VS.NET
either. I suppose if I had to, I could learn RDL, but that doesn't seem an
effective method for users. Maybe someone out there is already writing a
VS.NET program for that purpose! :)
--
Chris Shipley
HSI System Administrator
CAFCA
Hartford, CT
Ph: 860-560-5455
http://www.cafca.org/helpdesk
chriss@.crtct.org
"Jerry" <JerryNY32513@.hotmail.com> wrote in message
news:uvPSGLkBFHA.2568@.TK2MSFTNGP11.phx.gbl...
> Here is some information.
> http://www.ReportingServicesFAQ.com/ow.asp?ReportingWithoutVisualStudio
>
> Chris Shipley wrote:
> > I'm really interested in Reporting Services, but I can't seem to find
any
> > documentation on how to write reports and utilize it without Visual
Studio
> > .NET 2003. Is there any way to do that?
> >
> > --
> > Chris Shipley
> > HSI System Administrator
> > CAFCA, Inc.
> > Hartford, CT
> > http://www.cafca.org
> > chriss@.crtct.org
> >
> >|||Several partners provide applications for RS 2000 that will allow the
creation of reports without using VS.NET. Some of them provide web-based
designers, some of them provide tools integrated e.g. into Office. You may
want to check:
http://www.microsoft.com/sql/reporting/partners/softwareapps.asp
If you can wait till RS 2005, it will provide an additional report design
tool called "Report Builder". It is a stand-alone application (independent
of the VS.NET report designer) and is focused on end-users. It allows them
to easily create reports without needing to design queries or writing
expressions. Report Builder was briefly shown as one of the new features in
RS 2005 in this webcast:
http://msevents.microsoft.com/cui/eventdetail.aspx?eventid=1032263305&culture=en-us
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chris Shipley" <chriss@.crtct.org> wrote in message
news:%23HOyS7sBFHA.1408@.TK2MSFTNGP10.phx.gbl...
> Hey, thanks for that! See, I have this huge database (1.3+ gb) with over
> 500 users, but there's no good reporting tool for them. I'm looking for a
> way to give them a visual report writing tool, perhaps on the web secured
> through SSL. But if they have to use VS.NET to create a report, its not
> very cost effective.
> Anyone out there know of any resources I can look at to achieve my
> objective? I'd utilize SQL Reporting Services, but I don't have VS.NET
> either. I suppose if I had to, I could learn RDL, but that doesn't seem
an
> effective method for users. Maybe someone out there is already writing a
> VS.NET program for that purpose! :)
> --
> Chris Shipley
> HSI System Administrator
> CAFCA
> Hartford, CT
> Ph: 860-560-5455
> http://www.cafca.org/helpdesk
> chriss@.crtct.org
> "Jerry" <JerryNY32513@.hotmail.com> wrote in message
> news:uvPSGLkBFHA.2568@.TK2MSFTNGP11.phx.gbl...
> > Here is some information.
> >
> > http://www.ReportingServicesFAQ.com/ow.asp?ReportingWithoutVisualStudio
> >
> >
> >
> > Chris Shipley wrote:
> > > I'm really interested in Reporting Services, but I can't seem to find
> any
> > > documentation on how to write reports and utilize it without Visual
> Studio
> > > .NET 2003. Is there any way to do that?
> > >
> > > --
> > > Chris Shipley
> > > HSI System Administrator
> > > CAFCA, Inc.
> > > Hartford, CT
> > > http://www.cafca.org
> > > chriss@.crtct.org
> > >
> > >
>|||Thanks Robert.
Is there a beta version of RS 2005?
--
Chris Shipley
HSI System Administrator
CAFCA
Hartford, CT
Ph: 860-560-5455
http://www.cafca.org
chriss@.crtct.org
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:uN%23$chyBFHA.1452@.TK2MSFTNGP11.phx.gbl...
> Several partners provide applications for RS 2000 that will allow the
> creation of reports without using VS.NET. Some of them provide web-based
> designers, some of them provide tools integrated e.g. into Office. You may
> want to check:
> http://www.microsoft.com/sql/reporting/partners/softwareapps.asp
> If you can wait till RS 2005, it will provide an additional report design
> tool called "Report Builder". It is a stand-alone application (independent
> of the VS.NET report designer) and is focused on end-users. It allows them
> to easily create reports without needing to design queries or writing
> expressions. Report Builder was briefly shown as one of the new features
in
> RS 2005 in this webcast:
>
http://msevents.microsoft.com/cui/eventdetail.aspx?eventid=1032263305&culture=en-us
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Chris Shipley" <chriss@.crtct.org> wrote in message
> news:%23HOyS7sBFHA.1408@.TK2MSFTNGP10.phx.gbl...
> > Hey, thanks for that! See, I have this huge database (1.3+ gb) with
over
> > 500 users, but there's no good reporting tool for them. I'm looking for
a
> > way to give them a visual report writing tool, perhaps on the web
secured
> > through SSL. But if they have to use VS.NET to create a report, its not
> > very cost effective.
> >
> > Anyone out there know of any resources I can look at to achieve my
> > objective? I'd utilize SQL Reporting Services, but I don't have VS.NET
> > either. I suppose if I had to, I could learn RDL, but that doesn't seem
> an
> > effective method for users. Maybe someone out there is already writing
a
> > VS.NET program for that purpose! :)
> >
> > --
> > Chris Shipley
> > HSI System Administrator
> > CAFCA
> > Hartford, CT
> > Ph: 860-560-5455
> > http://www.cafca.org/helpdesk
> > chriss@.crtct.org
> >
> > "Jerry" <JerryNY32513@.hotmail.com> wrote in message
> > news:uvPSGLkBFHA.2568@.TK2MSFTNGP11.phx.gbl...
> > > Here is some information.
> > >
> > >
http://www.ReportingServicesFAQ.com/ow.asp?ReportingWithoutVisualStudio
> > >
> > >
> > >
> > > Chris Shipley wrote:
> > > > I'm really interested in Reporting Services, but I can't seem to
find
> > any
> > > > documentation on how to write reports and utilize it without Visual
> > Studio
> > > > .NET 2003. Is there any way to do that?
> > > >
> > > > --
> > > > Chris Shipley
> > > > HSI System Administrator
> > > > CAFCA, Inc.
> > > > Hartford, CT
> > > > http://www.cafca.org
> > > > chriss@.crtct.org
> > > >
> > > >
> >
> >
>|||Yes, there is a Beta program for SQL Server 2005 (which includes RS 2005).
More information can be found here:
http://www.microsoft.com/sql/2005/default.asp
If you are a MSDN subscriber you should also have access to SQL Server CTPs
(Community Technology Previews). Report Builder is a completely new product
and not yet available in the December CTP, but it will be included in SQL
Server 2005 Beta 3 and very likely already in one of the upcoming CTPs.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chris Shipley" <chriss@.crtct.org> wrote in message
news:eApnSOMCFHA.328@.tk2msftngp13.phx.gbl...
> Thanks Robert.
> Is there a beta version of RS 2005?
> --
> Chris Shipley
> HSI System Administrator
> CAFCA
> Hartford, CT
> Ph: 860-560-5455
> http://www.cafca.org
> chriss@.crtct.org
> "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
> news:uN%23$chyBFHA.1452@.TK2MSFTNGP11.phx.gbl...
> > Several partners provide applications for RS 2000 that will allow the
> > creation of reports without using VS.NET. Some of them provide web-based
> > designers, some of them provide tools integrated e.g. into Office. You
may
> > want to check:
> > http://www.microsoft.com/sql/reporting/partners/softwareapps.asp
> >
> > If you can wait till RS 2005, it will provide an additional report
design
> > tool called "Report Builder". It is a stand-alone application
(independent
> > of the VS.NET report designer) and is focused on end-users. It allows
them
> > to easily create reports without needing to design queries or writing
> > expressions. Report Builder was briefly shown as one of the new features
> in
> > RS 2005 in this webcast:
> >
>
http://msevents.microsoft.com/cui/eventdetail.aspx?eventid=1032263305&culture=en-us
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "Chris Shipley" <chriss@.crtct.org> wrote in message
> > news:%23HOyS7sBFHA.1408@.TK2MSFTNGP10.phx.gbl...
> > > Hey, thanks for that! See, I have this huge database (1.3+ gb) with
> over
> > > 500 users, but there's no good reporting tool for them. I'm looking
for
> a
> > > way to give them a visual report writing tool, perhaps on the web
> secured
> > > through SSL. But if they have to use VS.NET to create a report, its
not
> > > very cost effective.
> > >
> > > Anyone out there know of any resources I can look at to achieve my
> > > objective? I'd utilize SQL Reporting Services, but I don't have
VS.NET
> > > either. I suppose if I had to, I could learn RDL, but that doesn't
seem
> > an
> > > effective method for users. Maybe someone out there is already
writing
> a
> > > VS.NET program for that purpose! :)
> > >
> > > --
> > > Chris Shipley
> > > HSI System Administrator
> > > CAFCA
> > > Hartford, CT
> > > Ph: 860-560-5455
> > > http://www.cafca.org/helpdesk
> > > chriss@.crtct.org
> > >
> > > "Jerry" <JerryNY32513@.hotmail.com> wrote in message
> > > news:uvPSGLkBFHA.2568@.TK2MSFTNGP11.phx.gbl...
> > > > Here is some information.
> > > >
> > > >
> http://www.ReportingServicesFAQ.com/ow.asp?ReportingWithoutVisualStudio
> > > >
> > > >
> > > >
> > > > Chris Shipley wrote:
> > > > > I'm really interested in Reporting Services, but I can't seem to
> find
> > > any
> > > > > documentation on how to write reports and utilize it without
Visual
> > > Studio
> > > > > .NET 2003. Is there any way to do that?
> > > > >
> > > > > --
> > > > > Chris Shipley
> > > > > HSI System Administrator
> > > > > CAFCA, Inc.
> > > > > Hartford, CT
> > > > > http://www.cafca.org
> > > > > chriss@.crtct.org
> > > > >
> > > > >
> > >
> > >
> >
> >
>

Designing reports with Reproting Services

I'm no graphic designer but I am really struggling with making a decent looking report.

Does anyone have any ideas or tips when working with reporting services?

Hi,

I'm no expert either, but what works for me is designing a report template which has the basics, and use that as a starting place for all subsequent reports. The template contains a page footer which contains the date the report was run, the name of our office and "page # out of total pages".

Starting with this generic template I add a page header which contains the report name and any selection criteria which is input by the user at run-time. On to content: I output data in the order specified by users and use bold for all headings to increase readability. Where appropriate the Reporting Services' "groupby" feature also increases clarity by allowing you to suppress duplicate values on the print-out.

Hope this helps!

Saturday, February 25, 2012

Designing Reports for SQL Reporting Services 2000

My customer has SQL Reporting Services on a server with SQL 2000 Standard Edition. The customer wants to develop his own Reporting Services reports. We have been recommending Visual Basic.NET Standard 2003 for this purpose in that it costs less than $100 (usually). However, with the advent of Visual Studio 2005, the VB.NET 2003 is becoming difficult or impossible to obtain. One option is Visual C#.NET Standard 2003 - I assume it will work - does anyone know for sure?

More importantly, when Visual C#.NET 2003 becomes unvailable, what options are left for developing RS 2000 reports?

Thanks for any suggestions.

Mark

>More importantly, when Visual C#.NET 2003 becomes unvailable, what options are left for developing RS 2000 reports?

None from Microsoft. There are third-party solutions, e.g. Cizer.

|||

You could also write a small tool that performs a RDL structure "downgrade" conversion (see e.g. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=988366&SiteID=1). However note that RS 2000 doesn't support a number of RS 2005 features (e.g. multi value parameters).

-- Robert

designing reports

Hi - we are just putting a proposal/costs together to implement reporting
services.
Might seem daft (!), I know i need the report designer and it works with the
visual studio .net 2003, but does that mean we need to buy visual studio .net
2003 (std/dev/enterprise?) and the designer comes free? Or vice versa? Or
both!
Thanks PaulThe designer comes free with SQL Server (you need a license for SQL Server
anywhere you have the server part of RS installed). But, the designer needs
some version (any version) of VS to install into. If you don't have VS 2003
then the cheapest thing to do is to buy VB.Net ($100).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:ED6BE78D-8085-4A3A-8F01-6BD0408734D9@.microsoft.com...
> Hi - we are just putting a proposal/costs together to implement reporting
> services.
> Might seem daft (!), I know i need the report designer and it works with
the
> visual studio .net 2003, but does that mean we need to buy visual studio
.net
> 2003 (std/dev/enterprise?) and the designer comes free? Or vice versa? Or
> both!
> Thanks Paul|||Thanks for the info Bruce! We have SQL server but are hoping to migrate from
Actuate...
"Bruce L-C [MVP]" wrote:
> The designer comes free with SQL Server (you need a license for SQL Server
> anywhere you have the server part of RS installed). But, the designer needs
> some version (any version) of VS to install into. If you don't have VS 2003
> then the cheapest thing to do is to buy VB.Net ($100).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:ED6BE78D-8085-4A3A-8F01-6BD0408734D9@.microsoft.com...
> > Hi - we are just putting a proposal/costs together to implement reporting
> > services.
> >
> > Might seem daft (!), I know i need the report designer and it works with
> the
> > visual studio .net 2003, but does that mean we need to buy visual studio
> ..net
> > 2003 (std/dev/enterprise?) and the designer comes free? Or vice versa? Or
> > both!
> >
> > Thanks Paul
>
>|||Hi Paul,
We too are evaluating products to migrate from Actuate. I can share our
findings if you're interested.
Bill
"Paul" wrote:
> Thanks for the info Bruce! We have SQL server but are hoping to migrate from
> Actuate...
> "Bruce L-C [MVP]" wrote:
> > The designer comes free with SQL Server (you need a license for SQL Server
> > anywhere you have the server part of RS installed). But, the designer needs
> > some version (any version) of VS to install into. If you don't have VS 2003
> > then the cheapest thing to do is to buy VB.Net ($100).
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Paul" <Paul@.discussions.microsoft.com> wrote in message
> > news:ED6BE78D-8085-4A3A-8F01-6BD0408734D9@.microsoft.com...
> > > Hi - we are just putting a proposal/costs together to implement reporting
> > > services.
> > >
> > > Might seem daft (!), I know i need the report designer and it works with
> > the
> > > visual studio .net 2003, but does that mean we need to buy visual studio
> > ..net
> > > 2003 (std/dev/enterprise?) and the designer comes free? Or vice versa? Or
> > > both!
> > >
> > > Thanks Paul
> >
> >
> >|||Hi Paul,
I have a lot of experience with Actuate (8 years) and am currently getting
up to speed on Reporting Services.
Let me know if you'd like to exchange information/experiences on migrating
from Actuate to Reporting Services.
-- Chris
--
Chris, SSSI
"Paul" wrote:
> Thanks for the info Bruce! We have SQL server but are hoping to migrate from
> Actuate...
> "Bruce L-C [MVP]" wrote:
> > The designer comes free with SQL Server (you need a license for SQL Server
> > anywhere you have the server part of RS installed). But, the designer needs
> > some version (any version) of VS to install into. If you don't have VS 2003
> > then the cheapest thing to do is to buy VB.Net ($100).
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Paul" <Paul@.discussions.microsoft.com> wrote in message
> > news:ED6BE78D-8085-4A3A-8F01-6BD0408734D9@.microsoft.com...
> > > Hi - we are just putting a proposal/costs together to implement reporting
> > > services.
> > >
> > > Might seem daft (!), I know i need the report designer and it works with
> > the
> > > visual studio .net 2003, but does that mean we need to buy visual studio
> > ..net
> > > 2003 (std/dev/enterprise?) and the designer comes free? Or vice versa? Or
> > > both!
> > >
> > > Thanks Paul
> >
> >
> >|||Hi Bill,
I have a lot of experience with Actuate (8 years) and am currently getting
up to speed on Reporting Services.
Let me know if you'd like to exchange information/experiences on migrating
from Actuate to Reporting Services.
-- Chris
Chris, SSSI
"Bill" wrote:
> Hi Paul,
> We too are evaluating products to migrate from Actuate. I can share our
> findings if you're interested.
> Bill
> "Paul" wrote:
> > Thanks for the info Bruce! We have SQL server but are hoping to migrate from
> > Actuate...
> >
> > "Bruce L-C [MVP]" wrote:
> >
> > > The designer comes free with SQL Server (you need a license for SQL Server
> > > anywhere you have the server part of RS installed). But, the designer needs
> > > some version (any version) of VS to install into. If you don't have VS 2003
> > > then the cheapest thing to do is to buy VB.Net ($100).
> > >
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
> > > news:ED6BE78D-8085-4A3A-8F01-6BD0408734D9@.microsoft.com...
> > > > Hi - we are just putting a proposal/costs together to implement reporting
> > > > services.
> > > >
> > > > Might seem daft (!), I know i need the report designer and it works with
> > > the
> > > > visual studio .net 2003, but does that mean we need to buy visual studio
> > > ..net
> > > > 2003 (std/dev/enterprise?) and the designer comes free? Or vice versa? Or
> > > > both!
> > > >
> > > > Thanks Paul
> > >
> > >
> > >

Designing Report in VS.NET2003 - studio is crashing

I am using reporting services 2000 already for 2 years. This problem is occurring on 2-3 reports, I can't say exactly what is the reason.

How I use the report designer is pretty simple and consistent. Report data is usualy produced by calling a stored procedure (on SLQ server 2000), I have a few parameters. Some of Paramaters are dates with a default values calculated to give yesterday's date or today - 7 days. And that is the only code in the report itselft. As soon as I click on Yes/No paramater, that doesn't have default, and is int in proc and report, then complete Visual Studio Environment starts flashing, making bip-bip noise, and is blocked, no access and reponse. I can't close it for a while, I can't bring up task manager, and in general this crash is very much resource intensive, Outlook is freezing, can't open IE, new spreadsheet. I am working on windows Xp platform. Eventually I would manage to close VS thru task manager.

As soon as this report is uploaded to Report Manager, the place where all the reports are available to users, on different server, the same report works fine.

Has anyone experienced this and what would be the reason.

Thanks in advance,
Elizabeta R

did you get out of memory exception.. check ur database may be it contains huge data..

run the query in sql server..

Designer changing report element sizes during a save

This is a repost using MSDN Subscription
Using SQL Server Reporting Services Designer Version 9.00.1399.00
I'm having trouble with a three column report with a page header the width
of the page. The designer is changing the width of elements when it is
saved. As long as you view the report in the designer, the report renders as
you would expect, but when it gets saved, some of the report elements get
changed.
Try this:
New empty Report Server Project
Add new empty report (Add -> New Item -> Select Report)
No datasource
Enable page header
Add a text box (textbox1) to page header. Make it begin at the left
margin/top margin and be almost the width of the page (6in).
Set the height of the page header to the height of the textbox1.
Insert five or six words in textbox1.
Make the report a 3 column report.
Reset the page header width to be 6.5in (1in right/left margins on 8.5in
paper) using the resizer in the page header.
The column width should be 1.83333in (1.83333 * 3 = 5.49999 + [column
spacing] 0.5in + 0.5in = 6.49999in)
Add a text box (textbox2) to the body (in column 1). Make it begin at the
left margin/top margin and be almost the width of the column (1.625in).
Insert a few words in textbox2.
View the report. Appears to be fine.
Save, Close the report, Reopen the report.
The width of the page header is now 6in (was 6.5in), column width is now
1.66667in (was 1.83333in)
Why did the width of the page header change?
Make the width of the page header and textbox1, 6.5in.
Save, Close the report, Reopen the report.
The page header is 6.499999in wide, but textbox1 is the same width as one of
the columns in the body (1.83333in)
Why did the width of the page header and textbox1 change?
Make textbox1 6in wide again.
Make the report 6.5in wide.
Add a new textbox (textbox3) in the page header to the right of textbox1
(starts at 6in, 0.5in wide), same height as the first one.
Insert a few letters in textbox3.
Save, Close the report, Reopen the report.
The report is now 6in wide (instead of 6.5in), columns are 1.66667in wide.
Textbox3 that was just added to the page header cannot be seen. It is at
the right edge of the page header, and has a negative width. It can only be
found using dropdown in the properties window.
Why did textbox3 disappear/get a negative width?
Are these known bugs? Are there any work arounds?Hello,
From your desscription, I tried to reproduce the issue to no avail. To
understand the issue better, will you please send the report project or
report to me? You could remove "online" in my displayed email address. I
know the report will be changed after saving, and reopen, however, you
report shall make me understanding your problem more directly. thank you!
Also, since you did not install SQL 2005 sp1, you may want to install it to
test the sitaution.
If you have other related information, please also let's know. We look
forward to your reply.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Im having the same error!! I have 2 reports that have mutliple columns. When
I save the report, it will change the text boxes in the header to negative
values. I have not found a work around for this error. Anyone have any
suggestions/Have run into the same problem as well?
-Theresa
"AOTX San Antonio" wrote:
> This is a repost using MSDN Subscription
> Using SQL Server Reporting Services Designer Version 9.00.1399.00
> I'm having trouble with a three column report with a page header the width
> of the page. The designer is changing the width of elements when it is
> saved. As long as you view the report in the designer, the report renders as
> you would expect, but when it gets saved, some of the report elements get
> changed.
> Try this:
> New empty Report Server Project
> Add new empty report (Add -> New Item -> Select Report)
> No datasource
> Enable page header
> Add a text box (textbox1) to page header. Make it begin at the left
> margin/top margin and be almost the width of the page (6in).
> Set the height of the page header to the height of the textbox1.
> Insert five or six words in textbox1.
> Make the report a 3 column report.
> Reset the page header width to be 6.5in (1in right/left margins on 8.5in
> paper) using the resizer in the page header.
> The column width should be 1.83333in (1.83333 * 3 = 5.49999 + [column
> spacing] 0.5in + 0.5in = 6.49999in)
> Add a text box (textbox2) to the body (in column 1). Make it begin at the
> left margin/top margin and be almost the width of the column (1.625in).
> Insert a few words in textbox2.
> View the report. Appears to be fine.
> Save, Close the report, Reopen the report.
> The width of the page header is now 6in (was 6.5in), column width is now
> 1.66667in (was 1.83333in)
> Why did the width of the page header change?
> Make the width of the page header and textbox1, 6.5in.
> Save, Close the report, Reopen the report.
> The page header is 6.499999in wide, but textbox1 is the same width as one of
> the columns in the body (1.83333in)
> Why did the width of the page header and textbox1 change?
> Make textbox1 6in wide again.
> Make the report 6.5in wide.
> Add a new textbox (textbox3) in the page header to the right of textbox1
> (starts at 6in, 0.5in wide), same height as the first one.
> Insert a few letters in textbox3.
> Save, Close the report, Reopen the report.
> The report is now 6in wide (instead of 6.5in), columns are 1.66667in wide.
> Textbox3 that was just added to the page header cannot be seen. It is at
> the right edge of the page header, and has a negative width. It can only be
> found using dropdown in the properties window.
> Why did textbox3 disappear/get a negative width?
> Are these known bugs? Are there any work arounds?|||Hello Theresa
,
I have reproduced the issue on my side. It seems that when adding textbox
or change textbox, it does not actually perform an optimization of the
report according to the algorithm that used when saving a report. I found
if I change the textbox1 width to 6 to 6.5, this size is not actually saved
to rdl and the width number is not stored at all. At this time, textbox1
actually has the 6.5 when rendering since it is aligned to the body width
1.83333 automatically.
Please rest assured your feedback is taken seriously this issue has been
reported to the product team. Product team may evaluate the business impact
and decide to fix this or not. If there is any update, we will let you
know.
You may manually edit rdl and set textbox in pageheader to the value it
should be to work around the issue. In the meantime, I also encourage you
submit your feedback on this issue via the link below
http://lab.msdn.microsoft.com/productfeedback/default.aspx
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Hello Every One,
I came across this issue and found a good work around for this.
Whenever you have the textbox's right margin alligned with the right
margin of a rectangle in a Page Header, we see this behavour in a multi
column report.
Work around: We suggest to keep a minimal gap between the textbox right
edge and the container and make the container border as none. This
makes it retain the width attribute in the rdl file and we dont loose
its width after saving.
Best Regards,
Dipanjan Banik
SQL Developer Support
Peter Yang [MSFT] wrote:
> Hello Theresa
> ,
> I have reproduced the issue on my side. It seems that when adding textbox
> or change textbox, it does not actually perform an optimization of the
> report according to the algorithm that used when saving a report. I found
> if I change the textbox1 width to 6 to 6.5, this size is not actually saved
> to rdl and the width number is not stored at all. At this time, textbox1
> actually has the 6.5 when rendering since it is aligned to the body width
> 1.83333 automatically.
> Please rest assured your feedback is taken seriously this issue has been
> reported to the product team. Product team may evaluate the business impact
> and decide to fix this or not. If there is any update, we will let you
> know.
> You may manually edit rdl and set textbox in pageheader to the value it
> should be to work around the issue. In the meantime, I also encourage you
> submit your feedback on this issue via the link below
> http://lab.msdn.microsoft.com/productfeedback/default.aspx
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
>
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================

Friday, February 24, 2012

Design question related to Grouping

Hello,

I am using SQL 2005 Reporting Services to create a user status report. Each page of the report will contain information about 1 user.

On a single page, there are 4 different views of the data (pulling from different tables). Ideally, I would like to group the data (by user for each page, then by category for each of the 4 views on the page). I grouped by user, and the separate pages came out fine. But attempting to group by category, I found that the grouping applies to all the data...and I only want to group a subset of the data.

Is this possible? Will I need to nest select statements to make it happen? Is there a better way to approach this?

Go easy on me...I'm new to this.

Thanks,
Davidi think what your looking for is an outer join.
select * from table1 1
left outer join table2 2 on 1.column = 2.column

Sunday, February 19, 2012

Design Question (Analysis Services or Integration Services)

Hi,

I have a design issue and not sure, which approach to follow. Iam not sure, if I have to use analysis services or integration services. But we would like to use price trending also, so probably analysis services could be an option.

We have a table which stores the Customer Items information. For making it easier, I will talk about customer 1 and item 1as shown in the table below:

CustomerID

CustomerCategoryID

RegionId

ItemID

Price

1

1

2

1

10.00

2

1

2

1

12.00

3

1

2

1

14.00

4

2

1

1

18.00

5

2

1

1

16.00

6

3

3

1

15.00

7

4

3

1

12.00

Now the Customers can belong to a single Category and single Region

Customer Categories are 6 (1 -6) and Category 7 indicates all Categories.

Regions are 6 (1-6) and Region 7 indicates all Regions.

Now the reports run from the following particular cube (under the assumption that analysis services will be used to build the following cube)

CustomerID

CustomerCategoryID

RegionID

ItemID

Price

LowPrice

AveragePrice

1

1

2

1

10.00

10.00

12.00

2

1

2

1

12.00

10.00

12.00

3

1

2

1

14.00

10.00

12.00

1

2

1

1

10.00

16.00

17.00

1

3

3

1

10.00

15.00

15.00

1

4

3

1

10.00

12.00

12.00

1

7

1

1

10.00

16.00

17.00

1

7

2

1

10.00

10.00

12.00

1

7

3

1

10.00

12.00

13.50

1

7

4

1

10.00

NULL

NULL

1

7

5

1

10.00

NULL

NULL

1

7

6

1

10.00

NULL

NULL

1

1

7

1

10.00

10.00

12.00

1

2

7

1

10.00

16.00

17.00

1

3

7

1

10.00

15.00

15.00

1

4

7

1

10.00

12.00

12.00

1

5

7

1

10.00

NULL

NULL

1

6

7

1

10.00

NULL

NULL

As you can see in the above table for customer 1 and item 1, the lowest and average price is calculated for every available combination for categoryid and regionid(the ones in red indicate all regions and all categories). This may not be the best example, but hope it will help in understanding the issue here. What is the best approach to design this one ? If I have to design the cube can anybody help me in getting started. I have a basic understanding of MDX queries and trying to get a hang of it.

Thanks in advance for your help.

-Prash

Hi,

This is the general dimension model and analysis server 2005 can take care of this very easily.

If you have seperate tables for the Customers, CustomerCategory, Region and Items, then start of by modelling these as dimensions in analysis server. The fact table which you have shown would have foreign key references to the dimenison tables.

If you dont have dimension tables, you can create them. Customers and CustomersCategory can be attributes of the same dimension.

You will have Price, LowPrice and AveragePrice as your measures in the cube.

start of by creating a DataDource, then a DataSourceView. Once this is ready, click on new cube, then select your fact and dimension tables, select your measures and click finish.

The DSV (DataSourceView) would identify the fact and dimension tables. you would need to create primary keys and then create relationships from the fact table to the dimension tables. (for customers, region and item tables)

Hope this is what you were looking for

Regards

|||

Thanks for the reply. I did go ahead and build the cube with Price, LowPrice and AveragePrice as measure.

But Iam having problem with the query below for building the above mentioned report. Any help on this would be really appreciated.

Select

{

[Measures].[Price]

,[Measures].[MinimumPrice]

,[Measures].[AveragePrice]

} on Columns,

{

(

Filter

(

NONEMPTYCrossJoin

([DimRegions].[DimRegions].Children,

[DimCustomerCategories].[DimCustomerCategories].Children,

[DimItem].[ItemName].Children,

[DimCustomer].[CustomerName].Children

)

,[Measures].[Count No Of Rows] > 1

)

)

} on Rows

From [Cube1]