Extra Characters appended to entry

I'm encountering a strange problem in all the applications I'm working on and am totally dumbfounded as to why it's occuring:
From a standard web form I'm inserting a record using a stored procedure. (I'm writing this to a SQL 2000 db - where the column types and variables are all consistant) No matter what I do, the columns are padded with extra characters maxing out the field length (if it's nchar or nvarchar or char) after insert or update. I've tried Trim - ing the field.text values that I'm feeding to the @.variables used in my stored procedure. I've even RTRIM() - ed the @.variables within the stored procedure. No matter what I do I get extra spaces padding the end of the intended column input. Ideas anyone?
Thanks in advance.
- AbeDepending on your extra characters, trimmimg won't solve your problem if they are not whitespaces.
Could you supply more info and post your ASP and T-Sql code?
|||

Thanks. I'm pretty sure it's spaces because if I run a query "SELECT Education FROM tblCV WHERE (Education LIKE N'% %')" I get all records returned except the ones that I manually stripped out the trailing spaces.

privatevoid InsertCV()
{

SqlConnection conn =new SqlConnection(connectString);

SqlCommand cmd =new SqlCommand("sp_InsertCV",conn);

cmd.CommandType = CommandType.StoredProcedure;

cmd.Parameters.Add("@.AAASS_ID",SqlDbType.NVarChar,5);

cmd.Parameters.Add("@.Education",SqlDbType.NChar,700);

cmd.Parameters.Add("@.Experience",SqlDbType.NChar,700);

cmd.Parameters.Add("@.Publication",SqlDbType.NChar,700);

cmd.Parameters.Add("@.ConferencePapers",SqlDbType.NChar,700);

cmd.Parameters.Add("@.OrganizationalMembership",SqlDbType.NChar,700);

cmd.Parameters.Add("@.EnteredBy",SqlDbType.NVarChar,10);

cmd.Parameters.Add("@.UpdatedBy",SqlDbType.NVarChar,10);

cmd.Parameters["@.AAASS_ID"].Value = _AAASSID;

cmd.Parameters["@.Education"].Value =this.education.Text;

cmd.Parameters["@.Experience"].Value =this.experience.Text;

cmd.Parameters["@.Publication"].Value =this.publications.Text;

cmd.Parameters["@.ConferencePapers"].Value =this.conferencePapers.Text;

cmd.Parameters["@.OrganizationalMembership"].Value =this.organizationalMembership.Text;

cmd.Parameters["@.EnteredBy"].Value = _AAASSID;

cmd.Parameters["@.UpdatedBy"].Value = _AAASSID;

conn.Open();

cmd.ExecuteNonQuery();

cmd.Dispose();

conn.Close();

}
CREATE PROCEDURE sp_InsertCV
(
@.AAASS_ID AS nvarchar(5),
@.Education AS nchar(700),
@.Experience AS nchar(700),
@.Publication AS nchar(700),
@.ConferencePapers AS nchar(700),
@.OrganizationalMembership AS nchar(700),
@.EnteredBy AS char(10),
@.UpdatedBy AS char(10)
)

AS
INSERT INTO [AAASSSQLData].[dbo].[tblCV]
(
[AAASS_ID], [Education], [Experience], [Publication], [ConferencePapers], [OrganizationalMembership], [DateEntered], [EnteredBy],
[DateUpdated], [UpdatedBy]
)
VALUES(
@.AAASS_ID,RTRIM(@.Education),RTRIM(@.Experience),
RTRIM(@.Publication),
RTRIM(@.ConferencePapers),
RTRIM(@.OrganizationalMembership),
GetDate(),
RTRIM(@.EnteredBy),
GetDate(),
RTRIM(@.UpdatedBy)
)
GO
tblCV
3 AAASS_ID nvarchar 5 0
0 Education nchar 700 1
0 Experience nchar 700 1
0 Publication nchar 700 1
0 ConferencePapers nchar 700 1
0 OrganizationalMembership nchar 700 1
0 DateEntered datetime 8 1
0 EnteredBy char 10 1
0 DateUpdated datetime 8 1
0 UpdatedBy char 10 1
Column contents: "SUNY Binghamton, B.A., Psychology, 1982
Pace U., MBA, Management Information Systems, 1986 "
Thank you for taking a look at this.
- Abe

|||Use varchar or nvarchar fields and they won't be padded. Char and nchar datatypes pad the data with spaces out to the field length.|||Thanks so much for the feedback. I'll give that a try.
Best,
- AbeR

extending SSIS Container?

Has anyone investigated extending any of the SSIS Container classes?

I have been looking into it because we'd like to add a set of standard logging calls on events, standard startup procedures, etc. on any package that we execute.

I've been looking into the Sequence Container, For-Each, etc. They are all sealed classes. I'm not sure why MS has sealed them.

We're currently thinking of implementing our own version of the Sequence Container -- we'd really like to be able to extend the functionality of a standard container class, but we don't want to have to implement the actual container class itself.

Any insight appreciated.

Nope, it is not possible to extend these classes.

The managed classes in Dts.Runtime namespace allow you to manipulate the built-in containers in a package. They are sealed because they are not actually used at execution time, so subclassing them would not be useful.|||

Thanks Michael.

I'm not sure I understand how the containers are not used at execution time -- something like a For-Each loop container would be, wouldn't it?

I think what I'd really like to do is extend the SSIS Package class instead. But that is sealed as well. Perhaps we'll wind up using something like a decorator for the Package class.

|||When package schedules the tasks, SSIS uses its internal representation for For-Each container, but not the actual .NET class. I.e. even if you could subclass the container and override Execute() method, SSIS would not call your method.

We've received similar feedback several times. For now, you can use Execute Package task to achieve some of the functionality, but we know it does not provide all the functionality that might be needed.|||

jhikel wrote:

Has anyone investigated extending any of the SSIS Container classes?

I have been looking into it because we'd like to add a set of standard logging calls on events, standard startup procedures, etc. on any package that we execute.

I've been looking into the Sequence Container, For-Each, etc. They are all sealed classes. I'm not sure why MS has sealed them.

We're currently thinking of implementing our own version of the Sequence Container -- we'd really like to be able to extend the functionality of a standard container class, but we don't want to have to implement the actual container class itself.

Any insight appreciated.

frequently used logging configurations can be created as templates.sql

Extending CDOSYS Mail to include Query Attachments?

Hi,

I was wondering if anyone has extended the standard CDOSYS Mail Stored Procedure (SP) to allow it to send the results of a query as an attachment?

I have set up a SP for CDOSYS Mail as outlined in the following link:
http://support.microsoft.com/default.aspx?id=kb;de;312839&sd=tech

Currently I am using the old SQL Mail (xp_SendMail). But due to the problems with losing the MAPI connection and other limitations, I have been forced to find another solution. Using SQL Mail, I was able to add a query parameter and attach the results of the query to the email. I need to have the same functionality in CDOSYS Mail

Thanks,
KimHi,

I was wondering if anyone has extended the standard CDOSYS Mail Stored Procedure (SP) to allow it to send the results of a query as an attachment?

I have set up a SP for CDOSYS Mail as outlined in the following link:
http://support.microsoft.com/default.aspx?id=kb;de;312839&sd=tech

Currently I am using the old SQL Mail (xp_SendMail). But due to the problems with losing the MAPI connection and other limitations, I have been forced to find another solution. Using SQL Mail, I was able to add a query parameter and attach the results of the query to the email. I need to have the same functionality in CDOSYS Mail

Thanks,
Kim

Jasper has written an sp for it check it out here:
http://www.sqlteam.com/Forums/topic.asp?TOPIC_ID=20649|||Sorry, I don't think I explained myself very well!

I currently use xp_sendmail and pass a query as a parameter and attach the results of this query to an email. I would like to know if anyone has extended CDOSYS Mail to have the same functionality? Example of how I use this is in xp_sendmail @.query parameter would be a query which returns the total number of records on an import table and xp_sendmail sends the results in an email attachement OR sends the results as part of the body of the email.

Extract of the xp_sendmail Syntax:
xp_sendmail {[@.recipients =] 'recipients [;...n]'}
[,[@.query =] 'query']

[,[@.attach_results =] 'attach_value']|||I had the same problem and found a workaround using osql to write the results of the query to a file. I then include the file as an attachment and delete it from the server. Seems to work well even within a loop.

I used this to work from.
http://www.sqlteam.com/item.asp?ItemID=4722

And came up with this command line that seems to create a file with the same format as the attach query results did with sendMail:

SET @.bcpCommand = "osql -h-1 -w800 /U usrId /P pw /d " + @.dbName + " /Q ""myprocname parm1, parm2"" -o "
SET @.bcpCommand = @.bcpCommand + @.FileName

EXEC master..xp_cmdshell @.bcpCommand

Then just pass @.fileName as the attachment to the cdosys mail procedure. I then use xp_cmdshell to delete the file from the server.

Extended stored procedure, performance?

Hi everybody,
I should begin to write a DLL library for Sql2000 server.
The functions I like to implement are mathematical functions, like standard
deviation, and similar, nothing really complex. Often I have to use more
then one standard deviation inside the sama function, using subset of a
record set.
Of course I can use sql2000, that implemets standard deviation and basic
mathematical function, so the question is: is it opportune to write a DDL to
improve performance, or is it worse, or just the same?
thanks a lot for any kindly advice
cesare"Cesare" <cvairetti@.mcgestioni.it> wrote in message
news:et2MIqvjGHA.4304@.TK2MSFTNGP03.phx.gbl...
> Hi everybody,
> I should begin to write a DLL library for Sql2000 server.
> The functions I like to implement are mathematical functions, like
> standard
> deviation, and similar, nothing really complex. Often I have to use more
> then one standard deviation inside the sama function, using subset of a
> record set.
> Of course I can use sql2000, that implemets standard deviation and basic
> mathematical function, so the question is: is it opportune to write a DDL
> to
> improve performance, or is it worse, or just the same?
>
Extended stored procedures are so dangerous to the stability of the database
server that they should be used very, very carefully.
In SQL 2005 CLR integration provides a safe way to extent the SQL engine
with custom calculations.
David

Extend CSV Rendering

Is there anyway to extend the existing CSV rending to change deviceinfo
settings that would be used when export is selected from the standard
ReportServer interface.
Example would be to have TXT rendering capability that used the CSV
rendering components, but changed the deviceinfo settings so that
Extension=txt, FieldDelimiter=|. I want to use the parameter selection
capability, and then allow the user to export to this TXT format instead of
CSV.
Logically I would think that you could added some DeviceInfo settings to the
config file in the Report Service directory where Render is defined. But I
am unable to find any sort of documentation.
Also the BOL talks about extending existing rendering formats, as opposed to
create custom rendering extensions. I have yet to find out how it is
possible to extend the CSV rendering extension to accomplish this. I really
want to be able to leverage the existing CSV rendering extension, to modify
a couple of settings.
I know that this can be done via URL and Hidden values in the calling web
page that shells the Report Services window. But when you click the Export
functionality and pick CSV none of the CSV deviceinfo settings are carried
forward to the Export window that is opened before prompting to Save or Open
the file.
Thanks,
MikeUnfortunately, we do not support setting the device info through report
manager.
Regarding the BOL reference to extending rather than writing your own: I
think this might just be a case of terminology confusion. You cannot extend
a particular format. You can extend the report server by adding your own
formats. I'll see about getting the wording changed.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael McCallum" <mmccallum@.honovi.net> wrote in message
news:%23D35dY2FFHA.3648@.TK2MSFTNGP09.phx.gbl...
> Is there anyway to extend the existing CSV rending to change deviceinfo
> settings that would be used when export is selected from the standard
> ReportServer interface.
> Example would be to have TXT rendering capability that used the CSV
> rendering components, but changed the deviceinfo settings so that
> Extension=txt, FieldDelimiter=|. I want to use the parameter selection
> capability, and then allow the user to export to this TXT format instead
> of CSV.
> Logically I would think that you could added some DeviceInfo settings to
> the config file in the Report Service directory where Render is defined.
> But I am unable to find any sort of documentation.
> Also the BOL talks about extending existing rendering formats, as opposed
> to create custom rendering extensions. I have yet to find out how it is
> possible to extend the CSV rendering extension to accomplish this. I
> really want to be able to leverage the existing CSV rendering extension,
> to modify a couple of settings.
> I know that this can be done via URL and Hidden values in the calling web
> page that shells the Report Services window. But when you click the
> Export functionality and pick CSV none of the CSV deviceinfo settings are
> carried forward to the Export window that is opened before prompting to
> Save or Open the file.
> Thanks,
> Mike
>|||Thanks for the information. Maybe this could be a wishlist type item?
Mike
"Lukasz Pawlowski [MSFT]" <lukaszp@.online.microsoft.com> wrote in message
news:eg8QrjHGFHA.2156@.TK2MSFTNGP09.phx.gbl...
> Unfortunately, we do not support setting the device info through report
> manager.
> Regarding the BOL reference to extending rather than writing your own: I
> think this might just be a case of terminology confusion. You cannot
> extend a particular format. You can extend the report server by adding
> your own formats. I'll see about getting the wording changed.
> -Lukasz
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Michael McCallum" <mmccallum@.honovi.net> wrote in message
> news:%23D35dY2FFHA.3648@.TK2MSFTNGP09.phx.gbl...
>> Is there anyway to extend the existing CSV rending to change deviceinfo
>> settings that would be used when export is selected from the standard
>> ReportServer interface.
>> Example would be to have TXT rendering capability that used the CSV
>> rendering components, but changed the deviceinfo settings so that
>> Extension=txt, FieldDelimiter=|. I want to use the parameter selection
>> capability, and then allow the user to export to this TXT format instead
>> of CSV.
>> Logically I would think that you could added some DeviceInfo settings to
>> the config file in the Report Service directory where Render is defined.
>> But I am unable to find any sort of documentation.
>> Also the BOL talks about extending existing rendering formats, as opposed
>> to create custom rendering extensions. I have yet to find out how it is
>> possible to extend the CSV rendering extension to accomplish this. I
>> really want to be able to leverage the existing CSV rendering extension,
>> to modify a couple of settings.
>> I know that this can be done via URL and Hidden values in the calling web
>> page that shells the Report Services window. But when you click the
>> Export functionality and pick CSV none of the CSV deviceinfo settings are
>> carried forward to the Export window that is opened before prompting to
>> Save or Open the file.
>> Thanks,
>> Mike
>|||Yes, we plan (at some point :-)) to expose UI around device info settings.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael McCallum" <mmccallum@.honovi.com> wrote in message
news:%23oBG%234OGFHA.1836@.tk2msftngp13.phx.gbl...
> Thanks for the information. Maybe this could be a wishlist type item?
> Mike
> "Lukasz Pawlowski [MSFT]" <lukaszp@.online.microsoft.com> wrote in message
> news:eg8QrjHGFHA.2156@.TK2MSFTNGP09.phx.gbl...
>> Unfortunately, we do not support setting the device info through report
>> manager.
>> Regarding the BOL reference to extending rather than writing your own: I
>> think this might just be a case of terminology confusion. You cannot
>> extend a particular format. You can extend the report server by adding
>> your own formats. I'll see about getting the wording changed.
>> -Lukasz
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Michael McCallum" <mmccallum@.honovi.net> wrote in message
>> news:%23D35dY2FFHA.3648@.TK2MSFTNGP09.phx.gbl...
>> Is there anyway to extend the existing CSV rending to change deviceinfo
>> settings that would be used when export is selected from the standard
>> ReportServer interface.
>> Example would be to have TXT rendering capability that used the CSV
>> rendering components, but changed the deviceinfo settings so that
>> Extension=txt, FieldDelimiter=|. I want to use the parameter selection
>> capability, and then allow the user to export to this TXT format instead
>> of CSV.
>> Logically I would think that you could added some DeviceInfo settings to
>> the config file in the Report Service directory where Render is defined.
>> But I am unable to find any sort of documentation.
>> Also the BOL talks about extending existing rendering formats, as
>> opposed to create custom rendering extensions. I have yet to find out
>> how it is possible to extend the CSV rendering extension to accomplish
>> this. I really want to be able to leverage the existing CSV rendering
>> extension, to modify a couple of settings.
>> I know that this can be done via URL and Hidden values in the calling
>> web page that shells the Report Services window. But when you click the
>> Export functionality and pick CSV none of the CSV deviceinfo settings
>> are carried forward to the Export window that is opened before prompting
>> to Save or Open the file.
>> Thanks,
>> Mike
>>
>|||Lukasz, Is there any complexity in rendering dynamically generated matrix
total columns in CSV format? I have been having this problem that when I
export my reports to CSV, if a matrix in the report has column groupings as
well as dynamic total columns, these total columns don't generate in CSV
version. I was thinking of writing my own CSV renderer but then I thought
there's probably a complexity into that, otherwise the Microsoft CSV renderer
would do it. Is that right? Or do you think CSV rendere just wasn't intended
to render dynamic columns in a matrix?
"Lukasz Pawlowski [MSFT]" wrote:
> Yes, we plan (at some point :-)) to expose UI around device info settings.
> -Lukasz
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Michael McCallum" <mmccallum@.honovi.com> wrote in message
> news:%23oBG%234OGFHA.1836@.tk2msftngp13.phx.gbl...
> > Thanks for the information. Maybe this could be a wishlist type item?
> > Mike
> >
> > "Lukasz Pawlowski [MSFT]" <lukaszp@.online.microsoft.com> wrote in message
> > news:eg8QrjHGFHA.2156@.TK2MSFTNGP09.phx.gbl...
> >> Unfortunately, we do not support setting the device info through report
> >> manager.
> >>
> >> Regarding the BOL reference to extending rather than writing your own: I
> >> think this might just be a case of terminology confusion. You cannot
> >> extend a particular format. You can extend the report server by adding
> >> your own formats. I'll see about getting the wording changed.
> >>
> >> -Lukasz
> >>
> >>
> >> --
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >>
> >> "Michael McCallum" <mmccallum@.honovi.net> wrote in message
> >> news:%23D35dY2FFHA.3648@.TK2MSFTNGP09.phx.gbl...
> >> Is there anyway to extend the existing CSV rending to change deviceinfo
> >> settings that would be used when export is selected from the standard
> >> ReportServer interface.
> >>
> >> Example would be to have TXT rendering capability that used the CSV
> >> rendering components, but changed the deviceinfo settings so that
> >> Extension=txt, FieldDelimiter=|. I want to use the parameter selection
> >> capability, and then allow the user to export to this TXT format instead
> >> of CSV.
> >>
> >> Logically I would think that you could added some DeviceInfo settings to
> >> the config file in the Report Service directory where Render is defined.
> >> But I am unable to find any sort of documentation.
> >>
> >> Also the BOL talks about extending existing rendering formats, as
> >> opposed to create custom rendering extensions. I have yet to find out
> >> how it is possible to extend the CSV rendering extension to accomplish
> >> this. I really want to be able to leverage the existing CSV rendering
> >> extension, to modify a couple of settings.
> >>
> >> I know that this can be done via URL and Hidden values in the calling
> >> web page that shells the Report Services window. But when you click the
> >> Export functionality and pick CSV none of the CSV deviceinfo settings
> >> are carried forward to the Export window that is opened before prompting
> >> to Save or Open the file.
> >>
> >> Thanks,
> >> Mike
> >>
> >>
> >>
> >
> >
>
>

