Viewing 4 posts - 1 through 4 (of 4 total)
Thanks!
November 4, 2011 at 4:40 am
#1403136
Hi,
sorry for my badly english.
I've also sometimes some unclear errors within one or the other
maintenanceplan.
First I've tried was to replace the backup step with the generated
t-sql-code from this step with...
July 22, 2009 at 5:15 am
#1028200
SoehnelS (7/10/2009) To fix the Problem I used the command (default instance): start /wait setup.exe /qb REINSTALL=SQL_Engine REBUILDDATABASE=SAPWD=useyourownpassword SQLCOLLATION=Latin1_General_CI_AS Now the server use the wished collation Latin1_General_CI_AS.
SoehnelS (7/10/2009)
start /wait setup.exe /qb REINSTALL=SQL_Engine REBUILDDATABASE=SAPWD=useyourownpassword SQLCOLLATION=Latin1_General_CI_AS
Now the server use the wished collation Latin1_General_CI_AS.
No, does'nt, uses Latin1_General_CI_AI...
I don't know why...
du.pereira...
July 11, 2009 at 4:55 am
#1023475
Hi @ all
and also sorry for my badly english (I'm from Germany:-)).
My Problem:
Existing Databases with collation Latin1_General_CI_AS should
be attached into an SQL Server 2005 on an US-English System.
When I install...
July 10, 2009 at 1:35 pm
#1023302