Sql Advice: March 2012

Thursday, March 29, 2012

Deserialization failed: The type initializer for 'Microsoft.ReportDesigner.Drawing.RptStyle

I have VS2003 and VS2005 installed as well as SQL Server 2000 and SQL Server 2005 Tools. I have RS2000 and RS2005 installed. RS2000 works fine in VS2003. When using VS2005 and opening a Microsoft sample project for 2005, I get the error listed in the subject line.

When trying to create a new project and connecting to an Oracle database or a SQL Server 2005 database, I get the following error: "A connection cannot be made to the database. Set and check the connection string." The connection works fine when the test button is clicked, but fails when continuing in the wizard.

Any suggestions. We are trying to migrate from RS2000 to RS2005 and nothing in 2005 works.

We're gettiing the same error on 8 machines at our company. We opened a ticket with MS and they closed it tell us to reinstall XP on the PCs. None have agreed to let us do this without knowing if it will work. If anyone has a clue why this is happening we'd really like to know.|||

Try the cure-all for every software problem. Reformat and reinstall.

|||Try modifying the HKEY_CURRENT_USER\Control Panel\International\sPositiveSign registry key so that its value is nothing. If it appears as though the value is already empty, edit the data string to some arbitrary viewable character, save it, open it up again and remove the value.sql

Deserialization failed: The element has invalid child element

a) how do I know which version of SSRS designer I have? how do I know
which version is current?
b) anyone know what this means:
c:\documents and settings\administrator\my documents\visual studio
projects\takeonefivefive_20070329\takeonefivefive\takeonefivefive
\takeonefivefive\rptReviewingMembersLetterFUN.rdl(571):
Deserialization failed: The element 'http://schemas.microsoft.com/
sqlserver/reporting/2003/10/reportdefinition:Value' has invalid child
element 'http://schemas.microsoft.com/sqlserver/reporting/2003/10/
reportdefinition:Enteranyadditionalcomments'. An error occurred at ,
(571, 23).On Apr 3, 7:29 pm, "aaron.ke...@.gmail.com" <aaron.ke...@.gmail.com>
wrote:
> a) how do I know which version of SSRS designer I have? how do I know
> which version is current?
> b) anyone know what this means:
> c:\documents and settings\administrator\my documents\visual studio
> projects\takeonefivefive_20070329\takeonefivefive\takeonefivefive
> \takeonefivefive\rptReviewingMembersLetterFUN.rdl(571):
> Deserialization failed: The element 'http://schemas.microsoft.com/
> sqlserver/reporting/2003/10/reportdefinition:Value' has invalid child
> element 'http://schemas.microsoft.com/sqlserver/reporting/2003/10/
> reportdefinition:Enteranyadditionalcomments'. An error occurred at ,
> (571, 23).
In Visual Studio, select the 'Help' tab and 'About Microsoft Visual
Studio' to get the version number, service pack, etc. Don't quote me
on this, but I believe that the latest version is 9.0.3042.
This thread may offer some insight into your error:
http://groups.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/232cb81b9f1f1328/5bb841311ab856ac?lnk=st&q=The+element+%27http%3A%2F%2Fschemas.microsoft.com%2Fsqlserver%2Freporting%2F2003+has+invalid+child+element&rnum=1#5bb841311ab856ac
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||I meant for SQL 2000 on the version thing
I've got 8.0.0.760 on the visual studio side.. or something around 700
I assume that this is not SP2 for SSRS 2000?
On Apr 3, 5:50 pm, "EMartinez" <emartinez...@.gmail.com> wrote:
> On Apr 3, 7:29 pm, "aaron.ke...@.gmail.com" <aaron.ke...@.gmail.com>
> wrote:
> > a) how do I know which version of SSRS designer I have? how do I know
> > which version is current?
> > b) anyone know what this means:
> > c:\documents and settings\administrator\my documents\visual studio
> > projects\takeonefivefive_20070329\takeonefivefive\takeonefivefive
> > \takeonefivefive\rptReviewingMembersLetterFUN.rdl(571):
> > Deserialization failed: The element 'http://schemas.microsoft.com/
> > sqlserver/reporting/2003/10/reportdefinition:Value' has invalid child
> > element 'http://schemas.microsoft.com/sqlserver/reporting/2003/10/
> > reportdefinition:Enteranyadditionalcomments'. An error occurred at ,
> > (571, 23).
> In Visual Studio, select the 'Help' tab and 'About Microsoft Visual
> Studio' to get the version number, service pack, etc. Don't quote me
> on this, but I believe that the latest version is 9.0.3042.
> This thread may offer some insight into your error:http://groups.google.com/group/microsoft.public.sqlserver.reportingsv...
> Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant|||On Apr 4, 11:45 am, "aaron.ke...@.gmail.com" <aaron.ke...@.gmail.com>
wrote:
> I meant for SQL 2000 on the version thing
> I've got 8.0.0.760 on the visual studio side.. or something around 700
> I assume that this is not SP2 for SSRS 2000?
> On Apr 3, 5:50 pm, "EMartinez" <emartinez...@.gmail.com> wrote:
> > On Apr 3, 7:29 pm, "aaron.ke...@.gmail.com" <aaron.ke...@.gmail.com>
> > wrote:
> > > a) how do I know which version of SSRS designer I have? how do I know
> > > which version is current?
> > > b) anyone know what this means:
> > > c:\documents and settings\administrator\my documents\visual studio
> > > projects\takeonefivefive_20070329\takeonefivefive\takeonefivefive
> > > \takeonefivefive\rptReviewingMembersLetterFUN.rdl(571):
> > > Deserialization failed: The element 'http://schemas.microsoft.com/
> > > sqlserver/reporting/2003/10/reportdefinition:Value' has invalid child
> > > element 'http://schemas.microsoft.com/sqlserver/reporting/2003/10/
> > > reportdefinition:Enteranyadditionalcomments'. An error occurred at ,
> > > (571, 23).
> > In Visual Studio, select the 'Help' tab and 'About Microsoft Visual
> > Studio' to get the version number, service pack, etc. Don't quote me
> > on this, but I believe that the latest version is 9.0.3042.
> > This thread may offer some insight into your error:http://groups.google.com/group/microsoft.public.sqlserver.reportingsv...
> > Hope this helps.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
You should be using either SP3 or SP3a, according to your version.
This link should be useful:
http://support.microsoft.com/kb/321185
Regards,
Enrique Martinez
Sr. Software Consultant|||yeah.. but that is the SP for the database-- not for the reporting
services side
I'll find it soon I guess
thanks
On Apr 4, 11:07 am, "EMartinez" <emartinez...@.gmail.com> wrote:
> On Apr 4, 11:45 am, "aaron.ke...@.gmail.com" <aaron.ke...@.gmail.com>
> wrote:
>
>
> > I meant for SQL 2000 on the version thing
> > I've got 8.0.0.760 on the visual studio side.. or something around 700
> > I assume that this is not SP2 for SSRS 2000?
> > On Apr 3, 5:50 pm, "EMartinez" <emartinez...@.gmail.com> wrote:
> > > On Apr 3, 7:29 pm, "aaron.ke...@.gmail.com" <aaron.ke...@.gmail.com>
> > > wrote:
> > > > a) how do I know which version of SSRS designer I have? how do I know
> > > > which version is current?
> > > > b) anyone know what this means:
> > > > c:\documents and settings\administrator\my documents\visual studio
> > > > projects\takeonefivefive_20070329\takeonefivefive\takeonefivefive
> > > > \takeonefivefive\rptReviewingMembersLetterFUN.rdl(571):
> > > > Deserialization failed: The element 'http://schemas.microsoft.com/
> > > > sqlserver/reporting/2003/10/reportdefinition:Value' has invalid child
> > > > element 'http://schemas.microsoft.com/sqlserver/reporting/2003/10/
> > > > reportdefinition:Enteranyadditionalcomments'. An error occurred at ,
> > > > (571, 23).
> > > In Visual Studio, select the 'Help' tab and 'About Microsoft Visual
> > > Studio' to get the version number, service pack, etc. Don't quote me
> > > on this, but I believe that the latest version is 9.0.3042.
> > > This thread may offer some insight into your error:http://groups.google.com/group/microsoft.public.sqlserver.reportingsv...
> > > Hope this helps.
> > > Regards,
> > > Enrique Martinez
> > > Sr. Software Consultant
> You should be using either SP3 or SP3a, according to your version.
> This link should be useful:http://support.microsoft.com/kb/321185
> Regards,
> Enrique Martinez
> Sr. Software Consultant- Hide quoted text -
> - Show quoted text -

Deserialization Failed: Parent Columns and Child Columns don't have type-matching columns.

After about an hour and a half of validation, my Analysis Services database has been migrated from 2000 to Analysis Services 2005.

I am now receiving the error in the subject any time I try and access the Data Source View that was created. All dimensions and cubes cannot be processed.

I have tried editing the xml manually to no avail.

Any ideas would be much appreciated!

Would still like to know what the issue is, but I found a workaround in the meantime.

I manually edited the .dsv file, renamed the ids, and restarted OLAP. I then opened the project in Business Intelligence Studio, and manually created the DSV. After a couple of renames of calculated columns the project seems to build properly.

|||I have exactly the same problem (Migration : all OK but I can not open the dsv properties )
I don't understand your resolution.
The migration generated a file .dsv.xml
What "Id" did you rename ?
I tried to rename the data source view ID but still cannot open
I cannot open the databases through Visual Studio. Same error message.

Deserialization Failed: Parent Columns and Child Columns don't have type-matching columns.

After about an hour and a half of validation, my Analysis Services database has been migrated from 2000 to Analysis Services 2005.

I am now receiving the error in the subject any time I try and access the Data Source View that was created. All dimensions and cubes cannot be processed.

I have tried editing the xml manually to no avail.

Any ideas would be much appreciated!

Would still like to know what the issue is, but I found a workaround in the meantime.

Deserialization failed: File or assembly name Microsoft.ReportingServices.Interfaces not f

