Question about reportBuilder (Installation)

Hi !

I've already ask this question a couple of weeks ago but nobody answer me so i'll ask again .

We have a web application using ReportServer. Some of our client want to be able to create their own reports and to add them. So we thought that ReportBuilder could be a good idea. We would create model for them and using ReportBuilder they could create easily their reports.

My question is how can i install ReportBuilder ? What i mean is reportBuilder seems to be working fine when he is install on the Server. What i want is to install ReportBuilder on different computer and configue ReportBuilder to connect to the Server. Is it possible ? How ? Do we need to buy licence ?

Thanks !

Report builder is a thin client application. And it will be installed on the computer when it is called for the first time. So it doesn't need to be pre-installed. I also don't think it uses seperate licening because it is a part of sql server 2005.

If you don't want the users to open report builder through Report Manager, you can always call report builder through url access. That way report builder will be opend (or installed if it's the first time you call it) directly.

More info about these url access:
Bob Meyers blog: Report Builder launch parameters: http://blogs.msdn.com/bobmeyers/archive/2006/01/24/517083.aspx

I hope this helps!

|||Thanks a lot !!!! This is exactly what i was looking for !!|||

I have a similar problem.

I do see Report Builder button on the Server, but do not see it from a remote machine in Report Manager.

Yes I can Report Builder with http://<servername>/reportserver/reportbuilder/reportbuilder.application

How do I make the Report Builder button appear on remote machines?

Thanks

|||

Rob68:

Please see these MSDN articles:

http://msdn2.microsoft.com/en-us/library/ms365173.aspx
http://msdn2.microsoft.com/en-us/library/ms159667.aspx

|||

Hypo,

Thanks for leading me in the right direction, but my problem is still unresolved.

These articles state: Assign to a user the roles of Report Builder and System User.

I can assign the role of Report Builder but do not see any way of assigning the role of the System User.

What am I missing? I am, BTW, using Report Manager in SQL Server 2005. It comes with these two roles pre-defined.

thanks

|||

Hi, do it from the Report Manager web page:

site settings -> Configure site-wide security -> New Role Assignment -> add user to 'System User'

Mountain

Question about dynamic report

Hi:

I have a question of create a dynamic the report.

For example: At the beginning I have 3 columns in the report, build by VS. After couple weeks, the same report needs to have more columns. And i don't want to use the VS to modify the layout manually, instead, when adding new columns, I can call a function to modify the rdl file add attributes into the xml file automatically. But after that which way I can go to publish the modified report into the report server, then when user clicks on that report again, there will be more columns show up.

thanks

LuZ,

You can use the Reporting Services web service to publish the new report. See this link for documentation:

http://msdn2.microsoft.com/en-us/library/ms154697.aspx

-Ryan

Question about dynamic report

Hi:

I have a question of create a dynamic the report.

For example: At the beginning I have 3 columns in the report, build by VS. After couple weeks, the same report needs to have more columns. And i don't want to use the VS to modify the layout manually, instead, when adding new columns, I can call a function to modify the rdl file add attributes into the xml file automatically. But after that which way I can go to publish the modified report into the report server, then when user clicks on that report again, there will be more columns show up.

thanks

LuZ,

You can use the Reporting Services web service to publish the new report. See this link for documentation:

http://msdn2.microsoft.com/en-us/library/ms154697.aspx

-Ryan

Question about detaching databases.

