IE7 + ReportViewer: cuts off export and zoom drop downs

As I recall, this was a known issue that was meant to be resolved with a future release of IE7. Is there any update on this one or known work-a-round? Thankswas able to resolve via css

IE 7.0.5335.5 Beta 2 and SSRS 2000

Hi,
I'm trying to track and issue with IE 7 and reporting services.
First off, the report export to Excel works fine using IE 6
In IE 7 when I initially generate the report from a link in our website, the
report comes up correctly, but when I attempt to export that report to xls,
PDF, TIFF, HTML, etc I get an error that says:
"Internet Explorer cannon download Format=EXCEL from 192.168.0.250.
Internet Explorer was unable to open this Internet Site. The requested site
is either unavailable or cannot be found. Please try again later."
The site and format that it is trying to download is correct, but the
Certificate on the site is not working right (Known issue on our end). I
have added this site to the "Trusted Sites" under Internet Explorer"
Security.
Does anyone have a clue where this could come from?
Thanks
TrentAre you using SSL?
I had the same problem and found this topic which fixed my problem :
http://groups.google.co.nz/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/739f695f20237190/199c56a3165f6735?q=https&rnum=2#199c56a3165f6735|||That fixed it! Thank you for your response.
FYI - Solution is to uncheck "Do not save encrypted pages to disk"
This may be a long term security issue, but that is for another discussion.
Thanks again,
TTU
"CPNZ" wrote:
> Are you using SSL?
> I had the same problem and found this topic which fixed my problem :
> http://groups.google.co.nz/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/739f695f20237190/199c56a3165f6735?q=https&rnum=2#199c56a3165f6735
>sql

Identity field settings not copied by Import Wizard (2005)

It appears that when you use the import/export wizard from within Microsoft SQL Server Managment Studio, the identity attributes of the table being copied are not transferred. For example, say the source table has a column

[ref] [int] IDENTITY ( 1 , 1 ) NOT NULL,

When the import wizard is done the destination table will have a column named ref, but will not be an identity column. The column definition will be

[ref] [int] NOT NULL,

instead. Is there a way to change this behavior somewhere in the gui? When doing the import, the only options seems to be 'Enable Identity Insert', but checking this does not affect the definition of the column.

-Eric

Hi Eric,

Did you ever find a solution to this? Do you know if this is due to a bug that is being addressed in sp1? Thanks.

Ryan|||

I too have noticed this problem. I've installed SP1 and ticked the relevant Identity box but still does not create the Identity Columns.

Please help or sugest a workaround.

Thanks

Mark

|||If these is a copy of a database from one SQl Server to another, then I suggest looking at using the Copy Database Wizard instead of the Import/Export Wizard. The problem you might be hitting is that the IE wizard is generic, it works with any source/dest via OLE DB/ODBC and I am pretty sure that the identity property is not reported through those APIs. If you use Copy Database Wizard it is SQL to SQL only and hence can be more aware.|||If the target DB is SQL 2000, Copy Database is no good.|||

Did you find any way to copy the identity columns from Sql 2005 to Sql 2000?

Need help ASAP

Thanks

Black.

Identity field settings not copied by Import Wizard (2005)

It appears that when you use the import/export wizard from within Microsoft SQL Server Managment Studio, the identity attributes of the table being copied are not transferred. For example, say the source table has a column

[ref] [int] IDENTITY ( 1 , 1 ) NOT NULL,

When the import wizard is done the destination table will have a column named ref, but will not be an identity column. The column definition will be

[ref] [int] NOT NULL,

instead. Is there a way to change this behavior somewhere in the gui? When doing the import, the only options seems to be 'Enable Identity Insert', but checking this does not affect the definition of the column.

-Eric

Hi Eric,
Did you ever find a solution to this? Do you know if this is due to a bug that is being addressed in sp1? Thanks.
Ryan
|||

I too have noticed this problem. I've installed SP1 and ticked the relevant Identity box but still does not create the Identity Columns.

Please help or sugest a workaround.

Thanks

Mark

|||If these is a copy of a database from one SQl Server to another, then I suggest looking at using the Copy Database Wizard instead of the Import/Export Wizard. The problem you might be hitting is that the IE wizard is generic, it works with any source/dest via OLE DB/ODBC and I am pretty sure that the identity property is not reported through those APIs. If you use Copy Database Wizard it is SQL to SQL only and hence can be more aware.|||If the target DB is SQL 2000, Copy Database is no good.
|||

