Viewing 15 posts - 271 through 285 (of 409 total)
Not all that familiar with current version of PowerBuilder but that particular error sounds like a client rather than SQL Server error - is it possible that your application is...
August 9, 2007 at 1:00 am
Ed -
Another option on a SQL 2000 box is to use a SMTP mailer - search on this site for "smtp mail" and you'll find some good alternatives to xp_sendmail...
August 9, 2007 at 12:46 am
Every time I read a thread regarding RAID levels/SAN/NAS, etc. I always wonder what the percentages of us that run on various storage technologies is - as RAID level, performance, etc....
August 9, 2007 at 12:24 am
Short and correct answer is definitely no, you cannot restore a native SQL 2005 backup on a SQL 2000 database for a lot of reasons (starting with new datatypes, collations,...
August 9, 2007 at 12:08 am
Kavic -
The defaults for the export wizard (and a transfer objects SSIS task) do not include primary keys, indexes, triggers, etc. You need to be sure to specify that primary...
August 9, 2007 at 12:04 am
Check and make sure that your user does not have any server level permissions - if the user only has permissions to specific databases default behavior in 2005 is to...
August 8, 2007 at 12:02 am
Carol -
Openquery executes the specified query against the remote dataset - all of your SQL must be acceptable to the remote server. Best test - if you can execute the...
August 7, 2007 at 11:57 pm
Louis -
The secret is the sql agent account - I bet if you check the old server you will find that the sql agent is running under a domain account...
August 7, 2007 at 7:57 pm
Randy -
A lot of the answer depends on the amount of customization that has been done to your CRM instance - for good or bad, CRM is highly customizable and...
August 7, 2007 at 12:12 am
What are the settings for auto update statistics, auto close and auto shrink? Any one of those could cause the scenario you've described.
August 7, 2007 at 12:01 am
Try this, you're looking for a derived table:
select
topicid, lastposterid, postdate
from tbl
inner join
August 6, 2007 at 11:56 pm
Sherry -
Your best best is to simply move your databases, logins, jobs, etc. to the new server by backing up/restoring the users databases, scripting logins (or transferring with SSIS), scripting jobs,...
August 6, 2007 at 11:54 pm
Louis -
Is the "old" server by any chance in another domain than the new server? Check the owners of each of the failing jobs and make sure it's a valid...
August 6, 2007 at 11:42 pm
Sherry -
Are you migrating (e.g. starting fresh on a new database server) or upgrading (e.g. running the upgrade process against an existing SQL 2000 instance)?
Joe
August 6, 2007 at 11:34 pm
Do you mean different DB's on the same server or different DB's on different servers?
If the databases are on the same server, no problem just qualify...
August 6, 2007 at 11:21 pm
Viewing 15 posts - 271 through 285 (of 409 total)