Hello,
I just installed Vault Source Control on my machine. I then opened a
Reporting Services project with rdl's in it. Every RDL that is currently in
source control opens with this error
"Deserialization failed: File or assembly name
Microsoft.ReportingServices.Interfaces, or one of its dependencies, was not
found."
If I open another instance of the MSIDE without Vault (locally) and open a
different RDL it works fine. Is this an issue with the source control or
with the way it opens the file?
Any help will be appreciated. Need to get this solved.
PonnuI think it has to do with the way the add-in is written. Some add-ins turn
on shadow-copy, which plays havoc with the report designer as our assemblies
aren't located in the VS shared location. You might be able to copy the
report designer assemlies into the IDE directory. Not sure if you can
configure the add-in not to shadow copy.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
"Ponnurangam" <ponnurangam@.trellisys.net> wrote in message
news:uZiORNloEHA.1160@.tk2msftngp13.phx.gbl...
> Hello,
> I just installed Vault Source Control on my machine. I then opened a
> Reporting Services project with rdl's in it. Every RDL that is currently
> in
> source control opens with this error
> "Deserialization failed: File or assembly name
> Microsoft.ReportingServices.Interfaces, or one of its dependencies, was
> not
> found."
> If I open another instance of the MSIDE without Vault (locally) and open a
> different RDL it works fine. Is this an issue with the source control or
> with the way it opens the file?
> Any help will be appreciated. Need to get this solved.
> Ponnu
>

Deserialization failed: error message

This is the message I get when I try to create a report that has a lot of fields, I'm guessing that might be the problem.

Warning 1 Deserialization failed: The value must be between 0cm and 406.34921cm.
Parameter name: Width Line 10, position 30. 10 0

When you say lots of field how many are you talking about I wrote one that generated 165 valid pages with many concatenated columns.

|||

Thanks for the reply.

54 fields so doubt that is the issue.

|||sorry wrong query; the query involved returns 623 fields lol I think I will have to cut it down Smile

|||

I don't think you are getting that many fields from a database, if you are then you need to design it because if you do files and association the core of relational design 623 can be reduced to less than 100 fields. Hope this helps.

|||

Not my database and yes I am getting that many fields as I counted them.

Thanks for the replies I have sent the query back to the provider, will see what happens.

|||

I think you are getting Excel files in database files because relational design reduces such bloat to manageable tables and columns. Post again later because with design you can move the columns to a view and just call the view for that report.

sql

Deserialization failed error. Trying to automate an RDL file.

Whenever I try to change the SQL query on the RDL (which is an XML doc) and save it under a different name (to keep the original) I get the error...
"Deserialization failed: This is an unexpected token. The expected token is 'NAME'. Line 3325 position 28"

I am checking that line number and cannot fine any correlation.

One way to replicate this error is to create a new rdl file querying any number of fields. Save it and try to edit the sql using notepad inside the <CommmandText> section of the XML file. All I am doing is adding a union query so the fields stay the same, but I keep getting that error.

My purpose behind this is to generate rdl files with different sql criteria from an orignal template rdl.

Can any of you gurus figure this out?

No anwers on this yet?|||Still waiting...

Deserialization failed error

Can this be fixed by manually editing the rdl? I have tried however I
receive an error stating that Parameter name: Top must be between 0 and
85.33333in, when I change it to .5in, 1.5in I get ...is not a valid value.
Anyone, please help, I have created 11 pages and don't want to recreate them
as it failed on the last page.
Thanks for any help in this matter.Resolved. Yes this can be fixed by manually editing the rdl.
"DigitalVixen" wrote:
> Can this be fixed by manually editing the rdl? I have tried however I
> receive an error stating that Parameter name: Top must be between 0 and
> 85.33333in, when I change it to .5in, 1.5in I get ...is not a valid value.
> Anyone, please help, I have created 11 pages and don't want to recreate them
> as it failed on the last page.
> Thanks for any help in this matter.

Deserialization Failed - Microsoft Analysis Service

Hi Everyone,

I'm using Microsoft Analysis Service-2005. When I'm trying to open the database which contains 4 cubes and 10 dimensions, I'm getting the following error.

Deserialization Failed - Property not accessible because 'Parent columns
and Child columns don't have type -matching columns'.(Microsoft Analysis Service)

The system is not allowing me to open the cube so I'm unable to fix the issue.

All your suggestions would be highly appreciated.

Thanks,

Selva

Hello. Have you successfully built a parent-child dimension in BIDS that is processed and browsable? Both the parent column and the child-column have the same data types?

If this is the case you have either a problem with the join between the parent-child table and the fact table in the data source view or the join in the dimension usages tab in the cube editor.

Have you made a collection of the parent key(more than one column as the key) och child key in the dimension editor in an existing parent-child dimension? If so you would have to make a change in the dimension usage tab(where you join dimensions and measure groups), in the cube editor to reflect that?

Check this and return if the problem is not solved.

HTH

Thomas Ivarsson

Deserialization failed - how to fix?

Hi,
Have got the following message:
Deserialization failed: The table "table1" has rows that contain a different
number of cells than the number of the columns in the table (including cells
that span more than one column)
The report was fine until: I changed in the Code window the name of a
dataset field as it was used in 15 places for look and feel and it's quicker
to do it in the Code window via Search and Replace (have done this before).
The table 'table1' has a couple of merged cells, but these don't even use
this field. However it seems to me that the problem is related to the merged
cells.
I've changed it back in the code window, but the error remains. I can't
even see the report in Designer view anymore, just this error message. I can
still view the code.
Help! Have just spent days.
CR.Save the RDL, delete the report and re-add the RDL , That should get rid of
any former information in the RSS database and let you start anew.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"CR" <CR@.discussions.microsoft.com> wrote in message
news:0799C041-FCE0-41F2-9403-9F42C60800F0@.microsoft.com...
> Hi,
> Have got the following message:
> Deserialization failed: The table "table1" has rows that contain a
different
> number of cells than the number of the columns in the table (including
cells
> that span more than one column)
> The report was fine until: I changed in the Code window the name of a
> dataset field as it was used in 15 places for look and feel and it's
quicker
> to do it in the Code window via Search and Replace (have done this
before).
> The table 'table1' has a couple of merged cells, but these don't even use
> this field. However it seems to me that the problem is related to the
merged
> cells.
> I've changed it back in the code window, but the error remains. I can't
> even see the report in Designer view anymore, just this error message. I
can
> still view the code.
> Help! Have just spent days.
> CR.
>|||Have saved then deleted the RDL from the .NET project, then re-added. Is this
what you meant? The problem remains. Not sure what you mean by 'RSS'
database.
"Wayne Snyder" wrote:
> Save the RDL, delete the report and re-add the RDL , That should get rid of
> any former information in the RSS database and let you start anew.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "CR" <CR@.discussions.microsoft.com> wrote in message
> news:0799C041-FCE0-41F2-9403-9F42C60800F0@.microsoft.com...
> > Hi,
> >
> > Have got the following message:
> > Deserialization failed: The table "table1" has rows that contain a
> different
> > number of cells than the number of the columns in the table (including
> cells
> > that span more than one column)
> >
> > The report was fine until: I changed in the Code window the name of a
> > dataset field as it was used in 15 places for look and feel and it's
> quicker
> > to do it in the Code window via Search and Replace (have done this
> before).
> > The table 'table1' has a couple of merged cells, but these don't even use
> > this field. However it seems to me that the problem is related to the
> merged
> > cells.
> >
> > I've changed it back in the code window, but the error remains. I can't
> > even see the report in Designer view anymore, just this error message. I
> can
> > still view the code.
> >
> > Help! Have just spent days.
> >
> > CR.
> >
>
>|||I think he meant to delete from the server. (Using Report Manager)
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"CR" <CR@.discussions.microsoft.com> wrote in message
news:4AC3E1CC-5B9C-426C-877F-7704A66FCA2C@.microsoft.com...
> Have saved then deleted the RDL from the .NET project, then re-added. Is
> this
> what you meant? The problem remains. Not sure what you mean by 'RSS'
> database.
> "Wayne Snyder" wrote:
>> Save the RDL, delete the report and re-add the RDL , That should get rid
>> of
>> any former information in the RSS database and let you start anew.
>> --
>> Wayne Snyder, MCDBA, SQL Server MVP
>> Mariner, Charlotte, NC
>> www.mariner-usa.com
>> (Please respond only to the newsgroups.)
>> I support the Professional Association of SQL Server (PASS) and it's
>> community of SQL Server professionals.
>> www.sqlpass.org
>> "CR" <CR@.discussions.microsoft.com> wrote in message
>> news:0799C041-FCE0-41F2-9403-9F42C60800F0@.microsoft.com...
>> > Hi,
>> >
>> > Have got the following message:
>> > Deserialization failed: The table "table1" has rows that contain a
>> different
>> > number of cells than the number of the columns in the table (including
>> cells
>> > that span more than one column)
>> >
>> > The report was fine until: I changed in the Code window the name of a
>> > dataset field as it was used in 15 places for look and feel and it's
>> quicker
>> > to do it in the Code window via Search and Replace (have done this
>> before).
>> > The table 'table1' has a couple of merged cells, but these don't even
>> > use
>> > this field. However it seems to me that the problem is related to the
>> merged
>> > cells.
>> >
>> > I've changed it back in the code window, but the error remains. I
>> > can't
>> > even see the report in Designer view anymore, just this error message.
>> > I
>> can
>> > still view the code.
>> >
>> > Help! Have just spent days.
>> >
>> > CR.
>> >
>>|||Thanks both. I also deleted from ReportServer database. However can't
re-deploy due to Build failure with the original message.
It seems to me there's an issue with using Search and Replace in the Code
Window when merged cells are used in the table. Even when the merged cells
don't use the item you've editted. Have used Search/replace a lot and never
an issue, only in this case.
Wondering if anyone has found this also.
Cheers,
CR.
"Jeff A. Stucker" wrote:
> I think he meant to delete from the server. (Using Report Manager)
> --
> Cheers,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
> "CR" <CR@.discussions.microsoft.com> wrote in message
> news:4AC3E1CC-5B9C-426C-877F-7704A66FCA2C@.microsoft.com...
> > Have saved then deleted the RDL from the .NET project, then re-added. Is
> > this
> > what you meant? The problem remains. Not sure what you mean by 'RSS'
> > database.
> >
> > "Wayne Snyder" wrote:
> >
> >> Save the RDL, delete the report and re-add the RDL , That should get rid
> >> of
> >> any former information in the RSS database and let you start anew.
> >>
> >> --
> >> Wayne Snyder, MCDBA, SQL Server MVP
> >> Mariner, Charlotte, NC
> >> www.mariner-usa.com
> >> (Please respond only to the newsgroups.)
> >>
> >> I support the Professional Association of SQL Server (PASS) and it's
> >> community of SQL Server professionals.
> >> www.sqlpass.org
> >>
> >> "CR" <CR@.discussions.microsoft.com> wrote in message
> >> news:0799C041-FCE0-41F2-9403-9F42C60800F0@.microsoft.com...
> >> > Hi,
> >> >
> >> > Have got the following message:
> >> > Deserialization failed: The table "table1" has rows that contain a
> >> different
> >> > number of cells than the number of the columns in the table (including
> >> cells
> >> > that span more than one column)
> >> >
> >> > The report was fine until: I changed in the Code window the name of a
> >> > dataset field as it was used in 15 places for look and feel and it's
> >> quicker
> >> > to do it in the Code window via Search and Replace (have done this
> >> before).
> >> > The table 'table1' has a couple of merged cells, but these don't even
> >> > use
> >> > this field. However it seems to me that the problem is related to the
> >> merged
> >> > cells.
> >> >
> >> > I've changed it back in the code window, but the error remains. I
> >> > can't
> >> > even see the report in Designer view anymore, just this error message.
> >> > I
> >> can
> >> > still view the code.
> >> >
> >> > Help! Have just spent days.
> >> >
> >> > CR.
> >> >
> >>
> >>
> >>
>
>|||Using visual studio.net, un-merge the cells in your report (from the layout tab), then run the report. Now go back to report in the layout tab and merge your cells. I found that this worked for me.
Cheers
B
--
Message posted via http://www.sqlmonster.com

