Running a trace

Hello,
If i need to execute a trace, would be better to execute on the server
machine, or in another client station?
Is that impacts the server performance (executing on the server) ?
Thanks
BrazilLeast impact is a server side trace (obviously executing on the server - but
also defined as a server side trace).
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Leandro Loureiro dos Santos" <leandro@.email.com> wrote in message
news:erYn8KTrDHA.964@.TK2MSFTNGP10.phx.gbl...
> Hello,
> If i need to execute a trace, would be better to execute on the server
> machine, or in another client station?
> Is that impacts the server performance (executing on the server) ?
> Thanks
> Brazil
>

running a script to create a database in MSDE

I've been able to create a CD where it installs MSDE 2000
sp3 on a user machine. I need to create a database on the
users machine, how do I incorporate the SQL script to
create the database? Do I call the script within the
setup.ini file? Any sample anywhere I can take a look at?
Thank you,
Randers
hi Randers,
Randers wrote:
> I've been able to create a CD where it installs MSDE 2000
> sp3 on a user machine. I need to create a database on the
> users machine, how do I incorporate the SQL script to
> create the database? Do I call the script within the
> setup.ini file? Any sample anywhere I can take a look at?
> Thank you,
> Randers
unfortunately is not that easy as you are trying to do... nothing from the
box...
you can perhaps run oSql.exe to execute your DDL sql script, or a home built
app of yours you pass the path to your script and execute it via an
ADO/Ado.Net connection, or have a look at
http://msdn.microsoft.com/msdnmag/is...baseinstaller/ for
a custom made database installation task...
another approach is relying on tools such as
http://www.red-gate.com/sql/sql_packager.htm
or you could redistribute a full backup of your database made on your
distribution environment and, via osql.exe and/or a home built app of yours
relying on ADO/Ado.Net connection restore it on the destination instance...
the very same path could be performed using the .Mdf and .Ldf detached
database files and reattache them using sp_attach_db system stored
procedures...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Running 2000 and 2005 Sql Server on 1 machine

I'm currently running SQL Server 2000 and 2005 on one machine at least I
think I am. I have Enterprise Manager and all the other components for 2000
on my laptop. I also loaded SQL Server 2005 with the .NET application from a
CD that I got from a Microsoft convention a long time ago. Basically, my
problem is when I click on the SQL SERVER 2005 Management Studio and run a
SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
database in 2005 and the mdf and ldf files are stored in the C:\...\Microsoft
SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory. What
am I doing wrong? Can 2000 and 2005 not run on the same box? This is
preventing me from changing the database compatiblity level to 90 because it
doesn't show up. Can anyone help? or suggest what I should do?
-- TCI guess you are connecting to your SQL Server 2000 Instance using SQL Server
Management Studio. That's why it tells you it's 2000 when you run SELECT
@.@.VERSION.
Go to SQL Server Configuration Manager and see if your SQL Server 2005
instance is running. And connect to that instance using SSMS. So, you'll be
able to create databases compatibility level 90.
--
Ekrem Ã?nsoy
"Terrance" <Terrance@.discussions.microsoft.com> wrote in message
news:8EC78FDB-283B-4391-A9D9-6BEB46BC7F9C@.microsoft.com...
> I'm currently running SQL Server 2000 and 2005 on one machine at least I
> think I am. I have Enterprise Manager and all the other components for
> 2000
> on my laptop. I also loaded SQL Server 2005 with the .NET application from
> a
> CD that I got from a Microsoft convention a long time ago. Basically, my
> problem is when I click on the SQL SERVER 2005 Management Studio and run a
> SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
> database in 2005 and the mdf and ldf files are stored in the
> C:\...\Microsoft
> SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory.
> What
> am I doing wrong? Can 2000 and 2005 not run on the same box? This is
> preventing me from changing the database compatiblity level to 90 because
> it
> doesn't show up. Can anyone help? or suggest what I should do?
> -- TC|||Hi Terrance
Along with the other posts!! The second instance (i.e. SQL 2005) would be
installed as a named instance, therefore you should know what instance has
been connected to.
I would not expect the SQL Server 2000 instance to know if the
...\MSSQL.1\BIN directory as the MSSQL.1 directory naming was introduced in
SQL 2005. Even for the SQL 2005 instance you would expect the database files
to be put into ...\MSSQL.1\MSSQL\DATA How are you creating this database?
For a
SQL 2005 instance you can right click the instance in SSMS and choose
properties then the Database Settings will tell you the default data and log
directories, a CREATE DATABASE in a query window without specifying any of
the file names will use these directories.
To see or set the databases compatability level use sp_dbcmptlevel
EXEC sp_dbcmptlevel AdventureWorks;
GO
EXEC sp_dbcmptlevel AdventureWorks, 90;
GO
It is best to change compatibility while no users are connected to the
database!
John
"Terrance" wrote:
> I'm currently running SQL Server 2000 and 2005 on one machine at least I
> think I am. I have Enterprise Manager and all the other components for 2000
> on my laptop. I also loaded SQL Server 2005 with the .NET application from a
> CD that I got from a Microsoft convention a long time ago. Basically, my
> problem is when I click on the SQL SERVER 2005 Management Studio and run a
> SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
> database in 2005 and the mdf and ldf files are stored in the C:\...\Microsoft
> SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory. What
> am I doing wrong? Can 2000 and 2005 not run on the same box? This is
> preventing me from changing the database compatiblity level to 90 because it
> doesn't show up. Can anyone help? or suggest what I should do?
> -- TC

