Extra White Space

Hi All,
I've got a report that is set up with the Report Properties layout as
follows: page width = 8.5in; page height = 11in; left/right margins = .25in;
top/bottom margins = .50in.
When the report displays in IE7, there is a large white area (blank) to the
right of the report and it's full length. When I export as a PDF document,
this area seems to cause extra pages to be created in the PDF output.
Since I'm not sure "why" this extra white space is appearing, I thought I'd
post this here.
Thanks in advance!
Kind regards - FredHi Fred,
I've found, that meters of extra white space on the right side, before all
when viewed in HTML, are created when there are overlapping visible textboxes.
When textboxes overlap where one is invisible, there are also minor layout
differences, but never so dramatically.
Yours, Henry

Exterprise manager

On my SQL 2000 server I can no longer view the server properties with
Enterprise manager.
The properties page just flashes up and disappears.
No errors in the Event logs.
Does anyone have any suggestions about how I might overcome the problem.
Regards Craig.I remember seeing this a while ago. What SQL Server service pack is
installed on this client? Could you upgrade it so that it matches the SP
version of server?
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
What hardware is your SQL Server running on?
http://vyaskn.tripod.com/poll.htm
"Craig Leslie" <craigl@.cil.com.au> wrote in message
news:utz2Y6nUDHA.1276@.TK2MSFTNGP09.phx.gbl...
On my SQL 2000 server I can no longer view the server properties with
Enterprise manager.
The properties page just flashes up and disappears.
No errors in the Event logs.
Does anyone have any suggestions about how I might overcome the problem.
Regards Craig.|||Hi Craig,
This issue maybe caused by the MSSQLServer service startup accout lacking
of permission to access some registry keys. You may try to add the startup
account to local admin group, and then stop and restart the service to see
if it works.
This posting is provided "AS IS" with no warranties, and confers no rights.
Sincerely,
William Wang
Microsoft Partner Online Support
--
| Reply-To: "Craig Leslie" <craigl@.cil.com.au>
| From: "Craig Leslie" <craigl@.cil.com.au>
| Subject: Exterprise manager
| Date: Fri, 25 Jul 2003 15:27:20 +0800
| Lines: 12
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <utz2Y6nUDHA.1276@.TK2MSFTNGP09.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: cilfsrv1.cil.com.au 203.38.62.194
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.server:297767
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| On my SQL 2000 server I can no longer view the server properties with
| Enterprise manager.
|
| The properties page just flashes up and disappears.
|
| No errors in the Event logs.
|
| Does anyone have any suggestions about how I might overcome the problem.
|
| Regards Craig.
|
|
|

Extended properties created by Visual Studio on CLR UDF''s

When one deploys a CLR DLL that contains [SqlFunction]'s, Visual Studio creates three extended properties on the SQL function that is created: these are,

AutoDeployed, SqlAssemblyFile, SqlAssemblyFileLine.

What I haven't found anywhere on Help or MSDN online is what these extended properties mean.

Could someone enlighten me?

1. What is a description of the above properties?

2. What is the benefit of using them (clearly the function works without using them). Does it help debugging?

3. Does the developer need to manually keep for instance the SqlAssemblyFileLine in sync with changes in the .NET code?

Thanks a lot.

Aneela_B wrote:

When one deploys a CLR DLL that contains [SqlFunction]'s, Visual Studio creates three extended properties on the SQL function that is created: these are,

AutoDeployed, SqlAssemblyFile, SqlAssemblyFileLine.

What I haven't found anywhere on Help or MSDN online is what these extended properties mean.

Could someone enlighten me?

1. What is a description of the above properties?

2. What is the benefit of using them (clearly the function works without using them). Does it help debugging?

3. Does the developer need to manually keep for instance the SqlAssemblyFileLine in sync with changes in the .NET code?

AFAIK, the above properties do not have any use at the moment. They have no impact on debugging.

If you change the .NET code you have to re-deploy your assembly (either CREATE or ALTER).

Niels

Extended properties created by Visual Studio on CLR UDF''s

When one deploys a CLR DLL that contains [SqlFunction]'s, Visual Studio creates three extended properties on the SQL function that is created: these are,

AutoDeployed, SqlAssemblyFile, SqlAssemblyFileLine.