Deserialization failed

I am installing SSRS for the first time. I tried to create a simple report and I am getting the following error:

Deserialization failed: The type initializer for 'Microsoft.ReportDesigner.Drawing.RptStyleConstValue' threw an exception. Line 2, position 2.

Does anyone know how to fix this error?

Thanks,

Patrick

You have a problem http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=811976&SiteID=1

sql

Deserialization failed

I created a table with merged cells - etc. tried to render it and got the
following error:
Deserialization failed: The table "table2" has rows that contain a different
number of cells than the number of the columns in the table (including cells
that span more than one column)
Is there a way to fix this without redoing the whole report. The designer
won't show it in the layout window.
Thanks,
DavidI don't have a solution to your problem per se but I can tell you when it
seems to occur.
This happens to me when I cut/copy and paste columns that contain merged
cells. The merged cells themselves are ok. It seems that the copy/paste of
them doesn't work properly.
If I need to copy them now I unmerge them first copy then and merge them
back.
If this happens before you have exited the designer, you can usually salvage
your work by deleting the pasted rows in design view. After you have exited
the designer, it will no longer load the report into design view so short of
editing the rdl file manually (Which seems like it would be painful) I do
not know how to recover from this.
This appears to be a bug in the designer. Has anyone else experienced this?
General Patton
"CapitalEMR" <CapHS@.hvif.com> wrote in message
news:uCe3$gqVFHA.544@.TK2MSFTNGP15.phx.gbl...
> I created a table with merged cells - etc. tried to render it and got the
> following error:
> Deserialization failed: The table "table2" has rows that contain a
different
> number of cells than the number of the columns in the table (including
cells
> that span more than one column)
> Is there a way to fix this without redoing the whole report. The designer
> won't show it in the layout window.
> Thanks,
> David
>|||Yes, this is a known problem in Report Designer.
--
Albert Yen
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"General_Patton" <general_patton@.community.nospam.com> wrote in message
news:OyR9In$VFHA.2196@.TK2MSFTNGP09.phx.gbl...
>I don't have a solution to your problem per se but I can tell you when it
> seems to occur.
> This happens to me when I cut/copy and paste columns that contain merged
> cells. The merged cells themselves are ok. It seems that the copy/paste of
> them doesn't work properly.
> If I need to copy them now I unmerge them first copy then and merge them
> back.
> If this happens before you have exited the designer, you can usually
> salvage
> your work by deleting the pasted rows in design view. After you have
> exited
> the designer, it will no longer load the report into design view so short
> of
> editing the rdl file manually (Which seems like it would be painful) I do
> not know how to recover from this.
> This appears to be a bug in the designer. Has anyone else experienced
> this?
> General Patton
>
>
> "CapitalEMR" <CapHS@.hvif.com> wrote in message
> news:uCe3$gqVFHA.544@.TK2MSFTNGP15.phx.gbl...
>> I created a table with merged cells - etc. tried to render it and got the
>> following error:
>> Deserialization failed: The table "table2" has rows that contain a
> different
>> number of cells than the number of the columns in the table (including
> cells
>> that span more than one column)
>> Is there a way to fix this without redoing the whole report. The
>> designer
>> won't show it in the layout window.
>> Thanks,
>> David
>>
>|||"Albert Yen [MSFT]" wrote:
> Yes, this is a known problem in Report Designer.
That's really great you already know that. The question is, if there is some
RDL hack how one can remedy the problem. I've worked on a report for four
hours now and suddenly I've got that "Deserialization failed" error message.
Please, don't tell me I've got to do that work again!

Deserialization failed

I am trying to set the <Top> value of an image thru code.
<Image Name="Marker">
<ZIndex>35</ZIndex>
<Height>0.14583in</Height>
<Width>0.15625in</Width>
<Source>Embedded</Source>
<Style />
<Value>marker</Value>
<Top>=Code.GetPosition(Fields!TotalScore.Value, "1.55208in")</Top>
The error I receive is: "Deserialization failed:
=Code.GetPosition(Fields!TotalScore.Value, "1.55208in") cannot be parsed as a
unit because it does not contain numeric values. Examples of valid unit
strings are 1pt and .5in."
Is there a way to set the <Top> values thru code?
Thanks,
Phill SmogerPhill - Did you ever figure this out? I am trying to do the same thing for
the Width.
Thanks. Jen
"SmogerP" wrote:
> I am trying to set the <Top> value of an image thru code.
> <Image Name="Marker">
> <ZIndex>35</ZIndex>
> <Height>0.14583in</Height>
> <Width>0.15625in</Width>
> <Source>Embedded</Source>
> <Style />
> <Value>marker</Value>
> <Top>=Code.GetPosition(Fields!TotalScore.Value, "1.55208in")</Top>
> The error I receive is: "Deserialization failed:
> =Code.GetPosition(Fields!TotalScore.Value, "1.55208in") cannot be parsed as a
> unit because it does not contain numeric values. Examples of valid unit
> strings are 1pt and .5in."
> Is there a way to set the <Top> values thru code?
> Thanks,
> Phill Smoger
>|||<Top> and other position elements are always interpreted as constant values
representing measurement units. Expressions are not supported at this point.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jen Rubin" <JenRubin@.discussions.microsoft.com> wrote in message
news:94FD98AD-5CA1-4CE0-915A-AC760CF0291E@.microsoft.com...
> Phill - Did you ever figure this out? I am trying to do the same thing for
> the Width.
> Thanks. Jen
> "SmogerP" wrote:
>> I am trying to set the <Top> value of an image thru code.
>> <Image Name="Marker">
>> <ZIndex>35</ZIndex>
>> <Height>0.14583in</Height>
>> <Width>0.15625in</Width>
>> <Source>Embedded</Source>
>> <Style />
>> <Value>marker</Value>
>> <Top>=Code.GetPosition(Fields!TotalScore.Value,
>> "1.55208in")</Top>
>> The error I receive is: "Deserialization failed:
>> =Code.GetPosition(Fields!TotalScore.Value, "1.55208in") cannot be parsed
>> as a
>> unit because it does not contain numeric values. Examples of valid unit
>> strings are 1pt and .5in."
>> Is there a way to set the <Top> values thru code?
>> Thanks,
>> Phill Smoger

Descriptions on databases

Is there any way to put a description on a database? We have a couple databases that use acronyms which I would like to spell out as metadata.

See SQL Server 2005 Books Online topic:
Using Extended Properties on Database Objects
http://msdn2.microsoft.com/en-us/library/ms190243.aspx

Description: String cannot have zero length. Event ID: 6003

When i add a new document to the queue, I receive this error in the event log. I used the example from the book in chapter 5 but i left out the scheduled piece. I am unable to find anything via searches on google etc. Your help would be appreciated. Thank you!

XSLT File

<?xml version="1.0" encoding="UTF-8" ?>

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<xsl:output method="text"/>

<xsl:template match="notifications">

There is a new Test Document!

<xsl:apply-templates/>

</xsl:template>

<xsl:template match="notification">

Document Type: <xsl:value-of select="TypeName" />

Document Name: <xsl:value-of select="DocumentTitle" />

Document Category: <xsl:value-of select="CategoryName" />

<xsl:text>

</xsl:text>

</xsl:template>

</xsl:stylesheet>

Event log error:

Description: The assembly containing the content formatter could not be loaded.

EventParameters:

Instance Name: MyInstance 'Renamed for forum'

Application Name: Documents

Content Formatter Assembly Name:

Description: String cannot have zero length.

InstanceName: MyInstance 'Renamed for forum'

ApplicationName: Documents

Component: Distributor

ComponentDetails: DistributorName: MyDistributor 'Renamed for forum'

Thread: 4

ACF:

<ClassName>XsltFormatter</ClassName>

<Name>XsltBaseDirectoryPath</Name>

<Value>%_ApplicationBaseDirectoryPath_%\Formatters</Value>

</Argument>

<Name>XsltFileName</Name>

<Value>NewDocumentByType.xslt</Value>

</Argument>

</Arguments>

</ContentFormatter>

ICF

<ApplicationName>Documents</ApplicationName>