Express Versus Standard Footprint

Is there a current estimate of the footprint of SQL Server Express 2005 versus the footprint of SQL Server Standard 2005? Is the size difference significant?

Are you talking in general or for Reporting Services? There is not a significant difference in the core relational database. The things that aren't included are additional services, documentation and tools. You can download Express and see what is included.

Express to Standard upgrade

I have SQL Server 2005 Express that was installed with SharePoint Server 2007. I'm trying to upgrade it to SQL Server 2005 Standard edition and it gives this "Edition Change Check (Warning)" message:

"To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter."

I tried "setup skuupgrade=1" from the command prompt, but it's giving me the same message.

Can someone tell me how to correctly make the upgrade?

Sam

The paramater is case sensitive you need to use:

setup.exe SKUUPGRADE=1

|||Thank you. That did it!
|||

Hi isunshine,

I am also trying to upgrade my SharePoint 2007's SQL Express (default installation) to SQL Standard 2005. Since I have lot of contents on the SharePoint 200, I just thought to reconfirm with you. (Since you did the same thing). Did you have problems with SharePoint after the upgrade to SQL Standard 2005? Was you SQL Server express named server?

Thank you,

KG

|||No, i didn't have a problem after the upgrade. But mine didn't have lots of content so it could be a different story... i'm not quite sure what you mean by "named server".|||