What I haven't found anywhere on Help or MSDN online is what these extended properties mean.

Could someone enlighten me?

1. What is a description of the above properties?

2. What is the benefit of using them (clearly the function works without using them). Does it help debugging?

3. Does the developer need to manually keep for instance the SqlAssemblyFileLine in sync with changes in the .NET code?

Thanks a lot.

Aneela_B wrote:

When one deploys a CLR DLL that contains [SqlFunction]'s, Visual Studio creates three extended properties on the SQL function that is created: these are,

AutoDeployed, SqlAssemblyFile, SqlAssemblyFileLine.

What I haven't found anywhere on Help or MSDN online is what these extended properties mean.

Could someone enlighten me?

1. What is a description of the above properties?

2. What is the benefit of using them (clearly the function works without using them). Does it help debugging?

3. Does the developer need to manually keep for instance the SqlAssemblyFileLine in sync with changes in the .NET code?

AFAIK, the above properties do not have any use at the moment. They have no impact on debugging.

If you change the .NET code you have to re-deploy your assembly (either CREATE or ALTER).

Niels

Extended Properties

Hi:

Does anyone know of a good primer on extended properties and why I would want to use them. I have you the on-line books sections but that does a clear "why". I have search for white papers and similar documents.

I understand they are good for documentation, but I was looking for something that explain Microsoft long-term vision. How I might use them in template scripts, VSTS, etc.

Thanks in advance for your help.

Gene

Most people tend to use them for documentation, sort of like a built-in data dictionary.

Extended Properties

I am having some wierd behavior that I can't seem to correct regarding exteneded properties. Via a T-SQL statement, I have added several exteneded properties to a table, for example:

exec sp_addextendedproperty N'AP121ID', @.value = 'AP121 Primary Key',
@.level0type = N'Schema', @.level0name = dbo,
@.level1type = N'Table', @.level1name=ap121,
@.level2type = N'Column', @.level2name=AP121ID;
GO

This statement runs successfully. I can even query the sys.extended_properties table and see the entries.

However, if i look at the properties of teh table to which I added the exteneded properties, they are not listed. Nor does it allow me to add one via that properties page.

Any ideas?

Thanks...

Scott

Looks like you are adding extended properties to the column of the table and not the table itself.

Can you check for extended properties on the table column via the properties page ?

|||Ah, yep, that was it. Thanks!

Extended Properties

I am having some wierd behavior that I can't seem to correct regarding exteneded properties. Via a T-SQL statement, I have added several exteneded properties to a table, for example:

exec sp_addextendedproperty N'AP121ID', @.value = 'AP121 Primary Key',
@.level0type = N'Schema', @.level0name = dbo,
@.level1type = N'Table', @.level1name=ap121,
@.level2type = N'Column', @.level2name=AP121ID;
GO

This statement runs successfully. I can even query the sys.extended_properties table and see the entries.

However, if i look at the properties of teh table to which I added the exteneded properties, they are not listed. Nor does it allow me to add one via that properties page.

Any ideas?

Thanks...

Scott

Looks like you are adding extended properties to the column of the table and not the table itself.

Can you check for extended properties on the table column via the properties page ?

|||Ah, yep, that was it. Thanks!

Extended Properties

When I add an extended property using SMO, it doesn't show up on the Properties of the table in SQL Management Studio. Also, if I add one in Managment Studio, I can't see it using SMO. What am I missing here?

Can you please provide some more information on how you are trying to add and retrieve the Extended Properties using SMO. And also what version of SQL Server are you using.

Your code should look similar to -

Table t = mydb.Tables["tableName"];

foreach(ExtendedProperty exp in t.ExtendedProperties)

{

Console.WriteLine(exp.Name + " " + exp.Value);

}

t.ExtendedProperties.Add(new ExtendedProperty("propertyName", "property value"));

|||My code is pretty much just like that. I am using SQL Server 2005.|||

Here is the code sample which I found working, let me know if you face any issues.

Server server = newServer("localhost");

Table table = server.Databases["mydatabase"].Tables["mytable"];

table.ExtendedProperties.Add(newExtendedProperty(table, "propertyName", "propertyValue"));

table.Alter();

table.Refresh();

foreach (ExtendedProperty e in table.ExtendedProperties)