<BaseDirectoryPath>%_InstanceBaseDirectoryPath_%\Documents</BaseDirectoryPath>

<ApplicationDefinitionFilePath>ApplicationDefinition.xml</ApplicationDefinitionFilePath>

<Name>_NSServer_</Name>

<Value>%_NSServer_%</Value>

</Parameter>

<Name>_SQLServer_</Name>

<Value>%_SQLServer_%</Value>

</Parameter>

<Name>_ApplicationBaseDirectoryPath_</Name>

<Value>%_InstanceBaseDirectoryPath_%\Documents</Value>

</Parameter>

</Parameters>

</Application>

</Applications>

I fixed this by building a custom Formatter.

Description Metadata

When creating columns in MS-SQL there is a description field. How can I quer
y
this description field? I know how to return the Table Name, Column Name,
Data Type, Is_Nullable, etc. but I don’t know how to return the Descriptio
n.> When creating columns in MS-SQL there is a description field.
This is only ifyou create the columns in Enterprise Manager *and* choose to
use that property. Personally, I don't think you should do either, mostly
because your CREATE TABLE statements should be something that you can
script, modify, store in source control, etc.
In any case:
http://www.aspfaq.com/2244|||Aaron, good point! So where would you store the description of individual
columns? Would you create separate tables to store the descriptions of the
tables and the columns?|||> Aaron, good point! So where would you store the description of individual
> columns? Would you create separate tables to store the descriptions of the
> tables and the columns?
Why do you feel the description of your database schema needs to be stored
in the database?
We create separate human readable documentation. This allows us much more
freedom in how we are describing the schema, e.g. definitions > 64
characters, diagrams, tables, etc.
A|||I was thinking of creating a web app so that the descriptions, rules, etc.
can be documented, searched, and studied by several disparate groups. As of
now the database is completely undocumented. Then to complicate matters even
more, the knowledge of this database is scattered amongst many different
groups and individuals who won’t always work together. I keep running into
columns named TX5_RRT_SDescr and no one knows what the hell that column is
used for. The DBA is too busy to answer most questions and his answers are
too flipped to be of much use.
What form in your documentation in?|||Most of ours are in Word format. But you can make your job easier using an
extraction tool, for example Enterprise Architect.
Hey, if the DBA is too busy to answer questions that need to be answered,
why do you think he'd be willing to populate some table with the answers?
"Tome73" <Tome73@.discussions.microsoft.com> wrote in message
news:200AB1D7-AD01-426A-B580-7CE42716BBDE@.microsoft.com...
>I was thinking of creating a web app so that the descriptions, rules, etc.
> can be documented, searched, and studied by several disparate groups. As
> of
> now the database is completely undocumented. Then to complicate matters
> even
> more, the knowledge of this database is scattered amongst many different
> groups and individuals who won’t always work together. I keep running
> into
> columns named TX5_RRT_SDescr and no one knows what the hell that column is
> used for. The DBA is too busy to answer most questions and his answers are
> too flipped to be of much use.
> What form in your documentation in?|||Lol, he won’t! The rest of us peons will have to collaboratively piece thi
ngs
together. There are about 5 of us who have volunteered for this project and
I
just need to figure out how to best do it. I have a zero budget to work with
.
Ok then your suggestion is not to store the description in database
properties. Thanks.
The answer to my original post is:
Where Table name is ‘Admin_Users’ and the column name is ‘User_ID’
SELECT name, CONVERT(varchar(2000), [value]) AS Description
FROM ::fn_listextendedproperty(NULL, 'user', 'dbo', 'table',
'admin_Users', 'Column', 'User_ID')|||> The answer to my original post is:
> Where Table name is ‘Admin_Users’ and the column name is ‘User_ID’
> SELECT name, CONVERT(varchar(2000), [value]) AS Description
> FROM ::fn_listextendedproperty(NULL, 'user', 'dbo', 'table',
> 'admin_Users', 'Column', 'User_ID')
Yep, I posted a link to code samples earlier:
http://www.aspfaq.com/2244|||You could store your meta data in SQL Server tables and then develop your
own custom GUI and reports around it, but there are many 3rd party
applications would do a better job.
Tools like ERWin, Viseo (or even Enterprise Managers Diagramer) can be used
to create annotated diagrams of the database model
http://www.databaseanswers.com/modelling_tools.htm
Reporting Services 2005 has a Model Designer that provides end users with a
high level view of the database model for use with Report Builder.
http://www.devx.com/dbzone/Article/28047/1954?pf=true.
"Tome73" <Tome73@.discussions.microsoft.com> wrote in message
news:200AB1D7-AD01-426A-B580-7CE42716BBDE@.microsoft.com...
>I was thinking of creating a web app so that the descriptions, rules, etc.
> can be documented, searched, and studied by several disparate groups. As
> of
> now the database is completely undocumented. Then to complicate matters
> even
> more, the knowledge of this database is scattered amongst many different
> groups and individuals who won't always work together. I keep running into
> columns named TX5_RRT_SDescr and no one knows what the hell that column is
> used for. The DBA is too busy to answer most questions and his answers are
> too flipped to be of much use.
> What form in your documentation in?|||Aaron, yes you did and I missed it at first. I found
http://developer.com/db/article.php/3361751 which is basically the same.
Hey thanks Aaron for all your help and insight.sql

Description for fill factor on index rebuild maint plan misleading

Hi.
I found this misleading issue and thought I would share it.
We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
fillfactor of 90%. After the plan ran, the database grew by about 70% and
the fill factor was actually 10%.
We found the following in the maint plan:
'Change free space per page percentage to:' We entered 10%.
In hindsight, it meant FILLFACTOR and should have been 90%.
Do you also find this misleading?
The documentation (BOL) reads:
Change free space per page percentage to
Drop the indexes on the tables in the database and re-create them with a
new, automatically calculated fill factor, thereby reserving the specified
amount of free space on the index pages. The higher the percentage, the more
free space is reserved on the index pages, and the larger the index grows.
Valid values are from 0 through 100.
It says the HIGHER the percentage, the more free space is reserved. This
should read LOWER?
Is this a 'bug' in the documentation?
Could someone please pass this onto the Microsoft guys. Maybe they know
about this already.
Thanks!
WayneWayne
I agree that it is a little bit confusing
> We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
> fillfactor of 90%. After the plan ran, the database grew by about 70% and
> the fill factor was actually 10%.
rebuild indexes is logged operation and needs a free space to rebuild all
indexes
Kalen Delaney said
"The first definition
is correct; fillfactor specifies how full each page should be. 30 means 30%
full, 100 means 100% full. The only special case is 0, which means the leaf
level is full, but there is room for one or two rows per page in the upper
levels of the index tree.
I will report this discrepancy in the Books Online definitions. "
http://groups.google.com/group/microsoft.public.sqlserver.programming/browse_thread/thread/eda35e4b5bedab51/535a1ef3d33f1d88?lnk=st&q=&rnum=3&hl=en#535a1ef3d33f1d88
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:D30307D8-C6C6-4196-AB44-76E2F7958714@.microsoft.com...
> Hi.
> I found this misleading issue and thought I would share it.
> We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
> fillfactor of 90%. After the plan ran, the database grew by about 70% and
> the fill factor was actually 10%.
> We found the following in the maint plan:
> 'Change free space per page percentage to:' We entered 10%.
> In hindsight, it meant FILLFACTOR and should have been 90%.
> Do you also find this misleading?
> The documentation (BOL) reads:
>
> Change free space per page percentage to
> Drop the indexes on the tables in the database and re-create them with a
> new, automatically calculated fill factor, thereby reserving the specified
> amount of free space on the index pages. The higher the percentage, the
> more
> free space is reserved on the index pages, and the larger the index grows.
> Valid values are from 0 through 100.
>
> It says the HIGHER the percentage, the more free space is reserved. This
> should read LOWER?
>
> Is this a 'bug' in the documentation?
>
> Could someone please pass this onto the Microsoft guys. Maybe they know
> about this already.
> Thanks!
> Wayne
>|||"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:D30307D8-C6C6-4196-AB44-76E2F7958714@.microsoft.com...
> Hi.
> I found this misleading issue and thought I would share it.
> We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
> fillfactor of 90%. After the plan ran, the database grew by about 70% and
> the fill factor was actually 10%.
> We found the following in the maint plan:
> 'Change free space per page percentage to:' We entered 10%.
> In hindsight, it meant FILLFACTOR and should have been 90%.
> Do you also find this misleading?
> The documentation (BOL) reads:
>
> Change free space per page percentage to
> Drop the indexes on the tables in the database and re-create them with a
> new, automatically calculated fill factor, thereby reserving the specified
> amount of free space on the index pages. The higher the percentage, the
> more
> free space is reserved on the index pages, and the larger the index grows.
> Valid values are from 0 through 100.
>
> It says the HIGHER the percentage, the more free space is reserved. This
> should read LOWER?
>
> Is this a 'bug' in the documentation?
>
> Could someone please pass this onto the Microsoft guys. Maybe they know
> about this already.
>
Anyone can submit doc bugs. The feedback link at the bottom of the BOL
topics will generate an email that automatically creates a doc bug.
David

Description for fill factor on index rebuild maint plan misleading

Hi.
I found this misleading issue and thought I would share it.
We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
fillfactor of 90%. After the plan ran, the database grew by about 70% and
the fill factor was actually 10%.
We found the following in the maint plan:
'Change free space per page percentage to:' We entered 10%.
In hindsight, it meant FILLFACTOR and should have been 90%.
Do you also find this misleading?
The documentation (BOL) reads:
Change free space per page percentage to
Drop the indexes on the tables in the database and re-create them with a
new, automatically calculated fill factor, thereby reserving the specified
amount of free space on the index pages. The higher the percentage, the more
free space is reserved on the index pages, and the larger the index grows.
Valid values are from 0 through 100.
It says the HIGHER the percentage, the more free space is reserved. This
should read LOWER?
Is this a 'bug' in the documentation?
Could someone please pass this onto the Microsoft guys. Maybe they know
about this already.
Thanks!
WayneWayne
I agree that it is a little bit confusing

