Converting Access 2000 to SQL

Ok, I finally figured out SQL somewhat. I cannot upsize all of my databases using the upsize wizard provided with Access 2000. I can upsize some database, but most importantly, not the one I need to upsize. Does anybody have any idea why some would upsize and some wouldn't? Could it be a problem with linked tables? OR is there any other way of converting the access databases into SQL databases for SQL Server 2000? Remember, I am a very first time SQL user.
Thanks a lot,
Aaron Shoverwith SQL Server a very handy tool is delivered: Data Transformation Services (DTS). You can use DTS to transform data from one source to another for all major databases, office applications, text files and more. If you are willing to convert to SQL Server this is probably the way to go. You can search in the Books Online for more info.
You can also set up your Access databases as linked servers to access them from SQL server, but conversion is probably better.|||I found the DTS and I used it. Now, this database has a front end and a backend. When I transferred the front end all it allowed me to transfer were the queries. So then I had to go to the back end and transfer the backend in order to transfer the tables. I assume this is because of the database being split, and if it wasn't it would allow me to do both at the same time?|||well the tables aren't located in the front end - how can they be transferred??

They are only *linked* to the tables in the back end.|||That's what I thought; I just wanted conformation so I understand everything that is going on.

Convert SqlExpress to Sql 2000

Some thread searches here say conversion (downgrade) of a SqlExpress database to Sql Server 2000 is trivial. I haven't yet figured out an efficient way of doing so beyond using someone's Database Publishing Wizard utility (http://www.codeplex.com/sqlhost) to create a sql 2000 compatible script, replete with schema *and* data, then running that script against the Sql 2000 database (freshly created without any structure). I've done this successfully with smaller databases, but the larger ones really tax and drain the server resources and scripts have failed with "out of memory" errors. We're putting more memory in the Sql 2000 server, which may avert memory errors, but there's still the issue of server load. Has anybody since come up with or know of a better method that's quicker, more efficent and less drain on the server?

TIA,

Rick
Nevermind. Was able to use 2000's DTS in conjunction with Database Publishing wizard. Much faster and easier on the server than INSERT scripts.

Convert SqlExpress to Sql 2000

Some thread searches here say conversion (downgrade) of a SqlExpress database to Sql Server 2000 is trivial. I haven't yet figured out an efficient way of doing so beyond using someone's Database Publishing Wizard utility (http://www.codeplex.com/sqlhost) to create a sql 2000 compatible script, replete with schema *and* data, then running that script against the Sql 2000 database (freshly created without any structure). I've done this successfully with smaller databases, but the larger ones really tax and drain the server resources and scripts have failed with "out of memory" errors. We're putting more memory in the Sql 2000 server, which may avert memory errors, but there's still the issue of server load. Has anybody since come up with or know of a better method that's quicker, more efficent and less drain on the server?

TIA,

Rick
Nevermind. Was able to use 2000's DTS in conjunction with Database Publishing wizard. Much faster and easier on the server than INSERT scripts.

Convert Date Format from 23 Aug 07 to mm-dd-yy

I have this stored procedure, and im trying to figured out how i can convert the date field into something i can actually sort in the right order in reporting services. Such as mm-dd-yy , whats the SQL code for doing that?

Give a look to the CONVERT-->CAST AND CONVERT article in books online; there is a section that deals with particular format flavors for DATE/TIME datatypes. The mm/dd/yyyy format is the "101" flavor. That function reference will look something like:

CONVERT(VARCHAR(10), yourDateVar, 101)

|||

I just realized this month comes from a view that has month put together by two fields. It looks like this

CONVERT(char(12), DATEADD(day, dbo.question_history.cycle_day - 1, dbo.period.start_date)

The period starte date looks like this 2007-07-16 00:00:00.000

The date is actually the period start date plus + the cycle day - 1. ITs confusing i know. So how come when i try to edit the date it wont let me, i get this 39280 for some weird reason.