Running 2000 and 2005 Sql Server on 1 machine

I'm currently running SQL Server 2000 and 2005 on one machine at least I
think I am. I have Enterprise Manager and all the other components for 2000
on my laptop. I also loaded SQL Server 2005 with the .NET application from a
CD that I got from a Microsoft convention a long time ago. Basically, my
problem is when I click on the SQL SERVER 2005 Management Studio and run a
SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
database in 2005 and the mdf and ldf files are stored in the C:\...\Microsoft
SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory. What
am I doing wrong? Can 2000 and 2005 not run on the same box? This is
preventing me from changing the database compatiblity level to 90 because it
doesn't show up. Can anyone help? or suggest what I should do?
-- TC
I guess you are connecting to your SQL Server 2000 Instance using SQL Server
Management Studio. That's why it tells you it's 2000 when you run SELECT
@.@.VERSION.
Go to SQL Server Configuration Manager and see if your SQL Server 2005
instance is running. And connect to that instance using SSMS. So, you'll be
able to create databases compatibility level 90.
Ekrem ?nsoy
"Terrance" <Terrance@.discussions.microsoft.com> wrote in message
news:8EC78FDB-283B-4391-A9D9-6BEB46BC7F9C@.microsoft.com...
> I'm currently running SQL Server 2000 and 2005 on one machine at least I
> think I am. I have Enterprise Manager and all the other components for
> 2000
> on my laptop. I also loaded SQL Server 2005 with the .NET application from
> a
> CD that I got from a Microsoft convention a long time ago. Basically, my
> problem is when I click on the SQL SERVER 2005 Management Studio and run a
> SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
> database in 2005 and the mdf and ldf files are stored in the
> C:\...\Microsoft
> SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory.
> What
> am I doing wrong? Can 2000 and 2005 not run on the same box? This is
> preventing me from changing the database compatiblity level to 90 because
> it
> doesn't show up. Can anyone help? or suggest what I should do?
> -- TC
|||Hi Terrance
Along with the other posts!! The second instance (i.e. SQL 2005) would be
installed as a named instance, therefore you should know what instance has
been connected to.
I would not expect the SQL Server 2000 instance to know if the
...\MSSQL.1\BIN directory as the MSSQL.1 directory naming was introduced in
SQL 2005. Even for the SQL 2005 instance you would expect the database files
to be put into ...\MSSQL.1\MSSQL\DATA How are you creating this database?
For a
SQL 2005 instance you can right click the instance in SSMS and choose
properties then the Database Settings will tell you the default data and log
directories, a CREATE DATABASE in a query window without specifying any of
the file names will use these directories.
To see or set the databases compatability level use sp_dbcmptlevel
EXEC sp_dbcmptlevel AdventureWorks;
GO
EXEC sp_dbcmptlevel AdventureWorks, 90;
GO
It is best to change compatibility while no users are connected to the
database!
John
"Terrance" wrote:

> I'm currently running SQL Server 2000 and 2005 on one machine at least I
> think I am. I have Enterprise Manager and all the other components for 2000
> on my laptop. I also loaded SQL Server 2005 with the .NET application from a
> CD that I got from a Microsoft convention a long time ago. Basically, my
> problem is when I click on the SQL SERVER 2005 Management Studio and run a
> SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
> database in 2005 and the mdf and ldf files are stored in the C:\...\Microsoft
> SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory. What
> am I doing wrong? Can 2000 and 2005 not run on the same box? This is
> preventing me from changing the database compatiblity level to 90 because it
> doesn't show up. Can anyone help? or suggest what I should do?
> -- TC

Running 2000 and 2005 Sql Server on 1 machine