When you install SQL Server you could select whether you want it to be default server or name server (name instance). I have a default instance of SQL Server 2005 installation as such we installed the name server (or name instance of the SQL Sever)

Thank you

KG

Express to Standard upgrade

I have SQL Server 2005 Express that was installed with SharePoint Server 2007. I'm trying to upgrade it to SQL Server 2005 Standard edition and it gives this "Edition Change Check (Warning)" message:

"To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter."

I tried "setup skuupgrade=1" from the command prompt, but it's giving me the same message.

Can someone tell me how to correctly make the upgrade?

Sam

The paramater is case sensitive you need to use:

setup.exe SKUUPGRADE=1

|||Thank you. That did it!|||

Hi isunshine,

I am also trying to upgrade my SharePoint 2007's SQL Express (default installation) to SQL Standard 2005. Since I have lot of contents on the SharePoint 200, I just thought to reconfirm with you. (Since you did the same thing). Did you have problems with SharePoint after the upgrade to SQL Standard 2005? Was you SQL Server express named server?

Thank you,

KG

|||No, i didn't have a problem after the upgrade. But mine didn't have lots of content so it could be a different story... i'm not quite sure what you mean by "named server".|||

When you install SQL Server you could select whether you want it to be default server or name server (name instance). I have a default instance of SQL Server 2005 installation as such we installed the name server (or name instance of the SQL Sever)