{

Console.WriteLine(e.Name + " " + e.Value.ToString());

}

Thanks,

Kuntal

Extended Properties

When I add an extended property using SMO, it doesn't show up on the Properties of the table in SQL Management Studio. Also, if I add one in Managment Studio, I can't see it using SMO. What am I missing here?

Can you please provide some more information on how you are trying to add and retrieve the Extended Properties using SMO. And also what version of SQL Server are you using.

Your code should look similar to -

Table t = mydb.Tables["tableName"];

foreach(ExtendedProperty exp in t.ExtendedProperties)

{

Console.WriteLine(exp.Name + " " + exp.Value);

}

t.ExtendedProperties.Add(new ExtendedProperty("propertyName", "property value"));

|||My code is pretty much just like that. I am using SQL Server 2005.|||

Here is the code sample which I found working, let me know if you face any issues.

Server server = new Server("localhost");

Table table = server.Databases["mydatabase"].Tables["mytable"];

table.ExtendedProperties.Add(new ExtendedProperty(table, "propertyName", "propertyValue"));

table.Alter();

table.Refresh();

foreach (ExtendedProperty e in table.ExtendedProperties)

{

Console.WriteLine(e.Name + " " + e.Value.ToString());

}

Thanks,

Kuntal

Extend existing report items

Hi,

I'm totally new to SSRS2005 and I was wondering if I could extend the existing report items. For instance, I'd like to add a few extra properties to the textbox report item. I tried wrting a custom Textbox control that inherits from System.Windows.Forms.Textbox. When I imported the dll in VS, the new textbox showed up in the toolbox, but it was grayed out.

Any idea what I'm missing here?

Thanks,
Phil
Best off writing your own and call the RS webservice.

http://msdn2.microsoft.com/en-us/library/aa179578(SQL.80).aspx|||But I want to inherit all existing functionality of the textbox... So why would I create my own from scratch?
|||Sorry, completely barking up the wrong end of the stick.

I was on about report parameter selection.

I'm guessing you can't do it.

Use Crystal Reports instead: from what I have read on these forums, it seems to do most things that RS can't.

The only reason people use RS is because they are too tight to shell out for a decent product (this has been the case where I've worked)

RS is "free". How much time have I wasted at what cost to the companies I have worked for trying to get it to do the simplest of things. Suddenly it's not so cheap, but then MS have figured out that bean counters are incapable of factoring in all this wasted time.

If only dev's got to make the purchasing decisions......

expression to get CreatedBy, CreationDate, ModifiedBy, and ModifiedDate properties for report?

If you look at the General Properties for a report in Report Manager, there are 4 properties listed at the top:

Modified Date: 2/26/2007 6:37 PM Modified By: DOMAIN\username1 Creation Date: 2/14/2006 5:19 PM Created By: DOMAIN\username2

What I'm looking for is if there's a way to retrieve these properties via an expression from a textbox within a report. For instance, there's already an expression that is:

=Globals!ReportName

I know it won't be that easy for the CreatedBy, CreationDate, ModifiedBy, and ModifiedDate properties, but I thought I'd ask if there was a workaround or hack.

We're wanting to put that info into the footer of all our reports. (Actually this is for Report Builder reports, but you can still use expressions in Report Builder reports, so it should apply as it would to normal reports.)

Hi Greg,

I don't believe any of that information is stored in the RDL itself. The only way I know to get that information is to query the ReportServer database, similar to:

SELECT [ModifiedDate]

,[Modified].[UserName]

,[CreationDate]

,[Created].[UserName]

FROM [ReportServer].[dbo].[Catalog]

INNERJOIN [ReportServer].[dbo].[Users] as [Modified] ON [Catalog].[ModifiedByID] = [Modified].[UserID]

INNERJOIN [ReportServer].[dbo].[Users] as [Created] ON [Catalog].[CreatedByID] = [Created].[UserID]

WHERE [Catalog].Name =Globals!ReportName.Value

Then you can access those fields from the dataset.

HTH,

Jessica

Expression editor on Custom Properties on Custom Data Flow Component

Hi,

I've created a Custom Data Flow Component and added some Custom Properties.

I want the user to set the contents using an expression. I did some research and come up with the folowing:

Code Snippet

IDTSCustomProperty90 SourceTableProperty = ComponentMetaData.CustomPropertyCollection.New();
SourceTableProperty.ExpressionType = DTSCustomPropertyExpressionType.CPET_NOTIFY;
SourceTableProperty.Name = "SourceTable";

But it doesn't work, if I enter @.[System:ackageName] in the field. It comes out "@.[System:ackageName]" instead of the actual package name.

I'm also unable to find how I can tell the designer to show the Expression editor. I would like to see the elipses (...) next to my field.

Any help would be greatly appreciated!

Thank you

The expression for a component's property is held at the task level. If a property is marked as CPET_NOTIFY, it notifies the task (the data flow which parent's the component), which tells it to generate a new property on which can be set an expression. So to see the expression in the designer look at the properties grid for the data flow task, not the component.