I'm currently running SQL Server 2000 and 2005 on one machine at least I
think I am. I have Enterprise Manager and all the other components for 2000
on my laptop. I also loaded SQL Server 2005 with the .NET application from a
CD that I got from a Microsoft convention a long time ago. Basically, my
problem is when I click on the SQL SERVER 2005 Management Studio and run a
SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
database in 2005 and the mdf and ldf files are stored in the C:\...\Microsof
t
SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory. What
am I doing wrong? Can 2000 and 2005 not run on the same box? This is
preventing me from changing the database compatiblity level to 90 because it
doesn't show up. Can anyone help? or suggest what I should do?
-- TCI guess you are connecting to your SQL Server 2000 Instance using SQL Server
Management Studio. That's why it tells you it's 2000 when you run SELECT
@.@.VERSION.
Go to SQL Server Configuration Manager and see if your SQL Server 2005
instance is running. And connect to that instance using SSMS. So, you'll be
able to create databases compatibility level 90.
Ekrem ?nsoy
"Terrance" <Terrance@.discussions.microsoft.com> wrote in message
news:8EC78FDB-283B-4391-A9D9-6BEB46BC7F9C@.microsoft.com...
> I'm currently running SQL Server 2000 and 2005 on one machine at least I
> think I am. I have Enterprise Manager and all the other components for
> 2000
> on my laptop. I also loaded SQL Server 2005 with the .NET application from
> a
> CD that I got from a Microsoft convention a long time ago. Basically, my
> problem is when I click on the SQL SERVER 2005 Management Studio and run a
> SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
> database in 2005 and the mdf and ldf files are stored in the
> C:\...\Microsoft
> SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory.
> What
> am I doing wrong? Can 2000 and 2005 not run on the same box? This is
> preventing me from changing the database compatiblity level to 90 because
> it
> doesn't show up. Can anyone help? or suggest what I should do?
> -- TC|||Hi Terrance
Along with the other posts!! The second instance (i.e. SQL 2005) would be
installed as a named instance, therefore you should know what instance has
been connected to.
I would not expect the SQL Server 2000 instance to know if the
...\MSSQL.1\BIN directory as the MSSQL.1 directory naming was introduced in
SQL 2005. Even for the SQL 2005 instance you would expect the database files
to be put into ...\MSSQL.1\MSSQL\DATA How are you creating this database?
For a
SQL 2005 instance you can right click the instance in SSMS and choose
properties then the Database Settings will tell you the default data and log
directories, a CREATE DATABASE in a query window without specifying any of
the file names will use these directories.
To see or set the databases compatability level use sp_dbcmptlevel
EXEC sp_dbcmptlevel AdventureWorks;
GO
EXEC sp_dbcmptlevel AdventureWorks, 90;
GO
It is best to change compatibility while no users are connected to the
database!
John
"Terrance" wrote:

> I'm currently running SQL Server 2000 and 2005 on one machine at least I
> think I am. I have Enterprise Manager and all the other components for 200
0
> on my laptop. I also loaded SQL Server 2005 with the .NET application from
a
> CD that I got from a Microsoft convention a long time ago. Basically, my
> problem is when I click on the SQL SERVER 2005 Management Studio and run a
> SELECT @.@.VERSION query it shows me that 2000 is installed. I created a
> database in 2005 and the mdf and ldf files are stored in the C:\...\Micros
oft
> SQL Server\MSSQL.1\BIN directory seperate from the 2000 bin directory. Wha
t
> am I doing wrong? Can 2000 and 2005 not run on the same box? This is
> preventing me from changing the database compatiblity level to 90 because
it
> doesn't show up. Can anyone help? or suggest what I should do?
> -- TCsql

Run SQL2k SE 32-bit on 64-bit machine?

Is this possible? If so, are there any OS configurations that need to be se
t
ahead of time? When attempting to install, I am getting an error that says:
The image file autorun.exe is valid, but for a machine type other than the
current machine.
Thanks!Try running setup ipv autorun; autorun is likely a 16 bit app, which
will not run on x64.
Mitch wrote:
> Is this possible? If so, are there any OS configurations that need to be
set
> ahead of time? When attempting to install, I am getting an error that say
s:
> The image file autorun.exe is valid, but for a machine type other than the
> current machine.
> Thanks!

Run SQL2k SE 32-bit on 64-bit machine?

Is this possible? If so, are there any OS configurations that need to be set
ahead of time? When attempting to install, I am getting an error that says:
The image file autorun.exe is valid, but for a machine type other than the
current machine.
Thanks!Try running setup ipv autorun; autorun is likely a 16 bit app, which
will not run on x64.
Mitch wrote:
> Is this possible? If so, are there any OS configurations that need to be set
> ahead of time? When attempting to install, I am getting an error that says:
> The image file autorun.exe is valid, but for a machine type other than the
> current machine.
> Thanks!

run sp1 where??