I need to have someone clarify a couple things for me.
1. If a system running MSDE is rebooted in the middle of a transaction, I
am assuming at some point when the system is restarted, the transaction log
file is rolled back into the main database file. However, if a database is
detached before anyone connects to it, will the uncommitted transaction log
data be rolled into the main database file before the detach is performed?
2. When exactly does the uncommitted transaction log data get rolled back
into the database after a reboot in the middle of a transaction?
--
Ken Varn
Senior Software Engineer
Diebold Inc.
EmailID = varnk
Domain = Diebold.com
hi Ken,
Ken Varn wrote:
> I need to have someone clarify a couple things for me.
> 1. If a system running MSDE is rebooted in the middle of a
> transaction, I am assuming at some point when the system is
> restarted, the transaction log file is rolled back into the main
> database file. However, if a database is detached before anyone
> connects to it, will the uncommitted transaction log data be rolled
> into the main database file before the detach is performed?
when a system stops (crashes or is unproperly shut down), all the pending
transactions are aborted ..
when the SQL Service restarts, it will stars and recover all databases...
that's to say committed transaction will be rolled forward and uncommitted
rolled back.. the algorithm is quiet complex as SQL Server searches the best
method to perform this task to put the db on line and available as soon as
possible..
so you are not entitled to detach the db before the db has been recovered..
you can perhaps move the physical files before starting SQL Server, but then
the db will be marked as corrupted as SQL Server can no longer find the db
files as registered in it's system tables, so this is not a good idea...
> 2. When exactly does the uncommitted transaction log data get rolled
> back into the database after a reboot in the middle of a transaction?
as soon as the db is recovered... if you open the log file of SQL Server, in
the \Log folder, and inspect one of the ERRORLOG files you'll see something
like
2005-08-11 16:33:22.45 spid8 Starting up database 'msdb'.
2005-08-11 16:33:22.48 spid9 Starting up database 'pubs'.
2005-08-11 16:33:22.49 spid10 Starting up database 'Northwind'.
2005-08-11 16:33:22.51 spid11 Starting up database 'a'.
2005-08-11 16:33:23.17 spid5 Clearing tempdb database.
2005-08-11 16:33:23.21 spid11 Starting up database 'atest'.
2005-08-11 16:33:24.35 spid5 Starting up database 'tempdb'.
2005-08-11 16:33:24.45 spid3 Recovery complete.
....
if something is pending fo a specific database you'll see rollforwad and
rollback operations...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||> so you are not entitled to detach the db before the db has been
recovered..
> you can perhaps move the physical files before starting SQL Server, but
then
> the db will be marked as corrupted as SQL Server can no longer find the db
> files as registered in it's system tables, so this is not a good idea...
So that I can clarify what you are saying here. SQL Server will not allow
you to detach a database until it has completed the recovery process?
I basically want to know if it is safe to get rid of the LDF file after a
database has been detached without any adverse ramifications, like database
corruption.
--
Ken Varn
Senior Software Engineer
Diebold Inc.
EmailID = varnk
Domain = Diebold.com
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3m3sgtF159l9rU1@.individual.net...
> hi Ken,
> Ken Varn wrote:
> when a system stops (crashes or is unproperly shut down), all the pending
> transactions are aborted ..
> when the SQL Service restarts, it will stars and recover all databases...
> that's to say committed transaction will be rolled forward and uncommitted
> rolled back.. the algorithm is quiet complex as SQL Server searches the
best
> method to perform this task to put the db on line and available as soon as
> possible..
> so you are not entitled to detach the db before the db has been
recovered..
> you can perhaps move the physical files before starting SQL Server, but
then
> the db will be marked as corrupted as SQL Server can no longer find the db
> files as registered in it's system tables, so this is not a good idea...
> as soon as the db is recovered... if you open the log file of SQL Server,
in
> the \Log folder, and inspect one of the ERRORLOG files you'll see
something
> like
> 2005-08-11 16:33:22.45 spid8 Starting up database 'msdb'.
> 2005-08-11 16:33:22.48 spid9 Starting up database 'pubs'.
> 2005-08-11 16:33:22.49 spid10 Starting up database 'Northwind'.
> 2005-08-11 16:33:22.51 spid11 Starting up database 'a'.
> 2005-08-11 16:33:23.17 spid5 Clearing tempdb database.
> 2005-08-11 16:33:23.21 spid11 Starting up database 'atest'.
> 2005-08-11 16:33:24.35 spid5 Starting up database 'tempdb'.
> 2005-08-11 16:33:24.45 spid3 Recovery complete.
> ...
> if something is pending fo a specific database you'll see rollforwad and
> rollback operations...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Ken,
Ken Varn wrote:
> So that I can clarify what you are saying here. SQL Server will not
> allow you to detach a database until it has completed the recovery
> process?
until the recovery has been completed, SQL Server does not allow to touch
all dbs at all... it is still "starting"...