> We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
> fillfactor of 90%. After the plan ran, the database grew by about 70% and
> the fill factor was actually 10%.
rebuild indexes is logged operation and needs a free space to rebuild all
indexes
Kalen Delaney said
"The first definition
is correct; fillfactor specifies how full each page should be. 30 means 30%
full, 100 means 100% full. The only special case is 0, which means the leaf
level is full, but there is room for one or two rows per page in the upper
levels of the index tree.
I will report this discrepancy in the Books Online definitions. "
http://groups.google.com/group/micr...33f1d88

"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:D30307D8-C6C6-4196-AB44-76E2F7958714@.microsoft.com...
> Hi.
> I found this misleading issue and thought I would share it.
> We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
> fillfactor of 90%. After the plan ran, the database grew by about 70% and
> the fill factor was actually 10%.
> We found the following in the maint plan:
> 'Change free space per page percentage to:' We entered 10%.
> In hindsight, it meant FILLFACTOR and should have been 90%.
> Do you also find this misleading?
> The documentation (BOL) reads:
>
> Change free space per page percentage to
> Drop the indexes on the tables in the database and re-create them with a
> new, automatically calculated fill factor, thereby reserving the specified
> amount of free space on the index pages. The higher the percentage, the
> more
> free space is reserved on the index pages, and the larger the index grows.
> Valid values are from 0 through 100.
>
> It says the HIGHER the percentage, the more free space is reserved. This
> should read LOWER?
>
> Is this a 'bug' in the documentation?
>
> Could someone please pass this onto the Microsoft guys. Maybe they know
> about this already.
> Thanks!
> Wayne
>|||"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:D30307D8-C6C6-4196-AB44-76E2F7958714@.microsoft.com...
> Hi.
> I found this misleading issue and thought I would share it.
> We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
> fillfactor of 90%. After the plan ran, the database grew by about 70% and
> the fill factor was actually 10%.
> We found the following in the maint plan:
> 'Change free space per page percentage to:' We entered 10%.
> In hindsight, it meant FILLFACTOR and should have been 90%.
> Do you also find this misleading?
> The documentation (BOL) reads:
>
> Change free space per page percentage to
> Drop the indexes on the tables in the database and re-create them with a
> new, automatically calculated fill factor, thereby reserving the specified
> amount of free space on the index pages. The higher the percentage, the
> more
> free space is reserved on the index pages, and the larger the index grows.
> Valid values are from 0 through 100.
>
> It says the HIGHER the percentage, the more free space is reserved. This
> should read LOWER?
>
> Is this a 'bug' in the documentation?
>
> Could someone please pass this onto the Microsoft guys. Maybe they know
> about this already.
>
Anyone can submit doc bugs. The feedback link at the bottom of the BOL
topics will generate an email that automatically creates a doc bug.
David

Description for Configuration Values

Hi, Pra

It seems that these descriptions are stored in the SQLDMO.RLL file, so
I see no easy way of retrieiving them from T-SQL (since these
descriptions are not stored in any system table).
Razvan|||Thanks Razvan
Can u tell me one more thing how can I relate the config value with the
message.
Thanks
Pra

"Razvan Socol" <rsocol@.gmail.com> wrote in message
news:1139988679.719312.27840@.g47g2000cwa.googlegroups.com...
> Hi, Pra

> It seems that these descriptions are stored in the SQLDMO.RLL file, so
> I see no easy way of retrieiving them from T-SQL (since these
> descriptions are not stored in any system table).
> Razvan
>|||Hi, Pra

You can use SQL-DMO to iterate through the each of the values in the
ConfigValues collection to get the Name and Description properties and
store them in your own table.
You may also want to take a look at:
http://msdn2.microsoft.com/en-us/library/ms131974.aspx
[url]http://msdn.microsoft.com/library/en-us/sqldmo/dmoref_cnst02_2w9x.asp?frame=true[/
url]
to check if you have found all the documented configuration values in
the ConfigValues collection.
Razvan|||Thanks
But I cant do that. Any other way.
Pra

"Razvan Socol" <rsocol@.gmail.com> wrote in message
news:1140002871.149041.272720@.z14g2000cwz.googlegroups.com...
> Hi, Pra

> You can use SQL-DMO to iterate through the each of the values in the
> ConfigValues collection to get the Name and Description properties and
> store them in your own table.
> You may also want to take a look at:
> http://msdn2.microsoft.com/en-us/library/ms131974.aspx
> http://msdn.microsoft.com/library/e...me=true

> to check if you have found all the documented configuration values in
> the ConfigValues collection.
> Razvan
>|||Hi, Pra