i have 3 machines running report service components:
1 - a sql server
2 - a web server
3 - a development machine with vsnet2003
do i run sp1 on all 3?
please help
dushan bilbijaInstall it everywhere you installed Reporting Services.
I have IIS (and Reporting Services) installed on my SQL Server, so the only
location I had to install the SP was on the combination database/web server
and on my machine to update the client piece (that runs within VS.NET 2003).
--
Keith
"Dushan Bilbija" <dbilbija@.msn.com> wrote in message
news:e%23rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> i have 3 machines running report service components:
> 1 - a sql server
> 2 - a web server
> 3 - a development machine with vsnet2003
> do i run sp1 on all 3?
> please help
> dushan bilbija
>|||On 2 and 3.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dushan Bilbija" <dbilbija@.msn.com> wrote in message
news:e#rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> i have 3 machines running report service components:
> 1 - a sql server
> 2 - a web server
> 3 - a development machine with vsnet2003
> do i run sp1 on all 3?
> please help
> dushan bilbija
>|||Tudor, doesn't SP1 also update the server as well?
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
news:uKCfRmTXEHA.384@.TK2MSFTNGP10.phx.gbl...
> On 2 and 3.
> --
> Tudor Trufinescu
> Dev Lead
> Sql Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Dushan Bilbija" <dbilbija@.msn.com> wrote in message
> news:e#rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> > i have 3 machines running report service components:
> >
> > 1 - a sql server
> > 2 - a web server
> > 3 - a development machine with vsnet2003
> >
> > do i run sp1 on all 3?
> >
> > please help
> >
> > dushan bilbija
> >
> >
>|||I did a diff on my development SQL Server box that is running both the
reporting service and database and my production (pre SP1) ReportServer db
and there are large differences between the two. That makes me believe that
I will need to run the SP on the production database server as well as the
production Reporting Service, unless running it on the production Reporting
Service will pass the database updates automatically to its database server.
Worst thing that happens is I run the SP on the production Reporting
Service, do my diff, notice the changes haven't propogated as expected, run
the SP on the SQL Server db.
Thx, Joel
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:uKoXakWXEHA.3564@.TK2MSFTNGP11.phx.gbl...
> Tudor, doesn't SP1 also update the server as well?
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> __________________________________
> "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
> news:uKCfRmTXEHA.384@.TK2MSFTNGP10.phx.gbl...
> > On 2 and 3.
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> > "Dushan Bilbija" <dbilbija@.msn.com> wrote in message
> > news:e#rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> > > i have 3 machines running report service components:
> > >
> > > 1 - a sql server
> > > 2 - a web server
> > > 3 - a development machine with vsnet2003
> > >
> > > do i run sp1 on all 3?
> > >
> > > please help
> > >
> > > dushan bilbija
> > >
> > >
> >
> >
>|||You don't need to run SP1 setup on the SQL Server box - if that's separate
from the report server box.
When you run SP1 setup on the RS box it will update stored procs and tables
on the SQL Server box.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:uKoXakWXEHA.3564@.TK2MSFTNGP11.phx.gbl...
> Tudor, doesn't SP1 also update the server as well?
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> __________________________________
> "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
> news:uKCfRmTXEHA.384@.TK2MSFTNGP10.phx.gbl...
> > On 2 and 3.
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> > "Dushan Bilbija" <dbilbija@.msn.com> wrote in message
> > news:e#rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> > > i have 3 machines running report service components:
> > >
> > > 1 - a sql server
> > > 2 - a web server
> > > 3 - a development machine with vsnet2003
> > >
> > > do i run sp1 on all 3?
> > >
> > > please help
> > >
> > > dushan bilbija
> > >
> > >
> >
> >
>|||I don't think that there are any database related changes within Reporting
Services SP1.
--
Keith
"Mark Barker" <MarkBarker@.discussions.microsoft.com> wrote in message
news:9E97C141-6BFA-424F-A6C2-A5F6524FC824@.microsoft.com...
> Iâ've upgrade in a similar scenario (a 2 node NLB running Reporting
Services and a separate server running SQL Server). Reporting Services is
showing the appropriate version number (8.00.878.00) so all seems well on
the NLB.
> The only thing that makes me slightly nervous about the upgrade is the
fact that I didnâ't see any kind of â'upgrading database...â' dialog box, and I
have seen this dialog box where I have upgraded Reporting Services servers
that are running SQL Server and Reporting Services on the same server.
> Should I just forget about this nervousness and assume that the database
has successfully upgraded â' Is there any way to verify that the upgrade has
taken place on the SQL Server?
> Thanks,
> Mark
>
> "Tudor Trufinescu (MSFT)" wrote:
> > You don't need to run SP1 setup on the SQL Server box - if that's
separate
> > from the report server box.
> > When you run SP1 setup on the RS box it will update stored procs and
tables
> > on the SQL Server box.
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> > news:uKoXakWXEHA.3564@.TK2MSFTNGP11.phx.gbl...
> > > Tudor, doesn't SP1 also update the server as well?
> > >
> > > --
> > > ____________________________________
> > > William (Bill) Vaughn
> > > Author, Mentor, Consultant
> > > Microsoft MVP
> > > www.betav.com
> > > Please reply only to the newsgroup so that others can benefit.
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > __________________________________
> > >
> > > "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
> > > news:uKCfRmTXEHA.384@.TK2MSFTNGP10.phx.gbl...
> > > > On 2 and 3.
> > > >
> > > > --
> > > > Tudor Trufinescu
> > > > Dev Lead
> > > > Sql Server Reporting Services
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > >
> > > >
> > > > "Dushan Bilbija" <dbilbija@.msn.com> wrote in message
> > > > news:e#rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> > > > > i have 3 machines running report service components:
> > > > >
> > > > > 1 - a sql server
> > > > > 2 - a web server
> > > > > 3 - a development machine with vsnet2003
> > > > >
> > > > > do i run sp1 on all 3?
> > > > >
> > > > > please help
> > > > >
> > > > > dushan bilbija
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >|||The SP1 bits would only work on the SP1 schema, so your upgrade is OK.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mark Barker" <MarkBarker@.discussions.microsoft.com> wrote in message
news:9E97C141-6BFA-424F-A6C2-A5F6524FC824@.microsoft.com...
> I've upgrade in a similar scenario (a 2 node NLB running Reporting
Services and a separate server running SQL Server). Reporting Services is
showing the appropriate version number (8.00.878.00) so all seems well on
the NLB.
> The only thing that makes me slightly nervous about the upgrade is the
fact that I didn't see any kind of 'upgrading database...' dialog box, and I
have seen this dialog box where I have upgraded Reporting Services servers
that are running SQL Server and Reporting Services on the same server.
> Should I just forget about this nervousness and assume that the database
has successfully upgraded - Is there any way to verify that the upgrade has
taken place on the SQL Server?
> Thanks,
> Mark
>
> "Tudor Trufinescu (MSFT)" wrote:
> > You don't need to run SP1 setup on the SQL Server box - if that's
separate
> > from the report server box.
> > When you run SP1 setup on the RS box it will update stored procs and
tables
> > on the SQL Server box.
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> > news:uKoXakWXEHA.3564@.TK2MSFTNGP11.phx.gbl...
> > > Tudor, doesn't SP1 also update the server as well?
> > >
> > > --
> > > ____________________________________
> > > William (Bill) Vaughn
> > > Author, Mentor, Consultant
> > > Microsoft MVP
> > > www.betav.com
> > > Please reply only to the newsgroup so that others can benefit.
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > __________________________________
> > >
> > > "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
> > > news:uKCfRmTXEHA.384@.TK2MSFTNGP10.phx.gbl...
> > > > On 2 and 3.
> > > >
> > > > --
> > > > Tudor Trufinescu
> > > > Dev Lead
> > > > Sql Server Reporting Services
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > >
> > > >
> > > > "Dushan Bilbija" <dbilbija@.msn.com> wrote in message
> > > > news:e#rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> > > > > i have 3 machines running report service components:
> > > > >
> > > > > 1 - a sql server
> > > > > 2 - a web server
> > > > > 3 - a development machine with vsnet2003
> > > > >
> > > > > do i run sp1 on all 3?
> > > > >
> > > > > please help
> > > > >
> > > > > dushan bilbija
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >|||There are definetly database changes. My diff showed 1 table change and 13
stored procedure changes. It's just as Tudor said though, the RS Service
takes care of the updates.
-Joel
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:Oweg%239eXEHA.1152@.TK2MSFTNGP09.phx.gbl...
> I don't think that there are any database related changes within Reporting
> Services SP1.
> --
> Keith
>
> "Mark Barker" <MarkBarker@.discussions.microsoft.com> wrote in message
> news:9E97C141-6BFA-424F-A6C2-A5F6524FC824@.microsoft.com...
> > I've upgrade in a similar scenario (a 2 node NLB running Reporting
> Services and a separate server running SQL Server). Reporting Services is
> showing the appropriate version number (8.00.878.00) so all seems well on
> the NLB.
> >
> > The only thing that makes me slightly nervous about the upgrade is the
> fact that I didn't see any kind of 'upgrading database...' dialog box, and
I
> have seen this dialog box where I have upgraded Reporting Services servers
> that are running SQL Server and Reporting Services on the same server.
> >
> > Should I just forget about this nervousness and assume that the database
> has successfully upgraded - Is there any way to verify that the upgrade
has
> taken place on the SQL Server?
> >
> > Thanks,
> > Mark
> >
> >
> > "Tudor Trufinescu (MSFT)" wrote:
> >
> > > You don't need to run SP1 setup on the SQL Server box - if that's
> separate
> > > from the report server box.
> > > When you run SP1 setup on the RS box it will update stored procs and
> tables
> > > on the SQL Server box.
> > >
> > > --
> > > Tudor Trufinescu
> > > Dev Lead
> > > Sql Server Reporting Services
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > > "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> > > news:uKoXakWXEHA.3564@.TK2MSFTNGP11.phx.gbl...
> > > > Tudor, doesn't SP1 also update the server as well?
> > > >
> > > > --
> > > > ____________________________________
> > > > William (Bill) Vaughn
> > > > Author, Mentor, Consultant
> > > > Microsoft MVP
> > > > www.betav.com
> > > > Please reply only to the newsgroup so that others can benefit.
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > > __________________________________
> > > >
> > > > "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
> > > > news:uKCfRmTXEHA.384@.TK2MSFTNGP10.phx.gbl...
> > > > > On 2 and 3.
> > > > >
> > > > > --
> > > > > Tudor Trufinescu
> > > > > Dev Lead
> > > > > Sql Server Reporting Services
> > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > >
> > > > >
> > > > > "Dushan Bilbija" <dbilbija@.msn.com> wrote in message
> > > > > news:e#rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> > > > > > i have 3 machines running report service components:
> > > > > >
> > > > > > 1 - a sql server
> > > > > > 2 - a web server
> > > > > > 3 - a development machine with vsnet2003
> > > > > >
> > > > > > do i run sp1 on all 3?
> > > > > >
> > > > > > please help
> > > > > >
> > > > > > dushan bilbija
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > >
>|||Thanks Tudor
Sounds like we are all agreed that the steps for running SP1 in a Web Farm outlined in the SP1 readme should be ignored?
â'The order in which you apply SP1 is important. You must first apply SP1 to the server that hosts the report server database (this updates the database format to the SP1 version). Once you update the database, you can update the report server nodes in any order.â'
Cleary if I have implemented my Web Farm following the recommendations in Reporting Services BOL , Step 1 (run SP1 on the database server) will never work.
Thanks,
Mark
"Tudor Trufinescu (MSFT)" wrote:
> The SP1 bits would only work on the SP1 schema, so your upgrade is OK.
> --
> Tudor Trufinescu
> Dev Lead
> Sql Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Mark Barker" <MarkBarker@.discussions.microsoft.com> wrote in message
> news:9E97C141-6BFA-424F-A6C2-A5F6524FC824@.microsoft.com...
> > I've upgrade in a similar scenario (a 2 node NLB running Reporting
> Services and a separate server running SQL Server). Reporting Services is
> showing the appropriate version number (8.00.878.00) so all seems well on
> the NLB.
> >
> > The only thing that makes me slightly nervous about the upgrade is the
> fact that I didn't see any kind of 'upgrading database...' dialog box, and I
> have seen this dialog box where I have upgraded Reporting Services servers
> that are running SQL Server and Reporting Services on the same server.
> >
> > Should I just forget about this nervousness and assume that the database
> has successfully upgraded - Is there any way to verify that the upgrade has
> taken place on the SQL Server?
> >
> > Thanks,
> > Mark
> >
> >
> > "Tudor Trufinescu (MSFT)" wrote:
> >
> > > You don't need to run SP1 setup on the SQL Server box - if that's
> separate
> > > from the report server box.
> > > When you run SP1 setup on the RS box it will update stored procs and
> tables
> > > on the SQL Server box.
> > >
> > > --
> > > Tudor Trufinescu
> > > Dev Lead
> > > Sql Server Reporting Services
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > > "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> > > news:uKoXakWXEHA.3564@.TK2MSFTNGP11.phx.gbl...
> > > > Tudor, doesn't SP1 also update the server as well?
> > > >
> > > > --
> > > > ____________________________________
> > > > William (Bill) Vaughn
> > > > Author, Mentor, Consultant
> > > > Microsoft MVP
> > > > www.betav.com
> > > > Please reply only to the newsgroup so that others can benefit.
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > > __________________________________
> > > >
> > > > "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
> > > > news:uKCfRmTXEHA.384@.TK2MSFTNGP10.phx.gbl...
> > > > > On 2 and 3.
> > > > >
> > > > > --
> > > > > Tudor Trufinescu
> > > > > Dev Lead
> > > > > Sql Server Reporting Services
> > > > > This posting is provided "AS IS" with no warranties, and confers no
> > > > rights.
> > > > >
> > > > >
> > > > > "Dushan Bilbija" <dbilbija@.msn.com> wrote in message
> > > > > news:e#rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> > > > > > i have 3 machines running report service components:
> > > > > >
> > > > > > 1 - a sql server
> > > > > > 2 - a web server
> > > > > > 3 - a development machine with vsnet2003
> > > > > >
> > > > > > do i run sp1 on all 3?
> > > > > >
> > > > > > please help
> > > > > >
> > > > > > dushan bilbija
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > >
>
>|||Yes, the wording is wrong here, I will pass this to our doc team.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mark Barker" <MarkBarker@.discussions.microsoft.com> wrote in message
news:74CA554A-9BCD-46CF-B99C-AC8B8445CF55@.microsoft.com...
> Thanks Tudor
> Sounds like we are all agreed that the steps for running SP1 in a Web Farm
outlined in the SP1 readme should be ignored?
> "The order in which you apply SP1 is important. You must first apply SP1
to the server that hosts the report server database (this updates the
database format to the SP1 version). Once you update the database, you can
update the report server nodes in any order."
> Cleary if I have implemented my Web Farm following the recommendations in
Reporting Services BOL , Step 1 (run SP1 on the database server) will never
work.
> Thanks,
> Mark
>
> "Tudor Trufinescu (MSFT)" wrote:
> > The SP1 bits would only work on the SP1 schema, so your upgrade is OK.
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Mark Barker" <MarkBarker@.discussions.microsoft.com> wrote in message
> > news:9E97C141-6BFA-424F-A6C2-A5F6524FC824@.microsoft.com...
> > > I've upgrade in a similar scenario (a 2 node NLB running Reporting
> > Services and a separate server running SQL Server). Reporting Services
is
> > showing the appropriate version number (8.00.878.00) so all seems well
on
> > the NLB.
> > >
> > > The only thing that makes me slightly nervous about the upgrade is the
> > fact that I didn't see any kind of 'upgrading database...' dialog box,
and I
> > have seen this dialog box where I have upgraded Reporting Services
servers
> > that are running SQL Server and Reporting Services on the same server.
> > >
> > > Should I just forget about this nervousness and assume that the
database
> > has successfully upgraded - Is there any way to verify that the upgrade
has
> > taken place on the SQL Server?
> > >
> > > Thanks,
> > > Mark
> > >
> > >
> > > "Tudor Trufinescu (MSFT)" wrote:
> > >
> > > > You don't need to run SP1 setup on the SQL Server box - if that's
> > separate
> > > > from the report server box.
> > > > When you run SP1 setup on the RS box it will update stored procs and
> > tables
> > > > on the SQL Server box.
> > > >
> > > > --
> > > > Tudor Trufinescu
> > > > Dev Lead
> > > > Sql Server Reporting Services
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in
message
> > > > news:uKoXakWXEHA.3564@.TK2MSFTNGP11.phx.gbl...
> > > > > Tudor, doesn't SP1 also update the server as well?
> > > > >
> > > > > --
> > > > > ____________________________________
> > > > > William (Bill) Vaughn
> > > > > Author, Mentor, Consultant
> > > > > Microsoft MVP
> > > > > www.betav.com
> > > > > Please reply only to the newsgroup so that others can benefit.
> > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > > __________________________________
> > > > >
> > > > > "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
> > > > > news:uKCfRmTXEHA.384@.TK2MSFTNGP10.phx.gbl...
> > > > > > On 2 and 3.
> > > > > >
> > > > > > --
> > > > > > Tudor Trufinescu
> > > > > > Dev Lead
> > > > > > Sql Server Reporting Services
> > > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > > rights.
> > > > > >
> > > > > >
> > > > > > "Dushan Bilbija" <dbilbija@.msn.com> wrote in message
> > > > > > news:e#rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> > > > > > > i have 3 machines running report service components:
> > > > > > >
> > > > > > > 1 - a sql server
> > > > > > > 2 - a web server
> > > > > > > 3 - a development machine with vsnet2003
> > > > > > >
> > > > > > > do i run sp1 on all 3?
> > > > > > >
> > > > > > > please help
> > > > > > >
> > > > > > > dushan bilbija
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> >
> >
> >

