Question about SQL

Hi all,

I have created a photo album in my local computer with [Microsoft Visual Web Developer 2005 Express Edition] my data base is SQL I built it with the same program. Also, I used the ASP.net Configuration to setup the user's account, every thing working 100% in my local computer.

I have an account with www. Hostonce .com they offer and support MS SQL 2005 and ASP.net, and they gave me an IP number to access to my MSSQL server with [SQL Server Management Studio Express], I do access when I put the IP address and the password, but I have no idea how to move the entire project with the SQL files to my server. I tried to transfer all my files with FTP, but it didn't work, they told me I have to transfer my SQL to the same IP address and then I have to do the connection things in my pages.

Please Help.

Thank You

Ok, you'll need to migrate the database from Express Edition to the MS SQL 2005 if they don't provide the Express Edition.|||

I think they support only MS SQL 2005 , but would you mind to tell me how i can solve this problem and how i can migrate the database from Express Edition to the MS SQL 2005 ?

Thank You,

|||If you don't have Studio to connect to both databases to do the migration. You can ask your hosting company to do the migration for you. Some hosting companies will do that for you

Question about converting bigint field to int field

We made a poor decision a long time ago when designing our database
structure. We used bigint data types as the identity keys for many of
our base tables. For many reasons I would like to change these fields
to int at the largest. The largest data in these fields is around
200,000. I know that int can easily store this.

What should I be worried about when changing these fields from bigint
to int? If anything. Your help is appreciated. I did several
searches without much luck.I think you've covered the one biggy - make sure your existing data will
fit!

Others...

a) Make sure anything you join with are the same type, basically make
sure you change it everywhere including your foreign keys table.
b) Remember to do the stored procedures, udfs, triggers that may use them
as parameter.
c) You'll need to drop any constraints on your column definied with the
identity property, see example problem...

drop table t

create table t (
mycol bigint identity primary key,
t char(1) )

insert t ( t) values( 'a' )

alter table t alter column mycol int not null

Tony.

--
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials

<mamorgan1@.gmail.com> wrote in message
news:1137768775.133857.115810@.g44g2000cwa.googlegr oups.com...
> We made a poor decision a long time ago when designing our database
> structure. We used bigint data types as the identity keys for many of
> our base tables. For many reasons I would like to change these fields
> to int at the largest. The largest data in these fields is around
> 200,000. I know that int can easily store this.
> What should I be worried about when changing these fields from bigint
> to int? If anything. Your help is appreciated. I did several
> searches without much luck.|||Just curious... What problems are there with having bigint as an
identity column?|||There aren't any problems - it works just fine.

--
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials

"pb648174" <google@.webpaul.net> wrote in message
news:1138052526.544803.80680@.z14g2000cwz.googlegro ups.com...
> Just curious... What problems are there with having bigint as an
> identity column?|||I think its because
Bigint takes 8 bytes storage and Int takes 4 bytes.
SQL Server will not automatically promote other integer data types
(tinyint, smallint, and int) to bigint.

Regards
Amish Shah|||> What problems are there with having bigint as an identity column?

extra storage space causing slower performance of everything