Please tell me the reason why you can't do that, so I can think of
another way that works (not another way that you can't do, either). You
can also state the overall scenario of what you are trying to do with
the description and why you need this description instead of the
description from the sys.configurations table.
In the mean time, I would say that you can invoke the SQL-DMO code from
T-SQL using the sp_OACreate / sp_SetProperty / sp_OAGetProperty
procedures. This is the "non-easy" way that I thought when I wrote the
first message.
Razvan|||Thanks Razvan
I never knew about OLE prog. using T-SQL.
See the scenario is previously we used the SQL-DMO to report on SQL
Servers.
Now with Yukon coming into picture and SQL-DMO not fully compatible with
Yukon. I have to change the implementation to ADO. I can't use SMO bcoz
there is some code which is already written in ADO so I want reuse that, so
I was thinking of getting these values from the tables/system tables/views
anything but DMO and SMO. So, I'm hunting for description other
values I got throught the sysconfigures, syscurconfigs, spt_values, only
description I couldn't get.
I'm stuck only bcoz of this field.
Thanks
Pra

"Razvan Socol" <rsocol@.gmail.com> wrote in message
news:1140007841.077219.207640@.g44g2000cwa.googlegroups.com...
> Hi, Pra

> Please tell me the reason why you can't do that, so I can think of
> another way that works (not another way that you can't do, either). You
> can also state the overall scenario of what you are trying to do with
> the description and why you need this description instead of the
> description from the sys.configurations table.
> In the mean time, I would say that you can invoke the SQL-DMO code from
> T-SQL using the sp_OACreate / sp_SetProperty / sp_OAGetProperty
> procedures. This is the "non-easy" way that I thought when I wrote the
> first message.
> Razvan
>|||Hi, Pra

What do you mean by "SQL-DMO not fully compatible with Yukon" ? As far
as I know, everything that you can do using SQL-DMO against a SQL
Server 2000 server, you can also do using SQL-DMO against a SQL Server
2005 server, as long as the updated SQL-DMO components are installed
(by default they are not).
If you need to use the new features of SQL Server 2005, you should use
SMO instead of SQL-DMO (especially if you are writing a .Net
application). SMO supports SQL Server 2000, too.
If you really don't want to use SQL-DMO or SMO, you can store the
descriptions in your application: retrieve them using SQL-DMO (only
once, using a separate little app) then store them as constants (or
something else) in your code.
Razvan|||Thanks Razvan
"Razvan Socol" <rsocol@.gmail.com> wrote in message
news:1140015110.381400.268180@.g43g2000cwa.googlegroups.com...
> Hi, Pra

> What do you mean by "SQL-DMO not fully compatible with Yukon" ? As far
> as I know, everything that you can do using SQL-DMO against a SQL
> Server 2000 server, you can also do using SQL-DMO against a SQL Server
> 2005 server, as long as the updated SQL-DMO components are installed
> (by default they are not).
> If you need to use the new features of SQL Server 2005, you should use
> SMO instead of SQL-DMO (especially if you are writing a .Net
> application). SMO supports SQL Server 2000, too.
> If you really don't want to use SQL-DMO or SMO, you can store the
> descriptions in your application: retrieve them using SQL-DMO (only
> once, using a separate little app) then store them as constants (or
> something else) in your code.
> Razvan
>

Description for Configuration Values

Hi,
From where can I get the description for the Config Values for both SQL
2000 and SQL 2005
Similar to the one that SQL-DMO returns when queried for the description
of a particular configuration values, is it stored in some system tables.
The comment field gives very little information about the configuration
value as compared to the description given by SQL-DMO.
Also, the description field value in SQL 2005 is not the same when
queried through SQL-DMO.
e.g. In the table sys.configurations the config value "affinity mask"
has description "affinity mask"
but when queried thru SQL-DMO it gives the following
"Indicates which processors SQL Server may use (default is 0, or any).
A non-zero value is interpreted as a bit mask; e.g, processors 1, 2, and 5
are specified with a hexadecimal value of 0x13 or the decimal equivalent
of 19."
TIA
PrasadHi, Prasad
It seems that these descriptions are stored in the SQLDMO.RLL file, so
I see no easy way of retrieiving them from T-SQL (since these
descriptions are not stored in any system table).
Razvan|||Thanks Razvan
Can u tell me one more thing how can I relate the config value with the
message.
Thanks
Prasad
"Razvan Socol" <rsocol@.gmail.com> wrote in message
news:1139988679.719312.27840@.g47g2000cwa.googlegroups.com...
> Hi, Prasad
> It seems that these descriptions are stored in the SQLDMO.RLL file, so
> I see no easy way of retrieiving them from T-SQL (since these
> descriptions are not stored in any system table).
> Razvan
>|||Hi, Prasad
You can use SQL-DMO to iterate through the each of the values in the
ConfigValues collection to get the Name and Description properties and
store them in your own table.
You may also want to take a look at:
http://msdn2.microsoft.com/en-us/library/ms131974.aspx
[url]http://msdn.microsoft.com/library/en-us/sqldmo/dmoref_cnst02_2w9x.asp?frame=true[/
url]
to check if you have found all the documented configuration values in
the ConfigValues collection.
Razvan|||Thanks
But I cant do that. Any other way.
Prasad
"Razvan Socol" <rsocol@.gmail.com> wrote in message
news:1140002871.149041.272720@.z14g2000cwz.googlegroups.com...
> Hi, Prasad
> You can use SQL-DMO to iterate through the each of the values in the
> ConfigValues collection to get the Name and Description properties and
> store them in your own table.
> You may also want to take a look at:
> http://msdn2.microsoft.com/en-us/library/ms131974.aspx
> http://msdn.microsoft.com/library/e...me=true

> to check if you have found all the documented configuration values in
> the ConfigValues collection.
> Razvan
>|||Hi, Prasad
Please tell me the reason why you can't do that, so I can think of
another way that works (not another way that you can't do, either). You
can also state the overall scenario of what you are trying to do with
the description and why you need this description instead of the
description from the sys.configurations table.
In the mean time, I would say that you can invoke the SQL-DMO code from
T-SQL using the sp_OACreate / sp_SetProperty / sp_OAGetProperty
procedures. This is the "non-easy" way that I thought when I wrote the
first message.
Razvan|||Thanks Razvan
I never knew about OLE prog. using T-SQL.
See the scenario is previously we used the SQL-DMO to report on SQL
Servers.
Now with Yukon coming into picture and SQL-DMO not fully compatible with
Yukon. I have to change the implementation to ADO. I can't use SMO bcoz
there is some code which is already written in ADO so I want reuse that, so
I was thinking of getting these values from the tables/system tables/views
anything but DMO and SMO. So, I'm hunting for description other
values I got throught the sysconfigures, syscurconfigs, spt_values, only
description I couldn't get.
I'm stuck only bcoz of this field.
Thanks
Prasad
"Razvan Socol" <rsocol@.gmail.com> wrote in message
news:1140007841.077219.207640@.g44g2000cwa.googlegroups.com...
> Hi, Prasad
> Please tell me the reason why you can't do that, so I can think of
> another way that works (not another way that you can't do, either). You
> can also state the overall scenario of what you are trying to do with
> the description and why you need this description instead of the
> description from the sys.configurations table.
> In the mean time, I would say that you can invoke the SQL-DMO code from
> T-SQL using the sp_OACreate / sp_SetProperty / sp_OAGetProperty
> procedures. This is the "non-easy" way that I thought when I wrote the
> first message.
> Razvan
>|||Hi, Prasad
What do you mean by "SQL-DMO not fully compatible with Yukon" ? As far
as I know, everything that you can do using SQL-DMO against a SQL
Server 2000 server, you can also do using SQL-DMO against a SQL Server
2005 server, as long as the updated SQL-DMO components are installed
(by default they are not).
If you need to use the new features of SQL Server 2005, you should use
SMO instead of SQL-DMO (especially if you are writing a .Net
application). SMO supports SQL Server 2000, too.
If you really don't want to use SQL-DMO or SMO, you can store the
descriptions in your application: retrieve them using SQL-DMO (only
once, using a separate little app) then store them as constants (or
something else) in your code.
Razvan|||Thanks Razvan
"Razvan Socol" <rsocol@.gmail.com> wrote in message
news:1140015110.381400.268180@.g43g2000cwa.googlegroups.com...
> Hi, Prasad
> What do you mean by "SQL-DMO not fully compatible with Yukon" ? As far
> as I know, everything that you can do using SQL-DMO against a SQL
> Server 2000 server, you can also do using SQL-DMO against a SQL Server
> 2005 server, as long as the updated SQL-DMO components are installed
> (by default they are not).
> If you need to use the new features of SQL Server 2005, you should use
> SMO instead of SQL-DMO (especially if you are writing a .Net
> application). SMO supports SQL Server 2000, too.
> If you really don't want to use SQL-DMO or SMO, you can store the
> descriptions in your application: retrieve them using SQL-DMO (only
> once, using a separate little app) then store them as constants (or
> something else) in your code.
> Razvan
>

Description for Configuration Values

Hi,
From where can I get the description for the Config Values for both SQL
2000 and SQL 2005
Similar to the one that SQL-DMO returns when queried for the description
of a particular configuration values, is it stored in some system tables.
The comment field gives very little information about the configuration
value as compared to the description given by SQL-DMO.
Also, the description field value in SQL 2005 is not the same when
queried through SQL-DMO.
e.g. In the table sys.configurations the config value "affinity mask"
has description "affinity mask"
but when queried thru SQL-DMO it gives the following
"Indicates which processors SQL Server may use (default is 0, or any).
A non-zero value is interpreted as a bit mask; e.g, processors 1, 2, and 5
are specified with a hexadecimal value of 0x13 or the decimal equivalent
of 19."
TIA
Prasad
Hi, Prasad
It seems that these descriptions are stored in the SQLDMO.RLL file, so
I see no easy way of retrieiving them from T-SQL (since these
descriptions are not stored in any system table).
Razvan
|||Thanks Razvan
Can u tell me one more thing how can I relate the config value with the
message.
Thanks
Prasad
"Razvan Socol" <rsocol@.gmail.com> wrote in message
news:1139988679.719312.27840@.g47g2000cwa.googlegro ups.com...
> Hi, Prasad
> It seems that these descriptions are stored in the SQLDMO.RLL file, so
> I see no easy way of retrieiving them from T-SQL (since these
> descriptions are not stored in any system table).
> Razvan
>
|||Hi, Prasad
You can use SQL-DMO to iterate through the each of the values in the
ConfigValues collection to get the Name and Description properties and
store them in your own table.
You may also want to take a look at:
http://msdn2.microsoft.com/en-us/library/ms131974.aspx
http://msdn.microsoft.com/library/en...asp?frame=true
to check if you have found all the documented configuration values in
the ConfigValues collection.
Razvan
|||Thanks
But I cant do that. Any other way.
Prasad
"Razvan Socol" <rsocol@.gmail.com> wrote in message
news:1140002871.149041.272720@.z14g2000cwz.googlegr oups.com...
> Hi, Prasad
> You can use SQL-DMO to iterate through the each of the values in the
> ConfigValues collection to get the Name and Description properties and
> store them in your own table.
> You may also want to take a look at:
> http://msdn2.microsoft.com/en-us/library/ms131974.aspx
> http://msdn.microsoft.com/library/en...asp?frame=true
> to check if you have found all the documented configuration values in
> the ConfigValues collection.
> Razvan
>
|||Hi, Prasad
Please tell me the reason why you can't do that, so I can think of
another way that works (not another way that you can't do, either). You
can also state the overall scenario of what you are trying to do with
the description and why you need this description instead of the
description from the sys.configurations table.
In the mean time, I would say that you can invoke the SQL-DMO code from
T-SQL using the sp_OACreate / sp_SetProperty / sp_OAGetProperty
procedures. This is the "non-easy" way that I thought when I wrote the
first message.
Razvan
|||Thanks Razvan
I never knew about OLE prog. using T-SQL.
See the scenario is previously we used the SQL-DMO to report on SQL
Servers.
Now with Yukon coming into picture and SQL-DMO not fully compatible with
Yukon. I have to change the implementation to ADO. I can't use SMO bcoz
there is some code which is already written in ADO so I want reuse that, so
I was thinking of getting these values from the tables/system tables/views
anything but DMO and SMO. So, I'm hunting for description other
values I got throught the sysconfigures, syscurconfigs, spt_values, only
description I couldn't get.
I'm stuck only bcoz of this field.
Thanks
Prasad
"Razvan Socol" <rsocol@.gmail.com> wrote in message
news:1140007841.077219.207640@.g44g2000cwa.googlegr oups.com...
> Hi, Prasad
> Please tell me the reason why you can't do that, so I can think of
> another way that works (not another way that you can't do, either). You
> can also state the overall scenario of what you are trying to do with
> the description and why you need this description instead of the
> description from the sys.configurations table.
> In the mean time, I would say that you can invoke the SQL-DMO code from
> T-SQL using the sp_OACreate / sp_SetProperty / sp_OAGetProperty
> procedures. This is the "non-easy" way that I thought when I wrote the
> first message.
> Razvan
>
|||Hi, Prasad
What do you mean by "SQL-DMO not fully compatible with Yukon" ? As far
as I know, everything that you can do using SQL-DMO against a SQL
Server 2000 server, you can also do using SQL-DMO against a SQL Server
2005 server, as long as the updated SQL-DMO components are installed
(by default they are not).
If you need to use the new features of SQL Server 2005, you should use
SMO instead of SQL-DMO (especially if you are writing a .Net
application). SMO supports SQL Server 2000, too.
If you really don't want to use SQL-DMO or SMO, you can store the
descriptions in your application: retrieve them using SQL-DMO (only
once, using a separate little app) then store them as constants (or
something else) in your code.
Razvan
|||Thanks Razvan
"Razvan Socol" <rsocol@.gmail.com> wrote in message
news:1140015110.381400.268180@.g43g2000cwa.googlegr oups.com...
> Hi, Prasad
> What do you mean by "SQL-DMO not fully compatible with Yukon" ? As far
> as I know, everything that you can do using SQL-DMO against a SQL
> Server 2000 server, you can also do using SQL-DMO against a SQL Server
> 2005 server, as long as the updated SQL-DMO components are installed
> (by default they are not).
> If you need to use the new features of SQL Server 2005, you should use
> SMO instead of SQL-DMO (especially if you are writing a .Net
> application). SMO supports SQL Server 2000, too.
> If you really don't want to use SQL-DMO or SMO, you can store the
> descriptions in your application: retrieve them using SQL-DMO (only
> once, using a separate little app) then store them as constants (or
> something else) in your code.
> Razvan
>
sql

Description for Configuration Values

Hi,
From where can I get the description for the Config Values for both SQL
2000 and SQL 2005
Similar to the one that SQL-DMO returns when queried for the description
of a particular configuration values, is it stored in some system tables.
The comment field gives very little information about the configuration
value as compared to the description given by SQL-DMO.
Also, the description field value in SQL 2005 is not the same when
queried through SQL-DMO.
e.g. In the table sys.configurations the config value "affinity mask"
has description "affinity mask"
but when queried thru SQL-DMO it gives the following
"Indicates which processors SQL Server may use (default is 0, or any).
A non-zero value is interpreted as a bit mask; e.g, processors 1, 2, and 5
are specified with a hexadecimal value of 0x13 or the decimal equivalent
of 19."
TIA
PrasadHi, Prasad
It seems that these descriptions are stored in the SQLDMO.RLL file, so
I see no easy way of retrieiving them from T-SQL (since these
descriptions are not stored in any system table).
Razvan|||Thanks Razvan
Can u tell me one more thing how can I relate the config value with the
message.
Thanks
Prasad
"Razvan Socol" <rsocol@.gmail.com> wrote in message
news:1139988679.719312.27840@.g47g2000cwa.googlegroups.com...
> Hi, Prasad
> It seems that these descriptions are stored in the SQLDMO.RLL file, so
> I see no easy way of retrieiving them from T-SQL (since these
> descriptions are not stored in any system table).
> Razvan
>|||Hi, Prasad
You can use SQL-DMO to iterate through the each of the values in the
ConfigValues collection to get the Name and Description properties and
store them in your own table.
You may also want to take a look at:
http://msdn2.microsoft.com/en-us/library/ms131974.aspx
http://msdn.microsoft.com/library/en-us/sqldmo/dmoref_cnst02_2w9x.asp?frame=true
to check if you have found all the documented configuration values in
the ConfigValues collection.
Razvan|||Thanks
But I cant do that. Any other way.
Prasad
"Razvan Socol" <rsocol@.gmail.com> wrote in message
news:1140002871.149041.272720@.z14g2000cwz.googlegroups.com...
> Hi, Prasad
> You can use SQL-DMO to iterate through the each of the values in the
> ConfigValues collection to get the Name and Description properties and
> store them in your own table.
> You may also want to take a look at:
> http://msdn2.microsoft.com/en-us/library/ms131974.aspx
> http://msdn.microsoft.com/library/en-us/sqldmo/dmoref_cnst02_2w9x.asp?frame=true
> to check if you have found all the documented configuration values in
> the ConfigValues collection.
> Razvan
>|||Hi, Prasad
Please tell me the reason why you can't do that, so I can think of
another way that works (not another way that you can't do, either). You
can also state the overall scenario of what you are trying to do with
the description and why you need this description instead of the
description from the sys.configurations table.
In the mean time, I would say that you can invoke the SQL-DMO code from
T-SQL using the sp_OACreate / sp_SetProperty / sp_OAGetProperty
procedures. This is the "non-easy" way that I thought when I wrote the
first message.
Razvan|||Thanks Razvan
I never knew about OLE prog. using T-SQL.
See the scenario is previously we used the SQL-DMO to report on SQL
Servers.
Now with Yukon coming into picture and SQL-DMO not fully compatible with
Yukon. I have to change the implementation to ADO. I can't use SMO bcoz
there is some code which is already written in ADO so I want reuse that, so
I was thinking of getting these values from the tables/system tables/views
anything but DMO and SMO. So, I'm hunting for description other
values I got throught the sysconfigures, syscurconfigs, spt_values, only
description I couldn't get.
I'm stuck only bcoz of this field.
Thanks
Prasad
"Razvan Socol" <rsocol@.gmail.com> wrote in message
news:1140007841.077219.207640@.g44g2000cwa.googlegroups.com...
> Hi, Prasad
> Please tell me the reason why you can't do that, so I can think of
> another way that works (not another way that you can't do, either). You
> can also state the overall scenario of what you are trying to do with
> the description and why you need this description instead of the
> description from the sys.configurations table.
> In the mean time, I would say that you can invoke the SQL-DMO code from
> T-SQL using the sp_OACreate / sp_SetProperty / sp_OAGetProperty
> procedures. This is the "non-easy" way that I thought when I wrote the
> first message.
> Razvan
>|||Hi, Prasad
What do you mean by "SQL-DMO not fully compatible with Yukon" ? As far
as I know, everything that you can do using SQL-DMO against a SQL
Server 2000 server, you can also do using SQL-DMO against a SQL Server
2005 server, as long as the updated SQL-DMO components are installed
(by default they are not).
If you need to use the new features of SQL Server 2005, you should use
SMO instead of SQL-DMO (especially if you are writing a .Net
application). SMO supports SQL Server 2000, too.
If you really don't want to use SQL-DMO or SMO, you can store the
descriptions in your application: retrieve them using SQL-DMO (only
once, using a separate little app) then store them as constants (or
something else) in your code.
Razvan|||Thanks Razvan
"Razvan Socol" <rsocol@.gmail.com> wrote in message
news:1140015110.381400.268180@.g43g2000cwa.googlegroups.com...
> Hi, Prasad
> What do you mean by "SQL-DMO not fully compatible with Yukon" ? As far
> as I know, everything that you can do using SQL-DMO against a SQL
> Server 2000 server, you can also do using SQL-DMO against a SQL Server
> 2005 server, as long as the updated SQL-DMO components are installed
> (by default they are not).
> If you need to use the new features of SQL Server 2005, you should use
> SMO instead of SQL-DMO (especially if you are writing a .Net
> application). SMO supports SQL Server 2000, too.
> If you really don't want to use SQL-DMO or SMO, you can store the
> descriptions in your application: retrieve them using SQL-DMO (only
> once, using a separate little app) then store them as constants (or
> something else) in your code.
> Razvan
>

Description for Calculated Members

You can add descriptions to measures that are built under the Cube Structure tab. But I cannot see how to add a description to a Calculated Member. Is it possible to add a description to a Calculated Member?
Looks like this has already been answered.

Anyone interested, here is the link.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=325816&SiteID=1
|||You might be interested in looking at BIDSHelper www.codeplex.com/bidshelper it's free addin for BI Development Studio that adds a number of useful features including the ability to add descriptions to calculated members (through the member properties dialog) http://www.codeplex.com/bidshelper/Wiki/View.aspx?title=Calculation%20Helpers&referringTitle=Home

Description for Calculated Measures?

Hi,

is there no way to add a description for a Calculated Measure? Well, that would be something to add if it's not there already... Metadata is so important so I think it's very important to have a description at this point, it's even more important since it's something you calculate and so it might be not good known for all the users...

Hello

It is perfectly possible in MSAS 2005,You can go to the Script View of calculated Measure and you can add the description there

Thx and regards

Pankaj

|||

Pankaj,

that sounds great... However: How to you do that? There is no documentation about that... I'm not talking about some comment in the MDX script, I would like to have a description which is saved with the measure and clients can display to the user...

Thanks,

|||

hello Thomas,

indeed, it looks like there is an omission in the UI, and setting description is not currently exposed.

If you really need to set it a lot, however, you can still specify the Description in cube file, using the CalculationProperty. In the Solution Explorer right click on your cube and choose View Code. Find the MdxScript element. See if it contains CalculationProperties element under it. if it does, see if there is already CalculationProperty element corresponding to the calculated member that you are interested in. If there is simply add the <Description>...</Description> tag there. If there is no CalculationPorperty for the specific calculation yet - go to calculation Properies dialog in the Calculations tab of cube editor (there is a toolbar button for it), and set a Display Folder for the calc member you are interested in. This should create a calculation property. Then edit the cube file and add <Description> there, you can also remove DisplayFolder, if you really didn't need it. [of course you can just create the whole calc property by hand, but i'd probably suggest using UI as is less possibility to make a typo or something.]

Below is a sample of the script with a single Calculated Member calculation and a Description set for it.

<MdxScripts>
<MdxScript dwd:design-time-name="2f5f0150-ae7c-47bf-b4ef-df02e6456044">
<ID>MdxScript</ID>
<Name>MdxScript</Name>
<CreatedTimestamp>0001-01-01T08:00:00Z</CreatedTimestamp>
<LastSchemaUpdate>0001-01-01T08:00:00Z</LastSchemaUpdate>
<Commands>
<Command>
<Text>/*
The CALCULATE command controls the aggregation of leaf cells in the cube.
If the CALCULATE command is deleted or modified, the data within the cube is affected.
You should edit this command only if you manually specify how the cube is aggregated.
*/
CALCULATE;

CREATE MEMBER CURRENTCUBE.[MEASURES].[Calculated Member]
AS 1,
VISIBLE = 1 ; </Text>
</Command>
</Commands>
<CalculationProperties>
<CalculationProperty dwd:design-time-name="53d79ba5-3a54-4165-9798-3b19ba278ca0">
<CalculationReference>[MEASURES].[Calculated Member]</CalculationReference>
<CalculationType>Member</CalculationType>
<Description>My Calc Member Description</Description>
</CalculationProperty>
</CalculationProperties>
</MdxScript>
</MdxScripts>

One should use caution editing the files directly though.

Thank you for mentioning this, we will consider exposing this in the UI in next version.

Hope this helps,

Description for Calculated Measures?

Hi,

Hello

It is perfectly possible in MSAS 2005,You can go to the Script View of calculated Measure and you can add the description there

Thx and regards

Pankaj

|||

Pankaj,

Thanks,

|||

hello Thomas,

indeed, it looks like there is an omission in the UI, and setting description is not currently exposed.

Below is a sample of the script with a single Calculated Member calculation and a Description set for it.

One should use caution editing the files directly though.

Thank you for mentioning this, we will consider exposing this in the UI in next version.

Hope this helps,

Description field in Subscriptions Table

The Description field in SQL Server 2005 Reporting Services just defaults to "Send e-mail to email@.domain.com" (obviously a dummy e-mail address) when you create an e-mail subscription. You cannot edit the Description when you select "Edit" beside a subscription.

The Description may be edited directly in the Subscriptions table under the ReportServer database but this is not end-user friendly.

I thought of using an add/update trigger to set the Description to the "Subject" out of the Extension Settings field. The Extension Settings field is XML so you would have to parse the Subject out of there first. The "Subject" is the e-mail Subject for the e-mail that is sent to the subscriber and it much more adequately describes the report.

My boss understood what I wanted to do but wanted to make sure in the industry literature that the product was not that lacking. Hard to believe that you cannot directly edit the Subscription Description through the web browser interface - would love for someone to prove me wrong.

Hello,

I'm wondering why you are wanting to change the description of a subscription? The description tells you what the subscription does, "Send email to..." for emails, or "Save as..." for files.

For adding a description to the report, you could set it in the properties of the report itself.

You can change the description directly, but it is reset after the subscription is updated.

Jarret

|||

Well, the reason that I want to change the Subscription Description is that I have ten of them that say the same thing - you cannot tell one from the other unless you click on edit. This is not the Report Description

What we are going to do is add a trigger that fires when an update or add takes place and we will set the description equal to the parsed subject from the Extension Settings. Well, unless someone comes up with a better idea.

Thank you very much for responding.

William

|||I have solved the problems by modifying the CreateSubscription and UpdateSubscription stored procedures so that they parse the Subject out of the ExtensionSettings column and then set the Description equal to the parsed substring.sql

Description field

Getting an error on the following SQL. The field in question is the Description field which has * in the description. Not sure how I should have the SQL to solve this

UPDATE Taylors
SET Area=::Area::,Avail=::Avail::,Address=::Address::,Type=::Type::,Price=::Price::,Bedrooms=::Bedrooms::,HotProps=::HotProps::,Office=::Office::,Description=::Description::
WHERE RefNo =::RefNo::

Database Results Error
Description: [Microsoft][ODBC Microsoft Access Driver] Syntax error (missing operator) in query expression '* modern retirement flat * double bedroom * south lounge * fitted kitchen * good size bathroom * communal gardens * residence parking *'.
Number: -2147217900 (0x80040E14)
Source: Microsoft OLE DB Provider for ODBC DriversCan you show the UPDATE command as it appears just before you send it? I have no idea what you mean by ::Area::, etc. Are these strings? Do you enclose literal strings in single quotes?

If you use parameters instead of doing whatever you are doing (Search and Replace?) things will go lots easier.

http://aspnet101.com/aspnet101/tutorials.aspx?id=1

Description Column in Table Creation

Hello,
When you add a column you can put in a description. What
is the maximum size of this ?
Thanks
Peteruse extended properties, plenty of help in BOL
regards,
mark baekdal
www.dbghost.com
>--Original Message--
>Hello,
>When you add a column you can put in a description. What
>is the maximum size of this ?
>Thanks
>Peter
>.
>|||From BOL
[ @.value = ] { 'value' }
Is the value to be associated with the property. value is sql_variant, with
a default of NULL. The size of value may not be more than 7,500 bytes;
otherwise, SQL Server raises an error.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:0c8801c3d5de$45f3d6d0$a101280a@.phx.gbl...
> Hello,
> When you add a column you can put in a description. What
> is the maximum size of this ?
> Thanks
> Peter|||Thanks Guys
>--Original Message--
>Hello,
>When you add a column you can put in a description. What
>is the maximum size of this ?
>Thanks
>Peter
>.
>

Describing a table structure

Hi Jig,
I too had the same problem, coming from an Oracle
background. The SQL Server equivalent of 'desc' is
sp_help, followed by the table name in single quotes.
e.g. To descibe the table employees in the Northwind
database:
Use Northwind
sp_help 'employees'
This give the same info as the Oracle 'desc'
Mark

>--Original Message--
>Hi,
>I would like to know the syntax in MS SQL 2K for
describing a table, without
>having to expand everything in the object browser.
>I know in Oracle it is: desc <table_name>;
>Thanks,
>Jig.
>.
>
Thanks.
"Mark Laffey" wrote:

> Hi Jig,
> I too had the same problem, coming from an Oracle
> background. The SQL Server equivalent of 'desc' is
> sp_help, followed by the table name in single quotes.
> e.g. To descibe the table employees in the Northwind
> database:
> Use Northwind
> sp_help 'employees'
> This give the same info as the Oracle 'desc'
> Mark
> describing a table, without
>

Describing a table structure

Hi,
I would like to know the syntax in MS SQL 2K for describing a table, without
having to expand everything in the object browser.
I know in Oracle it is: desc <table_name>;
Thanks,
Jig.
Do you mean
sp_help tblname
"Jig Bhakta" wrote:

> Hi,
> I would like to know the syntax in MS SQL 2K for describing a table, without
> having to expand everything in the object browser.
> I know in Oracle it is: desc <table_name>;
> Thanks,
> Jig.
|||is that the only way?
"Nigel Rivett" wrote:
[vbcol=seagreen]
> Do you mean
> sp_help tblname
> "Jig Bhakta" wrote:
|||This will create a script for it
http://www.mindsdoor.net/DMO/DMOScripting.html
and this will do a database or all databases on a server
http://www.mindsdoor.net/DMO/DMOScriptAllDatabases.html
Nigel Rivett
www.nigelrivett.net
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Hi,
there may be other ways, but this gives the info in more
or less the same format as you get in Oracle. Just make
sure that you select 'Results in grid' from the Query tab.
Jig,
that is the correct format
Mark
[vbcol=seagreen]
>--Original Message--
>is that the only way?
>"Nigel Rivett" wrote:
describing a table, without
>.
>

describe table

Oracle has describe table, which will return the SQL Definition of that tabl
e...what is the equivalent in MSSQL? I am aware of sp_help table, but that d
oesn't cut it.
I want to create a table using one of the various GUI tools that are "out th
ere" but I then want to save the resulting SQL DDL, so that I can script fut
ure database creates/drops/etc.
Any help appreciated.
BOBBoth Query Analyzer and Enterprise Manager can script DDL from an existing
objects. EM also allows you to save DDL scripts when creating or modifying
objects via the 'save change script' button.
Hope this helps.
Dan Guzman
SQL Server MVP
"bob" <bob@.discussions.microsoft.com> wrote in message
news:BA0FCA03-FD78-4845-9655-00CE08A5B290@.microsoft.com...
> Oracle has describe table, which will return the SQL Definition of that
table...what is the equivalent in MSSQL? I am aware of sp_help table, but
that doesn't cut it.
> I want to create a table using one of the various GUI tools that are "out
there" but I then want to save the resulting SQL DDL, so that I can script
future database creates/drops/etc.
> Any help appreciated.
> BOB|||If you use Enterprise Manager (one of those various GUI tools ;-)) you can
generate a create table script with the third button from the left.
Jacco Schalkwijk
SQL Server MVP
"bob" <bob@.discussions.microsoft.com> wrote in message
news:BA0FCA03-FD78-4845-9655-00CE08A5B290@.microsoft.com...
> Oracle has describe table, which will return the SQL Definition of that
table...what is the equivalent in MSSQL? I am aware of sp_help table, but
that doesn't cut it.
> I want to create a table using one of the various GUI tools that are "out
there" but I then want to save the resulting SQL DDL, so that I can script
future database creates/drops/etc.
> Any help appreciated.
> BOB|||Query Analyzer will script any table individually. Just right-click on the
table in the Object Browser and select Script to New Window As > Create.
Enterprise Manager will allow you to script multiple objects to a single
file or script an entire database if you wish.
David Portas
SQL Server MVP
--|||Thanks...I was hoping for a non EM solution...a simple bit of SQL (actually,
I am using MSDE, so EM is not an option...)
Cheers,
BOB
"Jacco Schalkwijk" wrote:

> If you use Enterprise Manager (one of those various GUI tools ;-)) you can
> generate a create table script with the third button from the left.
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "bob" <bob@.discussions.microsoft.com> wrote in message
> news:BA0FCA03-FD78-4845-9655-00CE08A5B290@.microsoft.com...
> table...what is the equivalent in MSSQL? I am aware of sp_help table, but
> that doesn't cut it.
> there" but I then want to save the resulting SQL DDL, so that I can script
> future database creates/drops/etc.
>
>|||Bob,
There's no TSQL out-of-the-box option to get the CREATE TABLE statement for
an existing table. There are bunch
of options, both GUI, client code and TSQL code, however. You might want to
start at:
http://www.karaszi.com/sqlserver/in...rate_script.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"bob" <bob@.discussions.microsoft.com> wrote in message
news:A51ADE49-037D-4CD6-85AB-E169CB524DAF@.microsoft.com...
> Thanks...I was hoping for a non EM solution...a simple bit of SQL (actually, I am
using MSDE, so EM is not
an option...)[vbcol=seagreen]
> Cheers,
> BOB
> "Jacco Schalkwijk" wrote:
>|||One of the ten commandments at our shop is to SCRIPT EVERYTHING.
That means we make a TEXT file with an extension of .SQL and put our TABLE c
reate right in there. We building indexes and constraints right in that scr
ipt. We have control over naming our indexes.
We script STORED PROCEDURE creation. We script the GRANTing of rights to SP
ROCS in the same script.
Changes made in the GUI can get lost and never make it to production servers
.
Having EM or QA create a script from the database is flawed - it doesn't hav
e everything associated with that table or sproc...
At least that's the way we do it - and it's been very successful in a rapid
development/get the software to the customer scenario over the past 3 years.
"David Portas" wrote:

> Query Analyzer will script any table individually. Just right-click on the
> table in the Object Browser and select Script to New Window As > Create.
> Enterprise Manager will allow you to script multiple objects to a single
> file or script an entire database if you wish.
> --
> David Portas
> SQL Server MVP
> --
>
>sql

Thursday, March 29, 2012

Deserialization failed: The type initializer for 'Microsoft.ReportDesigner.Drawing.RptStyle

Deserialization failed: The element has invalid child element

Deserialization Failed: Parent Columns and Child Columns don't have type-matching columns.

Deserialization Failed: Parent Columns and Child Columns don't have type-matching columns.

Deserialization failed: File or assembly name Microsoft.ReportingServices.Interfaces not f

Deserialization failed: error message

Deserialization failed error. Trying to automate an RDL file.

Deserialization failed error

Deserialization Failed - Microsoft Analysis Service

Deserialization failed - how to fix?

Deserialization failed

Deserialization failed

Deserialization failed

Descriptions on databases

Description: String cannot have zero length. Event ID: 6003

Description Metadata

Description for fill factor on index rebuild maint plan misleading

Description for fill factor on index rebuild maint plan misleading

Description for Configuration Values

Description for Configuration Values

Description for Configuration Values

Description for Configuration Values

Description for Calculated Members

Description for Calculated Measures?

Description for Calculated Measures?

Description field in Subscriptions Table

Description field

Description Column in Table Creation

Describing a table structure

Describing a table structure

describe table

Sql Advice

Blog Archive

About Me