Thank you

KG

Express to Standard

If I have sql 2005 express installed with a data in it, how can i upgrade
that to SQL standard 2005 without bringing the database down?
Thanks
You can't. The upgrade will replace the executable files so they have to be
closed before they can be overwritten. You can do the upgrade while SQL
Express is running but then it won't take effect until you reboot the
machine because the files will be in use.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Chanaka" <Chanaka@.discussions.microsoft.com> wrote in message
news:EF8EDB2B-A5BF-4F05-B454-C62970AFE7B6@.microsoft.com...
> If I have sql 2005 express installed with a data in it, how can i upgrade
> that to SQL standard 2005 without bringing the database down?
> Thanks
|||Thanks Roger!
"Roger Wolter[MSFT]" wrote:

> You can't. The upgrade will replace the executable files so they have to be
> closed before they can be overwritten. You can do the upgrade while SQL
> Express is running but then it won't take effect until you reboot the
> machine because the files will be in use.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Chanaka" <Chanaka@.discussions.microsoft.com> wrote in message
> news:EF8EDB2B-A5BF-4F05-B454-C62970AFE7B6@.microsoft.com...
>

Express and Standard

Hi All,
I received a copy of SQL Server 2005 Standard at a conference. To say
the least I am beyond blown away!!
Anyway, I went out and purchased Visual Studio 2005 Pro. When installing
it also installed SQL Server Express (I thought it would skip it since
standard was already there. I was going to uninstall express but I
wanted to make sure:
It won't screw up my Visual Studio install?
And in Add/Remove programs that is referenced by the "SQL Server Desktop
Engine". Am I right?
Thanks for your input.
Also was curious how the old timers feel about SQL becoming an object
orientated language platform? I guess in some ways it already was. I
just had never thought of it that way before.
KellyYou're about to start a holy war :)
"Also was curious how the old timers feel about SQL becoming an object
orientated language platform? I guess in some ways it already was. I
just had never thought of it that way before."
SQL is not an OOL, and I would try to avoid thinking of it like that.
SQL is a set-oriented language; data is handled en masse. That being
said, I am excited about the inclusion of the CLR in SQL Server because
it allows me to write functions to augment the data I collect and store
in my database (for example, I can write a function in the CLR to
handle conversion of my ip addresses from dotted quad to integer
format, allowing me to select greater ranges of related data).
However, I sat through one of the SQL Road Show discussions for
developers, and groaned as I heard developer after developer ask how
could store their complex business objects in SQL Server; I would hate
to be the DBA supporting that shop, because performance will suffer. I
butt heads with our OOP developers all the time because they want to
iterate through a collection and insert one row of data at a time into
our warehouse. SQL works best with sets; that's what it's designed
for.
Not sure about your installation questions, but wanted to drop my.02 in
before it got ugly :)
Stu|||Hello scorpion53061,

