How to deploy SQLProject from VS2005

Hello,
According to documentation I'm supposed to be able to deploy SQL project directly from VS2005. I don't have Either Build<project name> under Build menu, neither I have Deploy <project name> for my SQL project.
What am I doing wrong?
To deploy items in a SQL Server project to a SQL Server
1.. Build the project by selecting Build <project name> from the Build menu.
Note
Resolve all build errors prior to deploying.
2.. Select Deploy <project name> from the Build menu.
Note
If you receive a message informing you that the project cannot be deployed, then you may need to manually create the assembly on the server. This error is typically the result of referenced assemblies in your project. For more information on manually deploying your assembly, see the Create Assembly page in the "SQL Books Online."
Right-click the project in Solution Explorer. There's a deploy option there.
Most people will do it via scripts though.
HTH,
Greg
"GS" <nospam@.nowhere.com> wrote in message news:ObaPYusFGHA.3200@.tk2msftngp13.phx.gbl...
Hello,
According to documentation I'm supposed to be able to deploy SQL project directly from VS2005. I don't have Either Build<project name> under Build menu, neither I have Deploy <project name> for my SQL project.
What am I doing wrong?
To deploy items in a SQL Server project to a SQL Server
1.. Build the project by selecting Build <project name> from the Build menu.
Note
Resolve all build errors prior to deploying.
2.. Select Deploy <project name> from the Build menu.
Note
If you receive a message informing you that the project cannot be deployed, then you may need to manually create the assembly on the server. This error is typically the result of referenced assemblies in your project. For more information on manually deploying your assembly, see the Create Assembly page in the "SQL Books Online."

How to deploy SQLProject from VS2005

Hello,
According to documentation I'm supposed to be able to deploy SQL project directly from VS2005. I don't have Either Build<project name> under Build menu, neither I have Deploy <project name> for my SQL project.
What am I doing wrong?
To deploy items in a SQL Server project to a SQL Server
1.. Build the project by selecting Build <project name> from the Build menu.
Note
Resolve all build errors prior to deploying.
2.. Select Deploy <project name> from the Build menu.
Note
If you receive a message informing you that the project cannot be deployed, then you may need to manually create the assembly on the server. This error is typically the result of referenced assemblies in your project. For more information on manually deploying your assembly, see the Create Assembly page in the "SQL Books Online."
Right-click the project in Solution Explorer. There's a deploy option there.
Most people will do it via scripts though.
HTH,
Greg
"GS" <nospam@.nowhere.com> wrote in message news:ObaPYusFGHA.3200@.tk2msftngp13.phx.gbl...
Hello,
According to documentation I'm supposed to be able to deploy SQL project directly from VS2005. I don't have Either Build<project name> under Build menu, neither I have Deploy <project name> for my SQL project.
What am I doing wrong?
To deploy items in a SQL Server project to a SQL Server
1.. Build the project by selecting Build <project name> from the Build menu.
Note
Resolve all build errors prior to deploying.
2.. Select Deploy <project name> from the Build menu.
Note
If you receive a message informing you that the project cannot be deployed, then you may need to manually create the assembly on the server. This error is typically the result of referenced assemblies in your project. For more information on manually deploying your assembly, see the Create Assembly page in the "SQL Books Online."

How to deploy SQLProject from VS2005

Hello,
According to documentation I'm supposed to be able to deploy SQL project dir
ectly from VS2005. I don't have Either Build<project name> under Build menu,
neither I have Deploy <project name> for my SQL project.
What am I doing wrong?
To deploy items in a SQL Server project to a SQL Server
1.. Build the project by selecting Build <project name> from the Build menu.
Note
Resolve all build errors prior to deploying.
2.. Select Deploy <project name> from the Build menu.
Note
If you receive a message informing you that the project cannot be deployed,
then you may need to manually create the assembly on the server. This error
is typically the result of referenced assemblies in your project. For more i
nformation on manually deploying your assembly, see the Create Assembly page
in the "SQL Books Online."Right-click the project in Solution Explorer. There's a deploy option there.
Most people will do it via scripts though.
HTH,
Greg
"GS" <nospam@.nowhere.com> wrote in message news:ObaPYusFGHA.3200@.tk2msftngp1
3.phx.gbl...
Hello,
According to documentation I'm supposed to be able to deploy SQL project dir
ectly from VS2005. I don't have Either Build<project name> under Build menu,
neither I have Deploy <project name> for my SQL project.
What am I doing wrong?
To deploy items in a SQL Server project to a SQL Server
1.. Build the project by selecting Build <project name> from the Build menu.
Note
Resolve all build errors prior to deploying.
2.. Select Deploy <project name> from the Build menu.
Note
If you receive a message informing you that the project cannot be deployed,
then you may need to manually create the assembly on the server. This error
is typically the result of referenced assemblies in your project. For more i
nformation on manually deploying your assembly, see the Create Assembly page
in the "SQL Books Online."

