Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Thursday, May 22, 2025 
 
slxdeveloper.com Community Forums  
   
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!
 Data & Imports Forums - T-SQL & Queries
Forum to discuss general T-SQL questions and help with queries related to SalesLogix data. View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to T-SQL & Queries | New ThreadView:  Search:  
 Author  Thread: Modified field sizes
Michael Rogers
Posts: 70
 
Modified field sizesYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 07 Jan 08 4:57 PM
Getting ready to upgrade from 6.2.3 to 7.2.1 and it suddenly occured to me that our previous business partner might have changed field sizes on system tables (they were very creative.) Anyone have a query that will allow me to check that all fields in the DB are the same size after the upgrade (dev DB) that they were before the upgrade (current production?)

I tried to return the table name and field names from sysobjects and syscolumns but I can't join the two DBs on a compound key of table name and field name.

Thanks for any help you can send my way.

Michael
[Reply][Quote]
Bob (RJ)Ledger
Posts: 1103
Top 10 forum poster: 1103 posts
 
Re: Modified field sizesYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 09 Jan 08 7:00 AM
By "System Tables" you mean SalesLogix Tables.. right?

The only reason a partner may have done this (and most of us have at one time or another) was to solve a business problem where the length of a field was too short for typical (customer) data.

I'd leave it alone and just upgrade.
--
RJLedger - rjlSystems
[Reply][Quote]
Bob (RJ)Ledger
Posts: 1103
Top 10 forum poster: 1103 posts
 
Re: Modified field sizesYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 09 Jan 08 7:00 AM
By "System Tables" you mean SalesLogix Tables.. right?

The only reason a partner may have done this (and most of us have at one time or another) was to solve a business problem where the length of a field was too short for typical (customer) data.

I'd leave it alone and just upgrade.
--
RJLedger - rjlSystems
[Reply][Quote]
Eric Hobbs
Posts: 28
 
Re: Modified field sizesYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 10 Jan 08 3:02 AM
I am not sure if you realy need to bother with that, but if you do you might try using a tool like DB Compare (Google it). Back up a copy of the DB prior to upgrade, then restore it on a diferent server or on the same server as a different named database and compare the pre and post upgrade versions.

Hope that helps
[Reply][Quote]
 Page 1 of 1 
  You can subscribe to receive a daily forum digest in your user profile. View the site code of conduct for posting guidelines.

   Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
 

 
 slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.
 This site, and all contents herein, are Copyright © 2025 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 5/22/2025 8:00:51 PM