> Anyway, I went out and purchased Visual Studio 2005 Pro. When
> installing it also installed SQL Server Express (I thought it would
> skip it since standard was already there. I was going to uninstall
> express but I wanted to make sure:
> It won't screw up my Visual Studio install?
Nope. Uninstalling Express shouldn't mess up your VS install.

> And in Add/Remove programs that is referenced by the "SQL Server
> Desktop Engine". Am I right?
No, that's MSDE, the SQL Server 2000 version of SQL Server 2005 Express Edit
ion.
Express should be clearly labelled as Express.

> Also was curious how the old timers feel about SQL becoming an object
> orientated language platform? I guess in some ways it already was. I
> just had never thought of it that way before.
It's not, see my response to Stu.
Thank you,
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/|||Hello Stu,

> You're about to start a holy war :)
> "Also was curious how the old timers feel about SQL becoming an object
> orientated language platform? I guess in some ways it already was. I
> just had never thought of it that way before."
It's always been a platform for OOPs, just as Textfiles, sockets, RAM, etc.
Nothing to build a Jihad on. ;)

> SQL is not an OOL, and I would try to avoid thinking of it like that.
Its true that SQL, and in our space, T-SQL, is not an OOPL, and yes, its
wise to not think of it as one. But SQL Server isn't just a T-SQL processor.
The "Box Pox" (LINQ) is all about adding query processing to the OOPL. How
that will work out is yet to be seen, but it's clear that something like
it will materalize.

