The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Urgent Help! - Cutting Remote Office Problem
Posted: 04 Feb 09 10:25 AM
|
| Can I cut a remote office db on saleslogix 7.01 with sql 2005? Or do I have to use MSDE? Here is my problem. My db size is bigger than 2 gigs and msde wont be able to handle the size. I cannot cut directly on sql 2005 cause its not supported from what I heard and when I try I get an error: Invalid object name 'sysxlogins'.. I tried cutting it on a networked full standard version of 2000 but it had problems connecting to the server to do the cut. |
|
|
|
Re: Urgent Help! - Cutting Remote Office Problem
Posted: 04 Feb 09 12:09 PM
|
| I solved the problem. I was able to cut to a 2000 standard sql server. In the MSDE instance name, put the name of the networked server without the msde instance. For example, instead of SERVER\MSDE, put SERVER only. Also, I had to create the folders on the host where the sxd file will be created because it complained it could not find it. I find it crazy that saleslogix 7.01 cannot cut remote offices bigger than 2gigs on sql 2005. |
|
|
|
Re: Urgent Help! - Cutting Remote Office Problem
Posted: 05 Feb 09 4:11 AM
|
| You are wrong. You don't need to use MSDE, SQL/E - you can use normal SQL Server and have any database size you like. If you do use them - then the database limits come from SQL not SLX (i.e. 2Gb for MSDE and 4Gb for SQL/E |
|
|
|
Re: Urgent Help! - Cutting Remote Office Problem
Posted: 05 Feb 09 8:47 AM
|
| Does sql 2005 support DTS packages? It doesn't so how will DTS packages execute on a 2005 sql box? At the bottom of your "cut remote" options there are dts packages to execute which can only be done on standard 2000. Moreover, when I try to cut it in 2005, I get "invalid object" errors cause it cannot find certain procedures. |
|
|
|
Re: Urgent Help! - Cutting Remote Office Problem
Posted: 05 Feb 09 8:50 AM
|
Yes, they will - in the form of legacy support. Your issue with procedures is probably related to this:
***************************************************************************************************************
***************************************************************************************************************
Using SQL2005 as host database and ability to create remotes
***************************************************************************************************************
***************************************************************************************************************
o Enable "xp_cmdshell" via Surface Configuration
- Used to to delete the current .LDF and .SXD file if they exist.
o Create in "master" db a view as:
- create view sysxlogins as select * from sys.syslogins
- The sysxlogins view is used to grab cached SQL user info. See
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sp3sec02.mspx
|
|
|
|