How to deploy SQLProject from VS2005

This is a multi-part message in MIME format.
--=_NextPart_000_00A6_01C61699.4C6A9AA0
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
Hello,
According to documentation I'm supposed to be able to deploy SQL project = directly from VS2005. I don't have Either Build<project name> under = Build menu, neither I have Deploy <project name> for my SQL project.
What am I doing wrong?
To deploy items in a SQL Server project to a SQL Server
1.. Build the project by selecting Build <project name> from the Build = menu.
Note Resolve all build errors prior to deploying.

2.. Select Deploy <project name> from the Build menu.
Note If you receive a message informing you that the project cannot = be deployed, then you may need to manually create the assembly on the = server. This error is typically the result of referenced assemblies in = your project. For more information on manually deploying your assembly, = see the Create Assembly page in the "SQL Books Online."

--=_NextPart_000_00A6_01C61699.4C6A9AA0
Content-Type: text/html;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hello,

According to documentation I'm supposed = to be able to deploy SQL project directly from VS2005. I don't have Either = Build under Build menu, neither I have Deploy = for my SQL project.
What am I doing wrong?



To deploy items in a SQL Server project to a SQL = Server
Build the project by selecting Build from the Build menu.
Note
Resolve all build errors prior to deploying.
Select Deploy from the Build menu.
Note
If you receive a message informing you that the project = cannot be deployed, then you may need to manually create the assembly on = the server. This error is typically the result of referenced = assemblies in your project. For more information on manually deploying your = assembly, see the Create Assembly page in the "SQL Books = Online."=
--=_NextPart_000_00A6_01C61699.4C6A9AA0--This is a multi-part message in MIME format.
--=_NextPart_000_0042_01C617C5.60008200
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
Right-click the project in Solution Explorer. There's a deploy option =there.
Most people will do it via scripts though.
HTH,
Greg
"GS" <nospam@.nowhere.com> wrote in message =news:ObaPYusFGHA.3200@.tk2msftngp13.phx.gbl...
Hello,
According to documentation I'm supposed to be able to deploy SQL =project directly from VS2005. I don't have Either Build<project name> =under Build menu, neither I have Deploy <project name> for my SQL =project.
What am I doing wrong?
To deploy items in a SQL Server project to a SQL Server
1.. Build the project by selecting Build <project name> from the =Build menu.
Note Resolve all build errors prior to deploying.

2.. Select Deploy <project name> from the Build menu.
Note If you receive a message informing you that the project cannot =be deployed, then you may need to manually create the assembly on the =server. This error is typically the result of referenced assemblies in =your project. For more information on manually deploying your assembly, =see the Create Assembly page in the "SQL Books Online."
--=_NextPart_000_0042_01C617C5.60008200
Content-Type: text/html;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML XMLNS:MSHelp =3D "<HEAD>">http://msdn.microsoft.com/mshelp"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dkoi8-r">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Right-click the project in Solution =Explorer. There's a deploy option there.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Most people will do it via scripts though.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>HTH,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Greg</FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"GS" <<A =href=3D"mailto:nospam@.nowhere.com">nospam@.nowhere.com</A>> wrote in message <A =href=3D"news:ObaPYusFGHA.3200@.tk2msftngp13.phx.gbl">news:ObaPYusFGHA.3200=@.tk2msftngp13.phx.gbl</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Hello,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>According to documentation I'm =supposed to be able to deploy SQL project directly from VS2005. I don't have Either Build<project name> under Build menu, neither I have Deploy =<project name> for my SQL project.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>What am I doing wrong?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV>
<H1 class=3Dheading>To deploy items in a SQL Server project to a SQL =Server</H1>
<DIV class=3Dsection id=3DprocedureSection0>
<OL>
<LI>
<P>Build the project by selecting <B>Build <</B><I>project name</I><B>></B> from the <B>Build</B> menu.</P>
<DIV class=3Dalert>
<TABLE cellSpacing=3D0 cellPadding=3D0 width=3D"100%">
<TBODY>
<TR>
<TH align=3Dleft><IMG class=3Dnote alt=3DNote =src=3D"ms-help://MS.VSCC.v80/MS.MSDN.v80/MS.VisualStudio.v80.en/dv_raddat=a/local/note.gif"></IMG>Note </TH></TR>
<TR>
<TD>
<P>Resolve all build errors prior to deploying.</P></TD></TR></TBODY></TABLE></DIV>
<LI>
<P>Select <B>Deploy <</B><I>project name</I><B>></B> from the <B>Build</B> menu.</P>
<DIV class=3Dalert>
<TABLE cellSpacing=3D0 cellPadding=3D0 width=3D"100%">
<TBODY>
<TR>
<TH align=3Dleft><IMG class=3Dnote alt=3DNote =src=3D"ms-help://MS.VSCC.v80/MS.MSDN.v80/MS.VisualStudio.v80.en/dv_raddat=a/local/note.gif"></IMG>Note </TH></TR>
<TR>
<TD>
<P>If you receive a message informing you that the project =cannot be deployed, then you may need to manually create the assembly on =the server. This error is typically the result of referenced =assemblies in your project. For more information on manually deploying your assembly, see the <MSHelp:link tabIndex=3D0 keywords=3D"d8d1d245-c2c3-4325-be52-4fc1122c2079">Create Assembly</MSHelp:link> page in the "SQL Books =Online."</P></TD></TR></TBODY></TABLE></DIV></LI></OL></DIV></DIV></BLOCK=QUOTE></BODY></HTML>
--=_NextPart_000_0042_01C617C5.60008200--