> SQL is a set-oriented language; data is handled en masse. That being
> said, I am excited about the inclusion of the CLR in SQL Server
> because it allows me to write functions to augment the data I collect
> and store in my database (for example, I can write a function in the
> CLR to handle conversion of my ip addresses from dotted quad to
> integer format, allowing me to select greater ranges of related data).
Exactly. SQLCLR should be used to extend the reach and depth of T-SQL as
a tool for solving data manipulation problems with high degrees of parallali
zation
and volumes of disk I/O.

> However, I sat through one of the SQL Road Show discussions for
> developers, and groaned as I heard developer after developer ask how
> could store their complex business objects in SQL Server; I would hate
> to be the DBA supporting that shop, because performance will suffer.
I'm glad somebody actually remembers my talk from the Roadshows where I was
"don't do that" for using UDTs as mapped objects. :)
Its not only raw performance that suffers, but its the total sustainability
of the application that does as well.

> I butt heads with our OOP developers all the time because they want to
> iterate through a collection and insert one row of data at a time into
> our warehouse. SQL works best with sets; that's what it's designed
> for.
Yep. Now I would argue that if developers really do want to store object
data in a database, store the serialized XML and be done with it. Provided
it has a good fixed schema. :)
Thank you,
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/

Exporting to Excel

Hi guys,
I have set up a report that exports perfectly into PDF,
but not into Excel.
The report contains a table with:
- a standard table header
- a table row: with alternating logos & a textbox directly
next to it
- a details area
- a table footer
(By alternating logos, I am referring to having different
images placed into a rectangle and different logos will
appear depending on certain conditions).
The problem: When exported into Excel, the logo/image does
not appear on the same row as the textbox that is directly
next to it. And the rest of the details from the table
gets pushed a few rows down.
Any info would be appreciated.
Regards,
LisaNo takers from Microsoft on this one?
Regards,
Lisa
"Lisa Liputra" wrote:
> Hi guys,
> I have set up a report that exports perfectly into PDF,
> but not into Excel.
> The report contains a table with:
> - a standard table header
> - a table row: with alternating logos & a textbox directly
> next to it
> - a details area
> - a table footer
> (By alternating logos, I am referring to having different
> images placed into a rectangle and different logos will
> appear depending on certain conditions).
> The problem: When exported into Excel, the logo/image does
> not appear on the same row as the textbox that is directly
> next to it. And the rest of the details from the table
> gets pushed a few rows down.
> Any info would be appreciated.
> Regards,
> Lisa
>
>
>