|||Hello Darren,

Thank you for the quick response. But the expression editor doesn't show in the propertiesgrid either.

Could I be missing anything?|||

Are you looking at the properties grid of the DATA FLOW component or at your custom data flow component? Also, did you set the flag darren mentioned above so that the data flow component will know to include this property in it's properties expression list?

|||Ah, yes, I see it now. But it is not what I'm looking for.

Is there now way to set the expresison builder on the component itself? When the expression builder is used on the parent task, I cannot access the incomming rows.

Thank you kindly|||

Why do you think your component will have features over and above that available to Microsoft themselves?

Property expressions are ONLY available at the task level, because they are provided in the task framework.

You have created a property expression, so your mention of incoming rows does not make sense. Property expressions are just that, for the property, but not the value itself, the result will override the value. Just look how they work in the rest of SSIS.

A property that holds a text string that could be parsed as an expression is something different and maybe what you want? Perhaps the Derived Column transform may be easier?

Express SP1 No version #

I downloaded the SQL Server 2005 Express SP1 product today. If I right click SQLEXPR.EXE, select Properties, and select the Version tab, the File Version value is 0.0.0.0. The version listed for the GA product was 9.0.1399.6.

Is this a problem to be concerned about?

Hi,

that shouldn′t bother you, smae for me here. Look at the digital signature date, if it is sometime in April 2006 signed (as mine is) this is the right one for you. Starting the File will also come up with a EULA shwoing the Service pack Level.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

SQLEXPR.EXE is a compressed archive, you'll find version numbers on the actual files that are installed.

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

Express SP1 No version #

I downloaded the SQL Server 2005 Express SP1 product today. If I right click SQLEXPR.EXE, select Properties, and select the Version tab, the File Version value is 0.0.0.0. The version listed for the GA product was 9.0.1399.6.

Is this a problem to be concerned about?

Hi,

that shouldn′t bother you, smae for me here. Look at the digital signature date, if it is sometime in April 2006 signed (as mine is) this is the right one for you. Starting the File will also come up with a EULA shwoing the Service pack Level.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

SQLEXPR.EXE is a compressed archive, you'll find version numbers on the actual files that are installed.

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

Exporting the Table Structure...

Hye guys,
I want 2 export the field names and their properties of my tables to a file by which I would be able 2 print it , Study it and share it with my other friends... for discussions...

Which tool can be used 2 export the table stture in a printable format?

Kabin

Why don't you create a Diagram?

|||

Hi Kabin,

You have a few options depending on what you're looking for. You don't mention which version of SQL Server you have, so I'll try to provide instructions for 2000 and 2005 versions.

1. Create a script of the table's definition.

From Management Studio in Object Explorer, right-click the table and point to Script Table as and then select Create to and choose to save it to a file.

or for SQL Server 2000

From Query Analyzer, right-click the table and select Script Object to File as and then select Create.

2. Use sp_help.

From either Management Studio or Query Analyzer run the following statement.

EXEC sp_help ('your_table_name')

3. Create a database diagram.

See Books Online topics for creating database diagrams. (although your print options are somewhat limited with this).

Regards,

Gail

|||

Hi guys,
well I first tried creating diagram and then printing it. It was really litte bit some tedious work as I can only print from it. I can export it to excel or even notepad for formatting also. Diagram gave me really limited feature which is not sufficient.

Secondly I tried with SP_help. It also didn't worked.

