Friday, March 23, 2012
No comments allowed where creating a view?
comments. It seems that whenever I save the view, the comments are
stripped out. I find this rather annoying. Don't suppose there is
anyway around this?
Thanks,
MarcusRight views don't allow comments, I don't think there is a work around for
that.
But in 2005, you can add extended property to the view, and store all the
documentation for the view in that property. Hopefully that gives you some
ideas.
Thanks!
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Marcus" wrote:
> I have a fairly complex view that I would like to annotate with some
> comments. It seems that whenever I save the view, the comments are
> stripped out. I find this rather annoying. Don't suppose there is
> anyway around this?
> Thanks,
> Marcus
>|||Thanks, Mohit. I reposted this thread as I misspelled the title (tried
to delete the post but guess it didn't work). Apparently comments are
allowed. See Dan Guzman's response to my repost.
Marcus
On Jul 5, 10:42 am, Mohit K. Gupta <mohitkgu...@.msn.com> wrote:[vbcol=seagreen]
> Right views don't allow comments, I don't think there is a work around for
> that.
> But in 2005, you can add extended property to the view, and store all the
> documentation for the view in that property. Hopefully that gives you som
e
> ideas.
> Thanks!
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Marcus" wrote:
>
No comments allowed where creating a view?
comments. It seems that whenever I save the view, the comments are
stripped out. I find this rather annoying. Don't suppose there is
anyway around this?
Thanks,
MarcusRight views don't allow comments, I don't think there is a work around for
that.
But in 2005, you can add extended property to the view, and store all the
documentation for the view in that property. Hopefully that gives you some
ideas.
Thanks!
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Marcus" wrote:
> I have a fairly complex view that I would like to annotate with some
> comments. It seems that whenever I save the view, the comments are
> stripped out. I find this rather annoying. Don't suppose there is
> anyway around this?
> Thanks,
> Marcus
>|||Thanks, Mohit. I reposted this thread as I misspelled the title (tried
to delete the post but guess it didn't work). Apparently comments are
allowed. See Dan Guzman's response to my repost.
Marcus
On Jul 5, 10:42 am, Mohit K. Gupta <mohitkgu...@.msn.com> wrote:
> Right views don't allow comments, I don't think there is a work around for
> that.
> But in 2005, you can add extended property to the view, and store all the
> documentation for the view in that property. Hopefully that gives you some
> ideas.
> Thanks!
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Marcus" wrote:
> > I have a fairly complex view that I would like to annotate with some
> > comments. It seems that whenever I save the view, the comments are
> > stripped out. I find this rather annoying. Don't suppose there is
> > anyway around this?
> > Thanks,
> > Marcus
No comments allowed where creating a view?
comments. It seems that whenever I save the view, the comments are
stripped out. I find this rather annoying. Don't suppose there is
anyway around this?
Thanks,
Marcus
Right views don't allow comments, I don't think there is a work around for
that.
But in 2005, you can add extended property to the view, and store all the
documentation for the view in that property. Hopefully that gives you some
ideas.
Thanks!
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Marcus" wrote:
> I have a fairly complex view that I would like to annotate with some
> comments. It seems that whenever I save the view, the comments are
> stripped out. I find this rather annoying. Don't suppose there is
> anyway around this?
> Thanks,
> Marcus
>
|||Thanks, Mohit. I reposted this thread as I misspelled the title (tried
to delete the post but guess it didn't work). Apparently comments are
allowed. See Dan Guzman's response to my repost.
Marcus
On Jul 5, 10:42 am, Mohit K. Gupta <mohitkgu...@.msn.com> wrote:[vbcol=seagreen]
> Right views don't allow comments, I don't think there is a work around for
> that.
> But in 2005, you can add extended property to the view, and store all the
> documentation for the view in that property. Hopefully that gives you some
> ideas.
> Thanks!
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Marcus" wrote:
No comments allowed when creating a View?
comments. It seems that whenever I save the view, the comments are
stripped out. I find this rather annoying. Don't suppose there is
anyway around this?
Thanks,
Marcus
I assume you are using a designer to create the view? Instead, create the
view directly using a Query Analyzer or SQL Serve Management Studio query
window.
Hope this helps.
Dan Guzman
SQL Server MVP
"Marcus" <holysmokes99@.hotmail.com> wrote in message
news:1183656714.354511.114570@.g37g2000prf.googlegr oups.com...
>I have a fairly complex view that I would like to annotate with some
> comments. It seems that whenever I save the view, the comments are
> stripped out. I find this rather annoying. Don't suppose there is
> anyway around this?
> Thanks,
> Marcus
>
|||On Jul 5, 10:37 am, "Dan Guzman" <guzma...@.nospam-
online.sbcglobal.net> wrote:
> I assume you are using a designer to create the view? Instead, create the
> view directly using a Query Analyzer or SQL Serve Management Studio query
> window.
> --
> Hope this helps.
Thanks, Dan. I see now. If I right click on the view in SQL Server
Management Studio and then select "modify", it brings up the designer
which strips out the comments. However, if I right click on the view
and select "script view as-->alter to--> new query editor window"
then the comments are there. Don't really care for these extra steps,
but can live with that.
Cheers,
Marcus
[vbcol=seagreen]
> Dan Guzman
> SQL Server MVP
> "Marcus" <holysmoke...@.hotmail.com> wrote in message
> news:1183656714.354511.114570@.g37g2000prf.googlegr oups.com...
>
sql
No comments allowed when creating a View?
comments. It seems that whenever I save the view, the comments are
stripped out. I find this rather annoying. Don't suppose there is
anyway around this?
Thanks,
MarcusI assume you are using a designer to create the view? Instead, create the
view directly using a Query Analyzer or SQL Serve Management Studio query
window.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Marcus" <holysmokes99@.hotmail.com> wrote in message
news:1183656714.354511.114570@.g37g2000prf.googlegroups.com...
>I have a fairly complex view that I would like to annotate with some
> comments. It seems that whenever I save the view, the comments are
> stripped out. I find this rather annoying. Don't suppose there is
> anyway around this?
> Thanks,
> Marcus
>|||On Jul 5, 10:37 am, "Dan Guzman" <guzma...@.nospam-
online.sbcglobal.net> wrote:
> I assume you are using a designer to create the view? Instead, create the
> view directly using a Query Analyzer or SQL Serve Management Studio query
> window.
> --
> Hope this helps.
Thanks, Dan. I see now. If I right click on the view in SQL Server
Management Studio and then select "modify", it brings up the designer
which strips out the comments. However, if I right click on the view
and select "script view as-->alter to--> new query editor window"
then the comments are there. Don't really care for these extra steps,
but can live with that.
Cheers,
Marcus
> Dan Guzman
> SQL Server MVP
> "Marcus" <holysmoke...@.hotmail.com> wrote in message
> news:1183656714.354511.114570@.g37g2000prf.googlegroups.com...
> >I have a fairly complex view that I would like to annotate with some
> > comments. It seems that whenever I save the view, the comments are
> > stripped out. I find this rather annoying. Don't suppose there is
> > anyway around this?
> > Thanks,
> > Marcus
No comments allowed when creating a View?
comments. It seems that whenever I save the view, the comments are
stripped out. I find this rather annoying. Don't suppose there is
anyway around this?
Thanks,
MarcusI assume you are using a designer to create the view? Instead, create the
view directly using a Query Analyzer or SQL Serve Management Studio query
window.
Hope this helps.
Dan Guzman
SQL Server MVP
"Marcus" <holysmokes99@.hotmail.com> wrote in message
news:1183656714.354511.114570@.g37g2000prf.googlegroups.com...
>I have a fairly complex view that I would like to annotate with some
> comments. It seems that whenever I save the view, the comments are
> stripped out. I find this rather annoying. Don't suppose there is
> anyway around this?
> Thanks,
> Marcus
>|||On Jul 5, 10:37 am, "Dan Guzman" <guzma...@.nospam-
online.sbcglobal.net> wrote:
> I assume you are using a designer to create the view? Instead, create the
> view directly using a Query Analyzer or SQL Serve Management Studio query
> window.
> --
> Hope this helps.
Thanks, Dan. I see now. If I right click on the view in SQL Server
Management Studio and then select "modify", it brings up the designer
which strips out the comments. However, if I right click on the view
and select "script view as-->alter to--> new query editor window"
then the comments are there. Don't really care for these extra steps,
but can live with that.
Cheers,
Marcus
[vbcol=seagreen]
> Dan Guzman
> SQL Server MVP
> "Marcus" <holysmoke...@.hotmail.com> wrote in message
> news:1183656714.354511.114570@.g37g2000prf.googlegroups.com...
>
>
Wednesday, March 21, 2012
No ADO type command for Data Flow?
I'm probably not looking in the right place, but all I could find when creating a data flow task was OLE DB Commands. I was trying to utilize a dataaccesslayer piece of code that we use every where in our projects, but because it uses ADO and not OLE DB, it caused an issue between the column data types.
Is there an ADO command object available? Or are we forced to use the OLE DB command object? All I was looking to do was to Execute a SQL command. There's an object on the Control Flow level to do that, but not on the Data Flow levelnot sure why that is.
Thanks,
Jeff Tolman
E&M Electric
Its because executing a stand-alone SQL statement isn't relevant for a data-flow. As you have observed you can do that in the Execute SQL Task.
What exactly is it that you want to do? What is your SQL statement?
-Jamie
|||
You would only use the data flow task if you wanted to process many rows of data - either aggregating them to pass them to your command, or issuing the command for every row that passes.
If you have existing code, you can likely acheive that using the Script Component - but be sure your scenario is appropriate first.
Can you describe some more about what you are trying to acheive?
Donald
|||It's not necessarily a particular command. It's using ADO vs. OLE DB. Our DataAccessLayer code uses ADO, which I was able to import into the VSA scripting editor and that seemed to work just fine. However the output of the Script Component feeds records to separate SQL commands, but the only thing that I see that's available is the OLE DB Command. I know I could probably do this within the Script component, but it just seems to be more logically designed and layed out this way.
Thanks,
Jeff
|||I have a set of records coming in to a Script Component and based on the data and lookups into the destination table I'm determining if data should be deleted, inserted or updated in the destination table. It's basically a table copy routine with a little intelligence for deletes.
Jeff
|||JazzGeek wrote:
It's not necessarily a particular command. It's using ADO vs. OLE DB. Our DataAccessLayer code uses ADO, which I was able to import into the VSA scripting editor and that seemed to work just fine. However the output of the Script Component feeds records to separate SQL commands, but the only thing that I see that's available is the OLE DB Command. I know I could probably do this within the Script component, but it just seems to be more logically designed and layed out this way.
Thanks,
Jeff
Sorry, I'm really really confused. In SSIS you don't access data using the OLE DB Command component. You do it with a source adapter. There are many source adapters including one for OLE DB and one for ADO.
Are you saying that you want apply modifications using ADO rather than OLE DB?
-Jamie
|||
Hey Jamie,
I was just hoping to use our DataAccessLayer code library (which utilized ADO) to perform DB commands against our databases. I realize that with the OLE DB Command object you can execute a SQL command based on any of the input column data. Since I couldn't find an ADO Command object, I thought I'd use our DataAccessLayer library within a Script component to do it.
Thanks for the comments!
Jeff
Friday, March 9, 2012
Next Item in String
Example if the special date is March 26, 2007, I want it to use the next string item, which is April 9, 2007. I can't use +14, because the next string item isn't always +14 days.
Can anyone help me with the formula to use?
Thanks so much in advance!So you want the {Session_Starts.Special_Date} value of the next record? Use the Next function! Look in the help.