How to deploy report from QA to PROD without changing data source

Hi. I love the time-saving features of Reporting Services. I desing my report
in VS2005. Then deploy them to my QA server and, when that passes testing,
put it into my PROD environment. That all works very nicely.
I have defined 2 data sources, one for QA and one for PROD. What gets to me
is that after deploying to QA I have to go into Report Manager and select the
QA data source for each of my reports. Then, once deployed to PROD I have to
do the same. This becomes a major headache when I have to make many small
changes to a report and repeat the process each time.
Is there a way to specify an alias of some form that can point to my
development server data source when on my machine, and to the appropriate
databases when on QA and PROD?
Thanks.It's not exactly clear but do you have 2 shared datasources? If so why? If
you have a shared datasource on your QA server and one on your PROD server
with the same name and location (and the same as in your project) then you
wouldn't have to do this. When reports are deployed to qa/prod they would
just work. A shared datasource seems to be exactly what you want but from
the sound of it you are already using one?
--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Mike Kelly" <MikeKelly@.community.nospam> wrote in message
news:14B8552A-AFB7-42C9-AB9B-9F70A8D44763@.microsoft.com...
> Hi. I love the time-saving features of Reporting Services. I desing my
> report
> in VS2005. Then deploy them to my QA server and, when that passes testing,
> put it into my PROD environment. That all works very nicely.
> I have defined 2 data sources, one for QA and one for PROD. What gets to
> me
> is that after deploying to QA I have to go into Report Manager and select
> the
> QA data source for each of my reports. Then, once deployed to PROD I have
> to
> do the same. This becomes a major headache when I have to make many small
> changes to a report and repeat the process each time.
> Is there a way to specify an alias of some form that can point to my
> development server data source when on my machine, and to the appropriate
> databases when on QA and PROD?
> Thanks.|||We do what Jasper is suggesting.
We create a data source (maybe called Prod) in the project. The first time
we deploy, we go into report manager and change the connection information to
whatever it needs to be. Since redeployment does NOT change the connection (
unless you change the config), everything works fine.
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"Mike Kelly" wrote:
> Hi. I love the time-saving features of Reporting Services. I desing my report
> in VS2005. Then deploy them to my QA server and, when that passes testing,
> put it into my PROD environment. That all works very nicely.
> I have defined 2 data sources, one for QA and one for PROD. What gets to me
> is that after deploying to QA I have to go into Report Manager and select the
> QA data source for each of my reports. Then, once deployed to PROD I have to
> do the same. This becomes a major headache when I have to make many small
> changes to a report and repeat the process each time.
> Is there a way to specify an alias of some form that can point to my
> development server data source when on my machine, and to the appropriate
> databases when on QA and PROD?
> Thanks.|||Thanks Jasper and Wayne.
I am using shared data sources, but incorrectly. I was deploying them each
time. But was blind as to their inteded use. The word "Shared" threw me off
course. Now I see. I'll replace the two I was using (one for test and one for
prod) with a single one (since I only have a single database) and change the
definition for that one depeding on the environment it is running in. So
simple, once you get it!
"Wayne Snyder" wrote:
> We do what Jasper is suggesting.
> We create a data source (maybe called Prod) in the project. The first time
> we deploy, we go into report manager and change the connection information to
> whatever it needs to be. Since redeployment does NOT change the connection (
> unless you change the config), everything works fine.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> I support the Professional Association for SQL Server ( PASS) and it''s
> community of SQL Professionals.
>
> "Mike Kelly" wrote:
> > Hi. I love the time-saving features of Reporting Services. I desing my report
> > in VS2005. Then deploy them to my QA server and, when that passes testing,
> > put it into my PROD environment. That all works very nicely.
> >
> > I have defined 2 data sources, one for QA and one for PROD. What gets to me
> > is that after deploying to QA I have to go into Report Manager and select the
> > QA data source for each of my reports. Then, once deployed to PROD I have to
> > do the same. This becomes a major headache when I have to make many small
> > changes to a report and repeat the process each time.
> >
> > Is there a way to specify an alias of some form that can point to my
> > development server data source when on my machine, and to the appropriate
> > databases when on QA and PROD?
> >
> > Thanks.