THirdlr I tried with creating script for the object or table that worked fine but not also fully as i wanted. I just wanted the column name in left side and its properties in formatted way in right side in 2 column format but well Script also provided me some help.

Thanks Guys.

|||

Actually, sp_help should produce the information you want. Saying "It didn't work" doesn't give us much to go on to help you. Did you get an error message? If so, what was it?

You might want to query the table metadata by using the system tables (in SS 2000) or the catalog views (in SS2005). For example, in SQL Server 2005, you can write a query like the following example to return the table and column names and their properties.

SELECT o.name AS TableName,
c.name AS ColumnName,
t.name AS DataType,
c.Max_Length,
c.Precision,
c.Scale
FROM sys.objects AS o
INNER JOIN sys.columns AS c ON o.object_id = c.object_id
INNER JOIN sys.types AS t ON c.user_type_id = t.user_type_id
WHERE type = 'U'

And here's an equivalent query in SQL Server 2000.

SELECT o.name AS TableName,
c.name AS ColumnName,
t.name AS DataType,
c.length,
c.xprec,
c.xscale
FROM sysobjects AS o
INNER JOIN syscolumns AS c ON o.id = c.id
INNER JOIN systypes AS t ON c.usertype = t.usertype
WHERE o.type = 'U'

I only selected a few column properties. To see all the columns available in the system tables/views, see Books Online.

Regards,

Gail

|||

hi..Guys..

Thanks a lot ur suggestions helped me alot man...

|||

You can get the structure from the query analyser by the command --> sp_help tablename

Exporting the Table Structure...

Hye guys,
I want 2 export the field names and their properties of my tables to a file by which I would be able 2 print it , Study it and share it with my other friends... for discussions...

Which tool can be used 2 export the table stture in a printable format?

Kabin

Why don't you create a Diagram?

|||

Hi Kabin,

You have a few options depending on what you're looking for. You don't mention which version of SQL Server you have, so I'll try to provide instructions for 2000 and 2005 versions.

1. Create a script of the table's definition.

From Management Studio in Object Explorer, right-click the table and point to Script Table as and then select Create to and choose to save it to a file.

or for SQL Server 2000

From Query Analyzer, right-click the table and select Script Object to File as and then select Create.

2. Use sp_help.

From either Management Studio or Query Analyzer run the following statement.

EXEC sp_help ('your_table_name')

3. Create a database diagram.

See Books Online topics for creating database diagrams. (although your print options are somewhat limited with this).

Regards,

Gail

|||

Hi guys,
well I first tried creating diagram and then printing it. It was really litte bit some tedious work as I can only print from it. I can export it to excel or even notepad for formatting also. Diagram gave me really limited feature which is not sufficient.

Secondly I tried with SP_help. It also didn't worked.

THirdlr I tried with creating script for the object or table that worked fine but not also fully as i wanted. I just wanted the column name in left side and its properties in formatted way in right side in 2 column format but well Script also provided me some help.

Thanks Guys.

|||

Actually, sp_help should produce the information you want. Saying "It didn't work" doesn't give us much to go on to help you. Did you get an error message? If so, what was it?

You might want to query the table metadata by using the system tables (in SS 2000) or the catalog views (in SS2005). For example, in SQL Server 2005, you can write a query like the following example to return the table and column names and their properties.

SELECT o.name AS TableName,
c.name AS ColumnName,
t.name AS DataType,
c.Max_Length,
c.Precision,
c.Scale
FROM sys.objects AS o
INNER JOIN sys.columns AS c ON o.object_id = c.object_id
INNER JOIN sys.types AS t ON c.user_type_id = t.user_type_id
WHERE type = 'U'

And here's an equivalent query in SQL Server 2000.

SELECT o.name AS TableName,
c.name AS ColumnName,
t.name AS DataType,
c.length,
c.xprec,
c.xscale
FROM sysobjects AS o
INNER JOIN syscolumns AS c ON o.id = c.id
INNER JOIN systypes AS t ON c.usertype = t.usertype
WHERE o.type = 'U'

I only selected a few column properties. To see all the columns available in the system tables/views, see Books Online.

Regards,

Gail

|||

hi..Guys..

Thanks a lot ur suggestions helped me alot man...

|||

You can get the structure from the query analyser by the command --> sp_help tablename