Run reports in another machine

Hello,

Can I deploy my reports to another machine which does not have a SQL Server installed and run it from there?

Thanks,

Jim.

Hi,
you can deploy your reports to another machine.
Target machine must have Reporting Services installed, of course.
In the Target Machine Reporting Services (http://targetmachine/reports) you can
deploy your reports by Upload File function.

|||Can I install Reporting Service to a machine which does not have a SQL Server installed?|||

Yes,
you can install Reporting Services to a machine without Sql Server.
During installation setup, you have to provide Sql Server infos (machine name, user account, ecc.)
about machine which have Sql Server where Reporting Services will create
necessary data (ReportServer and ReportServerTempDb tables).

|||

Thanks you very much this is really helpful information. Will this installation require another license? My of my friend told me RS is free and as long as I have Standard SQL Server I can install RS to more than one machine, is that correct?

|||Hello JIM.H.,
Yes, that is the catch. You have to have a SQL Server license for each server
that will be running a portion of the server product.|||

So,

Thank you for your reply. If I have a Standard SQL Server (does it have to be Enterprise?) and I need to install RS in one development and one another server as live, I have to have two licenses for RS?

Thanks

|||Yes, that is my understanding of the current license agreement. It is also answered as question #1 in the FAQ:http://www.microsoft.com/sql/reporting/howtobuy/faq.asp

Run dynamic SQL in debugger, get sql dump

If memory serves there was a bug with the debugger where
if you run it from the client machine it would either not
work, or result in an error (sorry can't find the
Microsoft Page).
How I solved this is to run the debugger on the server.
One of the Great Ones, Uri, Narayana, Wayne, Dejan, Tibor,
Dan, Andrew or Adam could probably tell you the reason and
the fix.
Peter
"I favor the Civil Rights Act of 1964 and it must be
enforced at gunpoint if necessary."
Ronald Reagan

>--Original Message--
>
>Hi,
>One of our developer runs a stored procedure containing
dynamic SQL in
>T-SQL Debugger. She consistently gets error ( see below ):
>SqlDumpExceptionHandler: Process 73 generated fatal
exception c0000005
>EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating
this process.
>If she runs it without debugger, it runs fine. She checks
the code many
>times and can't find anything wrong in the code. We have
no idea what's
>wrong.
>The server is a SQL Server 2000 (SP3) on a Window 2000
with service pack
>4.
>Thank you.
>
>*** Sent via Developersdex http://www.codecomments.com
***
>Don't just participate in USENET...get rewarded for it!
>.
>
Thanx for the response.
She ran it on the server and got the same error.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Run dynamic SQL in debugger, get sql dump

If memory serves there was a bug with the debugger where
if you run it from the client machine it would either not
work, or result in an error (sorry can't find the
Microsoft Page).
How I solved this is to run the debugger on the server.
One of the Great Ones, Uri, Narayana, Wayne, Dejan, Tibor,
Dan, Andrew or Adam could probably tell you the reason and
the fix.
Peter
"I favor the Civil Rights Act of 1964 and it must be
enforced at gunpoint if necessary."
Ronald Reagan

>--Original Message--
>
>Hi,
>One of our developer runs a stored procedure containing
dynamic SQL in
>T-SQL Debugger. She consistently gets error ( see below ):
>SqlDumpExceptionHandler: Process 73 generated fatal
exception c0000005
>EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating
this process.
>If she runs it without debugger, it runs fine. She checks
the code many
>times and can't find anything wrong in the code. We have
no idea what's
>wrong.
>The server is a SQL Server 2000 (SP3) on a Window 2000
with service pack
>4.
>Thank you.
>
>*** Sent via Developersdex http://www.codecomments.com
***
>Don't just participate in USENET...get rewarded for it!
>.
>Thanx for the response.
She ran it on the server and got the same error.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Run DTS packages

I have users who need to run DTS packages but I don't want to put the full
SQL toolset on their machine. Is there a way to just install the ability to
run a DTS package?Take a look at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dtssql/dts_tools_other_8reb.asp
I think you can simply install client connectivity and dtsrun.exe... You
can even encrypt the connection information so they will not even know the
login stuff.
Also take a look at DTSRUNui...which will give your end user a little gui
interface to run packages.
--
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
"Mark Polino" <mpolino@.earthlink.net> wrote in message
news:uifNMo9VEHA.3696@.TK2MSFTNGP10.phx.gbl...
> I have users who need to run DTS packages but I don't want to put the full
> SQL toolset on their machine. Is there a way to just install the ability
to
> run a DTS package?
>
>|||There are dts specific resource files as well as dlls that
need to be registered for users to be able to execute
packages. You can find the list of these in the following
article:
Redistributing DTS with your program
http://www.sqldts.com/default.aspx?225
-Sue
On Mon, 21 Jun 2004 17:54:02 -0400, "Mark Polino"
<mpolino@.earthlink.net> wrote:
>I have users who need to run DTS packages but I don't want to put the full
>SQL toolset on their machine. Is there a way to just install the ability to
>run a DTS package?
>

Run DTS packages

I have users who need to run DTS packages but I don't want to put the full
SQL toolset on their machine. Is there a way to just install the ability to
run a DTS package?
Take a look at
http://msdn.microsoft.com/library/de...other_8reb.asp
I think you can simply install client connectivity and dtsrun.exe... You
can even encrypt the connection information so they will not even know the
login stuff.
Also take a look at DTSRUNui...which will give your end user a little gui
interface to run packages.
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
"Mark Polino" <mpolino@.earthlink.net> wrote in message
news:uifNMo9VEHA.3696@.TK2MSFTNGP10.phx.gbl...
> I have users who need to run DTS packages but I don't want to put the full
> SQL toolset on their machine. Is there a way to just install the ability
to
> run a DTS package?
>
>
|||There are dts specific resource files as well as dlls that
need to be registered for users to be able to execute
packages. You can find the list of these in the following
article:
Redistributing DTS with your program
http://www.sqldts.com/default.aspx?225
-Sue
On Mon, 21 Jun 2004 17:54:02 -0400, "Mark Polino"
<mpolino@.earthlink.net> wrote:

>I have users who need to run DTS packages but I don't want to put the full
>SQL toolset on their machine. Is there a way to just install the ability to
>run a DTS package?
>

Run DTS packages

I have users who need to run DTS packages but I don't want to put the full
SQL toolset on their machine. Is there a way to just install the ability to
run a DTS package?Take a look at
other_8reb.asp" target="_blank">http://msdn.microsoft.com/library/d...
other_8reb.asp
I think you can simply install client connectivity and dtsrun.exe... You
can even encrypt the connection information so they will not even know the
login stuff.
Also take a look at DTSRUNui...which will give your end user a little gui
interface to run packages.
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
"Mark Polino" <mpolino@.earthlink.net> wrote in message
news:uifNMo9VEHA.3696@.TK2MSFTNGP10.phx.gbl...
> I have users who need to run DTS packages but I don't want to put the full
> SQL toolset on their machine. Is there a way to just install the ability
to
> run a DTS package?
>
>|||There are dts specific resource files as well as dlls that
need to be registered for users to be able to execute
packages. You can find the list of these in the following
article:
Redistributing DTS with your program
http://www.sqldts.com/default.aspx?225
-Sue
On Mon, 21 Jun 2004 17:54:02 -0400, "Mark Polino"
<mpolino@.earthlink.net> wrote:

>I have users who need to run DTS packages but I don't want to put the full
>SQL toolset on their machine. Is there a way to just install the ability to
>run a DTS package?
>