Did you find any way to copy the identity columns from Sql 2005 to Sql 2000?

Need help ASAP

Thanks

Black.

Identity field settings not copied by Import Wizard (2005)

It appears that when you use the import/export wizard from within Microsoft SQL Server Managment Studio, the identity attributes of the table being copied are not transferred. For example, say the source table has a column

[ref] [int] IDENTITY ( 1 , 1 ) NOT NULL,

When the import wizard is done the destination table will have a column named ref, but will not be an identity column. The column definition will be

[ref] [int] NOT NULL,

instead. Is there a way to change this behavior somewhere in the gui? When doing the import, the only options seems to be 'Enable Identity Insert', but checking this does not affect the definition of the column.

-Eric

Hi Eric,
Did you ever find a solution to this? Do you know if this is due to a bug that is being addressed in sp1? Thanks.
Ryan
|||

I too have noticed this problem. I've installed SP1 and ticked the relevant Identity box but still does not create the Identity Columns.

Please help or sugest a workaround.

Thanks

Mark

|||If these is a copy of a database from one SQl Server to another, then I suggest looking at using the Copy Database Wizard instead of the Import/Export Wizard. The problem you might be hitting is that the IE wizard is generic, it works with any source/dest via OLE DB/ODBC and I am pretty sure that the identity property is not reported through those APIs. If you use Copy Database Wizard it is SQL to SQL only and hence can be more aware.|||If the target DB is SQL 2000, Copy Database is no good.
|||

Did you find any way to copy the identity columns from Sql 2005 to Sql 2000?

Need help ASAP

Thanks

Black.

Identity field settings not copied by Import Wizard (2005)

It appears that when you use the import/export wizard from within Microsoft SQL Server Managment Studio, the identity attributes of the table being copied are not transferred. For example, say the source table has a column

[ref] [int] IDENTITY ( 1 , 1 ) NOT NULL,

When the import wizard is done the destination table will have a column named ref, but will not be an identity column. The column definition will be

[ref] [int] NOT NULL,

instead. Is there a way to change this behavior somewhere in the gui? When doing the import, the only options seems to be 'Enable Identity Insert', but checking this does not affect the definition of the column.

-Eric

Hi Eric,
Did you ever find a solution to this? Do you know if this is due to a bug that is being addressed in sp1? Thanks.
Ryan
|||

I too have noticed this problem. I've installed SP1 and ticked the relevant Identity box but still does not create the Identity Columns.

Please help or sugest a workaround.

Thanks

Mark

|||If these is a copy of a database from one SQl Server to another, then I suggest looking at using the Copy Database Wizard instead of the Import/Export Wizard. The problem you might be hitting is that the IE wizard is generic, it works with any source/dest via OLE DB/ODBC and I am pretty sure that the identity property is not reported through those APIs. If you use Copy Database Wizard it is SQL to SQL only and hence can be more aware.|||If the target DB is SQL 2000, Copy Database is no good.
|||

Did you find any way to copy the identity columns from Sql 2005 to Sql 2000?

Need help ASAP

Thanks

Black.

IDENTITY Column!

Hi all,
I have noticed when i export data, that any resulting tables created don't
seem to include the IDENTITY attribute on the necessary columns.
These attributes are defined in the source tables, but don't carry over to
tables resulting from an export.
Can someone fill me in on what is happening there?
Is there something i could be missing?
Cheers,
AdamAdam
create table source
(
col1 int identity(1,1) not null primary key,
col2 char(1)
)
insert into source (col2) values ('a')
--create a destination table
select * into destination from source
--you will see that an identity property exists but primary key constraint
doesn't
"Adam Knight" <adam@.pertrain.com.au> wrote in message
news:exS9CWHAGHA.3372@.TK2MSFTNGP12.phx.gbl...
> Hi all,
> I have noticed when i export data, that any resulting tables created don't
> seem to include the IDENTITY attribute on the necessary columns.
> These attributes are defined in the source tables, but don't carry over to
> tables resulting from an export.
> Can someone fill me in on what is happening there?
> Is there something i could be missing?
> Cheers,
> Adam
>|||By which method do you export data?|||By which method do you export data?

Identity Column Property SQL SERVER

hi

i export tables from Local to Online Server But some tables have a column with Identity=True

But after export tables that Property is not True How I can change it True With Query Analyzer????/

Would it be possible at all to do a 'create sql scripts' on the database, and use the scripts on the live server to recreate your tables? This should fix your problem.