> I basically want to know if it is safe to get rid of the LDF file
> after a database has been detached without any adverse ramifications,
> like database corruption.
actually you should not get rid of the LDF file at all, as it is a needed
part of a database... even when the simple recovery model is used you should
always provide all transaction log files... you can use
sp_attach_single_file_db when they are not present but best practice implies
forwarding them too...
say you have a db file named [myDb] with 1 physical data file as
C:\..\myDb.Mdf and a t-log file C:\..\myDb.Ldf...
you only provide me the C:\..\myDb.Mdf instructing me to attach it via
sp_attach_single_file_db ...
on my system I already have another company sw which uses a db with the very
same physical data files (and names)...
the corresponding datafile will be C:\..\myDb.Mdf as the log file in
C:\..\myDb.Ldf
as I can not put your db in the same folder I move it to
C:\anotherDir\myDb.Mdf and use sp_attach_single_file_db ... the problem,
now... SQL Server try to create a new t-log file using the available info
(sysfiles and sysfiles1 system table) and will point to the other company
database C:\..\myDb.Ldf physical file...
that log file will be pointed by 2 db and will immediately raises exception
marking 1 of the 2 db as suspect...
to solve this problem I need the t-log of your db and the use of
sp_attach_db indicating all the required physical files..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||> actually you should not get rid of the LDF file at all, as it is a needed
> part of a database... even when the simple recovery model is used you
should
> always provide all transaction log files... you can use
> sp_attach_single_file_db when they are not present but best practice
implies
> forwarding them too...
> say you have a db file named [myDb] with 1 physical data file as
> C:\..\myDb.Mdf and a t-log file C:\..\myDb.Ldf...
> you only provide me the C:\..\myDb.Mdf instructing me to attach it via
> sp_attach_single_file_db ...
> on my system I already have another company sw which uses a db with the
very
> same physical data files (and names)...
> the corresponding datafile will be C:\..\myDb.Mdf as the log file in
> C:\..\myDb.Ldf
It sounds as if as long as I do not try to attach a database onto a system
that has the same database name I can use sp_attach_single_file_db with no
adverse affects. Or, are there other issues that I should be concerned
with?
Basically, without trying to go into too much detail here, our system has an
automated process that periodically detaches databases, removes the ldf file
and archives the mdf file. The system may re-attach any of these databases
again at a later time depending on certain circumstances. We have been
seeing some database corruption issues and have tried to determine if this
process is the cause. We do know that occasionally the system is restarted
due to power failures (although the UPS is doing an orderly shutdown) and we
want to figure out if our detach and removal of LDF file process could be
the cause of databases getting corrupt after we re-attach them during a
restart from a power fail.
--
Ken Varn
Senior Software Engineer
Diebold Inc.
EmailID = varnk
Domain = Diebold.com
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3m444tF155s4gU1@.individual.net...
> hi Ken,
> Ken Varn wrote:
> until the recovery has been completed, SQL Server does not allow to touch
> all dbs at all... it is still "starting"...
>
> actually you should not get rid of the LDF file at all, as it is a needed
> part of a database... even when the simple recovery model is used you
should
> always provide all transaction log files... you can use
> sp_attach_single_file_db when they are not present but best practice
implies
> forwarding them too...
> say you have a db file named [myDb] with 1 physical data file as
> C:\..\myDb.Mdf and a t-log file C:\..\myDb.Ldf...
> you only provide me the C:\..\myDb.Mdf instructing me to attach it via
> sp_attach_single_file_db ...
> on my system I already have another company sw which uses a db with the
very
> same physical data files (and names)...
> the corresponding datafile will be C:\..\myDb.Mdf as the log file in
> C:\..\myDb.Ldf
> as I can not put your db in the same folder I move it to
> C:\anotherDir\myDb.Mdf and use sp_attach_single_file_db ... the problem,
> now... SQL Server try to create a new t-log file using the available info
> (sysfiles and sysfiles1 system table) and will point to the other company
> database C:\..\myDb.Ldf physical file...
> that log file will be pointed by 2 db and will immediately raises
exception
> marking 1 of the 2 db as suspect...
> to solve this problem I need the t-log of your db and the use of
> sp_attach_db indicating all the required physical files..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Ken,
> It sounds as if as long as I do not try to attach a database onto a
> system that has the same database name I can use
> sp_attach_single_file_db with no adverse affects. Or, are there
> other issues that I should be concerned with?
should not... SQL Server will try to recreate the log file(s) based on the
original info... and if no "problem" is found it should be able to correctly
attach the db..

