| Author |
 Topic  |
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
 Posted - 04 March 2007 : 06:15:01
|
quote:
Originally posted by Steve B
I've downloaded and installed the evaluation version of SQL Server 2005. It's good for six months, which ought to get me past this upgrade thing!  BTW, I don't see Enterprise Manager, but there is a "MS SQL Server Management Studio." It doesn't seem to map well to the descriptions given here, but I'm hoping I can make it work. Or am I missing something really big here?
EM has been replaced by Management Studio in SQL Server 2005.
quote:
I hate to admit it, but I'm stumped. I do not have login access to these servers, only http, ftp, and whatever SQL EM (or SMS) uses. The Access and SQL databases are on different servers. The current connect string for the Access database is obviously not usable, since it's based on the local disk layout - e:\something\or\other\whatever.mdb. Can I specify the IP address and get to it somehow? (Oddly, when I try to browse to the database or the whereami.asp file in the same directory, I get a "The requested resource could not be found" error.) Anyway, I'm not sure how to connect.
You just need FTP access. You should find the folder where your database is located by loooking at the last couple folders in the path for the Access Db in the connection string. When you connect using FTP you will be at the root of your hosting space, and likely that's where you need to start looking for the path to the Access DB. That DB is in there, in one of those folders, so just compare the path you have in the connection string with that folder structure and you will find it.
< |
Snitz 3.4 Readme | Like the support? Support Snitz too |
 |
|
|
Steve B
Starting Member
11 Posts |
Posted - 04 March 2007 : 14:10:57
|
quote:
Originally posted by ruirib
EM has been replaced by Management Studio in SQL Server 2005.
OK, that helps, so at least I know I'm in the ballpark.
quote:
You just need FTP access. You should find the folder where your database is located by loooking at the last couple folders in the path for the Access Db in the connection string. When you connect using FTP you will be at the root of your hosting space, and likely that's where you need to start looking for the path to the Access DB. That DB is in there, in one of those folders, so just compare the path you have in the connection string with that folder structure and you will find it.
OK, I was thinking I had to connect to the Access database across the Net from within Management Studio. But I have FTP access to it, so I can download it and use the local copy.
It's taken me a while, digging through the MS menus, but I finally found where the "import data" function is, so I think I'm going to try and give it a shot tonight.
Thanks for all the help!
Steve< |
|
|
|
Steve B
Starting Member
11 Posts |
Posted - 04 March 2007 : 15:17:49
|
quote:
Originally posted by Carlos Miranda Levy
10. Import the data from the Access database (follow carefully)
g) Review settings for the destination database.
- In Destination, choose Microsoft OLE DB Provider for SQL Server (should be chosen for you already).
- Server: Indicate your MS SQL Server name, IP or if you are on the machine like me, choose local.
- Use Windows Authentication: Important, do not use SQL Server Authentication and the login/password you created for your connection script, or you will end up creating another set of tables.
I'm up to this point and running into another problem. The instructions say to use Windows authentication, but I'm attaching to a remote database where I do not have a Windows account. If I try to connect, I get the error below. If I try to use SQL Server Authentication with the database user name and password, I run into the errors described in the subsequent steps, e.g. the "Delete rows in destination table" option is not available.
How do I proceed from here?
Thanks,
Steve< |
Edited by - Steve B on 04 March 2007 17:27:25 |
|
|
|
AnonJr
Moderator
United States
5768 Posts |
Posted - 04 March 2007 : 16:39:57
|
Might want to edit out the IP addy for your database.... just thinkin...  < |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
|
Steve B
Starting Member
11 Posts |
Posted - 04 March 2007 : 21:16:37
|
quote:
Originally posted by ruirib
Looks like that server is only configured to support Windows authentication... you may take up that issue with your host.
No, my point is that Carlos' instructions specifically say to use only Windows Authentication. I am able to authenticate using SQL Server Authentication, but according to the instructions, that would cause errors later on. I tried, and I saw the problems he described, so I backed out.
It appears that the instructions are based on having a local login to the server, which may be not that common a scenario. In which case, what options do I have?< |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
|
Steve B
Starting Member
11 Posts |
Posted - 05 March 2007 : 05:39:01
|
quote:
Originally posted by ruirib
You need to use SQL Server authentication. What problems are yiu talking about?
Step 10 g) specifically says not to use SQL Server Authentication, because that will result in creating another set of tables.
Following that, Step 10 l) says to choose "Delete rows in destination table" and "Enable identity insert". If I do use SQL Server Authentication, it appears that the "Delete rows in destination table" option is not available.
< |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 05 March 2007 : 06:12:47
|
If you have executed setup.asp, the tables will have been created, even if with another schema. The schema name in use will be your SQL Server username, quite likely. You can find the schema by looking at the tables in EM - each table will show as 'schema_name.tablename'.
What I suggest you to do is to highlight all the tables in the transfer dialog, by clicking the all check box and the clicking the first and then press shift and click the last table in the list, then click Edit Mappings. This will allow you to define the schema once for all the tables, and you need to choose the schema in which your tables were created in. You need to also check identity insert and it will be done for all tables.
Alternatively, you can specify the proper schema individually, for each table. For that, just click the dropdown at the destination table in question and it will allow you to see the existing possibilities for destination table, including the right table, in the schema in which the setup script created it.< |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
Steve B
Starting Member
11 Posts |
Posted - 05 March 2007 : 17:43:24
|
OK, this is making sense now. I didn't realize you could go through, table by table, and select the existing tables to use rather than creating new ones. It's a chore, but it works. 
I'll have to schedule another outage, but I think I've got it now. Thank you so much!
Steve< |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 05 March 2007 : 18:04:58
|
| You don't even need to go one by one. By selecting all the tables, as I explained, and then click Edit Mappings, you can define the schema once for all the tables. It's that simple.< |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
Steve B
Starting Member
11 Posts |
Posted - 07 March 2007 : 07:57:12
|
quote:
Originally posted by ruirib
You don't even need to go one by one. By selecting all the tables, as I explained, and then click Edit Mappings, you can define the schema once for all the tables. It's that simple.
If there were an Edit Mappings button, I would be glad to do click on it. (I take no particular pleasure in doing things the hard way. That's why we have computers.) I'm using SQL Server 2005 Management Studio, and apparently someone decided that the Edit Mappings button was no longer necessary.< |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
|
Steve B
Starting Member
11 Posts |
Posted - 07 March 2007 : 14:43:52
|
Interesting. I do not see that. I have everything else, but no Edit Mappings.
Maybe it's a version difference. Or the fact that I have an evaluation version. Here's the info from the About box:
Microsoft SQL Server Management Studio (expires in 176 days) 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600
< |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 07 March 2007 : 15:59:56
|
Seems like my versions are more up to date:
Microsoft SQL Server Management Studio 9.00.2047.00
Microsoft Analysis Services Client Tools 2005.090.2047.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.91
Operating System 5.1.2600
< |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
Topic |
|
Topic Locked
<