> Basically, without trying to go into too much detail here, our system
> has an automated process that periodically detaches databases,
> removes the ldf file and archives the mdf file. The system may
> re-attach any of these databases again at a later time depending on
> certain circumstances. We have been seeing some database corruption
> issues and have tried to determine if this process is the cause. We
> do know that occasionally the system is restarted due to power
> failures (although the UPS is doing an orderly shutdown) and we want
> to figure out if our detach and removal of LDF file process could be
> the cause of databases getting corrupt after we re-attach them during
> a restart from a power fail.
missing log files in recovery moment can be a problem... I'd archive the log
files as well, even in simple recovery model..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Question about deploying DTS objects (COM, DTSRUN.exe, etc.).

Hello all!
I have a series of file-based DTS packages that I want to execute from our
web servers, and I have a couple of questions about the deployment of the
objects necessary to support these packages.
In my DTS packages, I have some ActiveX scripts that do some "package
manipulation" (enabling/disabling Steps, etc.). I'm guessing I'd need the
DTS COM objects to be installed and registered on the web servers?
Additionally, the DTS packages will be invoked by DTSRUN.exe on the Web
servers, so I'd probably need to install that (and any dependencies?) on the
Web servers.
I'm not really sure which files I need, or where to start looking. Are
there any licensing issues involved with having the DTS components on our
production web servers?
I'd be grateful for any assistance anyone can provide! :-)
John PetersonThis article is helpful
Redistributing DTS with your program
(http://www.sqldts.com/default.aspx?225)
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:%23AymH4SbFHA.1404@.TK2MSFTNGP09.phx.gbl...
> Hello all!
> I have a series of file-based DTS packages that I want to execute from our
> web servers, and I have a couple of questions about the deployment of the
> objects necessary to support these packages.
> In my DTS packages, I have some ActiveX scripts that do some "package
> manipulation" (enabling/disabling Steps, etc.). I'm guessing I'd need the
> DTS COM objects to be installed and registered on the web servers?
> Additionally, the DTS packages will be invoked by DTSRUN.exe on the Web
> servers, so I'd probably need to install that (and any dependencies?) on
> the Web servers.
> I'm not really sure which files I need, or where to start looking. Are
> there any licensing issues involved with having the DTS components on our
> production web servers?
> I'd be grateful for any assistance anyone can provide! :-)
> John Peterson
>|||Thanks Allan! I had *just* chanced upon that link when you replied. :-)
I notice that there's no mention of any licensing issues. Do you have any
suggestions regarding that?
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:OLzhPCTbFHA.3040@.TK2MSFTNGP14.phx.gbl...
> This article is helpful
> Redistributing DTS with your program
> (http://www.sqldts.com/default.aspx?225)
> --
>
> Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
> www.SQLDTS.com - The site for all your DTS needs.
> www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
> www.konesans.com - Consultancy from the people who know
>
> "John Peterson" <j0hnp@.comcast.net> wrote in message
> news:%23AymH4SbFHA.1404@.TK2MSFTNGP09.phx.gbl...
>|||Licencing - yuck.
Have a look in redist.txt.
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:ubodiFTbFHA.1148@.tk2msftngp13.phx.gbl...
> Thanks Allan! I had *just* chanced upon that link when you replied. :-)
> I notice that there's no mention of any licensing issues. Do you have any
> suggestions regarding that?
>
> "Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
> news:OLzhPCTbFHA.3040@.TK2MSFTNGP14.phx.gbl...
>

Question about deploying DTS objects (COM, DTSRUN.exe, etc.).

Hello all!
I have a series of file-based DTS packages that I want to execute from our
web servers, and I have a couple of questions about the deployment of the
objects necessary to support these packages.
In my DTS packages, I have some ActiveX scripts that do some "package
manipulation" (enabling/disabling Steps, etc.). I'm guessing I'd need the
DTS COM objects to be installed and registered on the web servers?
Additionally, the DTS packages will be invoked by DTSRUN.exe on the Web
servers, so I'd probably need to install that (and any dependencies?) on the
Web servers.
I'm not really sure which files I need, or where to start looking. Are
there any licensing issues involved with having the DTS components on our
production web servers?
I'd be grateful for any assistance anyone can provide! :-)
John PetersonThis article is helpful
Redistributing DTS with your program
(http://www.sqldts.com/default.aspx?225)
--
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:%23AymH4SbFHA.1404@.TK2MSFTNGP09.phx.gbl...
> Hello all!
> I have a series of file-based DTS packages that I want to execute from our
> web servers, and I have a couple of questions about the deployment of the
> objects necessary to support these packages.
> In my DTS packages, I have some ActiveX scripts that do some "package
> manipulation" (enabling/disabling Steps, etc.). I'm guessing I'd need the
> DTS COM objects to be installed and registered on the web servers?
> Additionally, the DTS packages will be invoked by DTSRUN.exe on the Web
> servers, so I'd probably need to install that (and any dependencies?) on
> the Web servers.
> I'm not really sure which files I need, or where to start looking. Are
> there any licensing issues involved with having the DTS components on our
> production web servers?
> I'd be grateful for any assistance anyone can provide! :-)
> John Peterson
>|||Thanks Allan! I had *just* chanced upon that link when you replied. :-)
I notice that there's no mention of any licensing issues. Do you have any
suggestions regarding that?
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:OLzhPCTbFHA.3040@.TK2MSFTNGP14.phx.gbl...
> This article is helpful
> Redistributing DTS with your program
> (http://www.sqldts.com/default.aspx?225)
> --
>
> Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
> www.SQLDTS.com - The site for all your DTS needs.
> www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
> www.konesans.com - Consultancy from the people who know
>
> "John Peterson" <j0hnp@.comcast.net> wrote in message
> news:%23AymH4SbFHA.1404@.TK2MSFTNGP09.phx.gbl...
>> Hello all!
>> I have a series of file-based DTS packages that I want to execute from
>> our web servers, and I have a couple of questions about the deployment of
>> the objects necessary to support these packages.
>> In my DTS packages, I have some ActiveX scripts that do some "package
>> manipulation" (enabling/disabling Steps, etc.). I'm guessing I'd need
>> the DTS COM objects to be installed and registered on the web servers?
>> Additionally, the DTS packages will be invoked by DTSRUN.exe on the Web
>> servers, so I'd probably need to install that (and any dependencies?) on
>> the Web servers.
>> I'm not really sure which files I need, or where to start looking. Are
>> there any licensing issues involved with having the DTS components on our
>> production web servers?
>> I'd be grateful for any assistance anyone can provide! :-)
>> John Peterson
>>
>|||Licencing - yuck.
Have a look in redist.txt.
--
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:ubodiFTbFHA.1148@.tk2msftngp13.phx.gbl...
> Thanks Allan! I had *just* chanced upon that link when you replied. :-)
> I notice that there's no mention of any licensing issues. Do you have any
> suggestions regarding that?
>
> "Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
> news:OLzhPCTbFHA.3040@.TK2MSFTNGP14.phx.gbl...
>> This article is helpful
>> Redistributing DTS with your program
>> (http://www.sqldts.com/default.aspx?225)
>> --
>>
>> Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
>> www.SQLDTS.com - The site for all your DTS needs.
>> www.SQLIS.com - You thought DTS was good. here we show you the new
>> stuff.
>> www.konesans.com - Consultancy from the people who know
>>
>> "John Peterson" <j0hnp@.comcast.net> wrote in message
>> news:%23AymH4SbFHA.1404@.TK2MSFTNGP09.phx.gbl...
>> Hello all!
>> I have a series of file-based DTS packages that I want to execute from
>> our web servers, and I have a couple of questions about the deployment
>> of the objects necessary to support these packages.
>> In my DTS packages, I have some ActiveX scripts that do some "package
>> manipulation" (enabling/disabling Steps, etc.). I'm guessing I'd need
>> the DTS COM objects to be installed and registered on the web servers?
>> Additionally, the DTS packages will be invoked by DTSRUN.exe on the Web
>> servers, so I'd probably need to install that (and any dependencies?) on
>> the Web servers.
>> I'm not really sure which files I need, or where to start looking. Are
>> there any licensing issues involved with having the DTS components on
>> our production web servers?
>> I'd be grateful for any assistance anyone can provide! :-)
>> John Peterson
>>
>>
>

Question about deploying DTS objects (COM, DTSRUN.exe, etc.).

Hello all!
I have a series of file-based DTS packages that I want to execute from our
web servers, and I have a couple of questions about the deployment of the
objects necessary to support these packages.
In my DTS packages, I have some ActiveX scripts that do some "package
manipulation" (enabling/disabling Steps, etc.). I'm guessing I'd need the
DTS COM objects to be installed and registered on the web servers?
Additionally, the DTS packages will be invoked by DTSRUN.exe on the Web
servers, so I'd probably need to install that (and any dependencies?) on the
Web servers.
I'm not really sure which files I need, or where to start looking. Are
there any licensing issues involved with having the DTS components on our
production web servers?
I'd be grateful for any assistance anyone can provide! :-)
John Peterson
This article is helpful
Redistributing DTS with your program
(http://www.sqldts.com/default.aspx?225)
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:%23AymH4SbFHA.1404@.TK2MSFTNGP09.phx.gbl...
> Hello all!
> I have a series of file-based DTS packages that I want to execute from our
> web servers, and I have a couple of questions about the deployment of the
> objects necessary to support these packages.
> In my DTS packages, I have some ActiveX scripts that do some "package
> manipulation" (enabling/disabling Steps, etc.). I'm guessing I'd need the
> DTS COM objects to be installed and registered on the web servers?
> Additionally, the DTS packages will be invoked by DTSRUN.exe on the Web
> servers, so I'd probably need to install that (and any dependencies?) on
> the Web servers.
> I'm not really sure which files I need, or where to start looking. Are
> there any licensing issues involved with having the DTS components on our
> production web servers?
> I'd be grateful for any assistance anyone can provide! :-)
> John Peterson
>
|||Thanks Allan! I had *just* chanced upon that link when you replied. :-)
I notice that there's no mention of any licensing issues. Do you have any
suggestions regarding that?
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:OLzhPCTbFHA.3040@.TK2MSFTNGP14.phx.gbl...
> This article is helpful
> Redistributing DTS with your program
> (http://www.sqldts.com/default.aspx?225)
> --
>
> Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
> www.SQLDTS.com - The site for all your DTS needs.
> www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
> www.konesans.com - Consultancy from the people who know
>
> "John Peterson" <j0hnp@.comcast.net> wrote in message
> news:%23AymH4SbFHA.1404@.TK2MSFTNGP09.phx.gbl...
>
|||Licencing - yuck.
Have a look in redist.txt.
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:ubodiFTbFHA.1148@.tk2msftngp13.phx.gbl...
> Thanks Allan! I had *just* chanced upon that link when you replied. :-)
> I notice that there's no mention of any licensing issues. Do you have any
> suggestions regarding that?
>
> "Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
> news:OLzhPCTbFHA.3040@.TK2MSFTNGP14.phx.gbl...
>

Question about Database Collations

I sent a couple of detached databases to a customer. When he installed his SQL Server he got database collation value of Latin1_General_CI_AS however, when he attached my databases they have a collation value of SQL_Latin1_General_CPI_CI_AS.

Now my stored procedures that use temp files are failing and a message is coming out SQL Server "Cannot resolve collation conflict for equal to operation"

I am assuming that the temp database has one collation value and my databases has another.

Q. Can anyone tell me the difference between the two collations? He is in Australia, I am in Canada - would he get a different default than I do?

Q. Can I safely alter the collation sequence of either the databases I sent or the temp database so that they match?

I have never run across this before but this is the first time I shipped the database offshore.

Thanks for any help you can give me. I am going to have to send my database to the Caribbean pretty soon and I need to know if this is going to happen there as well.

Well now that I've solved the problem I wonder what is the reasoning behind the defaults chosen by install.

First I can find no provision in the SQL Install to change the Default collation value.

My customer in Australia installed SQL Server on a new installation of Windows Server 2003 and got Latin1_General_CI_AS.
I built a brand new instance of Windows Server 2003 and when I installed SQL I got SQL_Latin1_General_CP1_CI_AS

The problem with my databases was in the stored procedures that used temporary tables - the collation values were different in the two databases and any comparisons on character fields failed.

I can work around the problem by altering all the stored procedures to include the collation clause to override the collation of tempdb. Is this the best way? I'm not sure. Is it a good practice to always include the collation clause when defining a table? I've always looked at it as kind of an annoyance -- never again
|||

I am replying to this fairly old post because others may be wondering why they get the SQL_Latin1_General_CP1_CI_AS collation.

I believe that this is the 'old fashioned' collation used by versions of SQL Server prior to 2000. It seems to be offered on upgrade, whereas Latin1_General_CI_AS is used in from scratch installations. Certainly the latter is preferred.

I'm disappointed that SQL2005 doesn't have a change collation wizard and you need to create a DMO script in order to change the collation of existing databases.

|||

did you know which were the installation parameters you choose to get SQL_Latin1_General_CP1_CI_AS?

thanks for your help

|||

Andres,

Upon installation, you need to select "Collation designator and sort order:"
Set it to "Latin1_General"
then, check the box for "Accent - sensitive"

That should do it!

Question about Database Collations

I sent a couple of detached databases to a customer. When he installed his SQL Server he got database collation value of Latin1_General_CI_AS however, when he attached my databases they have a collation value of SQL_Latin1_General_CPI_CI_AS.

Now my stored procedures that use temp files are failing and a message is coming out SQL Server "Cannot resolve collation conflict for equal to operation"

I am assuming that the temp database has one collation value and my databases has another.

Q. Can anyone tell me the difference between the two collations? He is in Australia, I am in Canada - would he get a different default than I do?

Q. Can I safely alter the collation sequence of either the databases I sent or the temp database so that they match?

I have never run across this before but this is the first time I shipped the database offshore.

Thanks for any help you can give me. I am going to have to send my database to the Caribbean pretty soon and I need to know if this is going to happen there as well.

Well now that I've solved the problem I wonder what is the reasoning behind the defaults chosen by install.

First I can find no provision in the SQL Install to change the Default collation value.

My customer in Australia installed SQL Server on a new installation of Windows Server 2003 and got Latin1_General_CI_AS.
I built a brand new instance of Windows Server 2003 and when I installed SQL I got SQL_Latin1_General_CP1_CI_AS

The problem with my databases was in the stored procedures that used temporary tables - the collation values were different in the two databases and any comparisons on character fields failed.

I can work around the problem by altering all the stored procedures to include the collation clause to override the collation of tempdb. Is this the best way? I'm not sure. Is it a good practice to always include the collation clause when defining a table? I've always looked at it as kind of an annoyance -- never again
|||

I am replying to this fairly old post because others may be wondering why they get the SQL_Latin1_General_CP1_CI_AS collation.

I believe that this is the 'old fashioned' collation used by versions of SQL Server prior to 2000. It seems to be offered on upgrade, whereas Latin1_General_CI_AS is used in from scratch installations. Certainly the latter is preferred.

I'm disappointed that SQL2005 doesn't have a change collation wizard and you need to create a DMO script in order to change the collation of existing databases.

|||

did you know which were the installation parameters you choose to get SQL_Latin1_General_CP1_CI_AS?

thanks for your help

|||

Andres,

Upon installation, you need to select "Collation designator and sort order:"
Set it to "Latin1_General"
then, check the box for "Accent - sensitive"

That should do it!