Current errorlog not showing

Hello everybody,
last week I had to move my master database en with it the location of
my SQL Server errorlogs. Since then new errorlogs are created in the
new location specified in the startup parameter, but in EM I can only
see the archived ones, not the current.
Turns out that xp_enumerrorlogs don't return 0, the number for the
current errorlog. Executing sp_readerrorlog returns the content of
current errorlog.
Any ideas how to fix this?
Tia Markus
From the EM, click on Server properties, General Tab & click startup
parameters. The location of the error log can be changed there.
Alternatively, you can change the location directly in the registry as well.
Anith
|||Have a look at startup parameters in EM. There is a -e entry for the
location of the errorlog, chaging it here should resolve. The value is being
saved under the following Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer\Parameters
Open EM / Right Click "Server" / Properties and choose Startup Parameters
HTH. Ryan
"MarkusB" <m.bohse@.quest-consultants.com> wrote in message
news:1139839000.665337.12560@.g44g2000cwa.googlegro ups.com...
> Hello everybody,
> last week I had to move my master database en with it the location of
> my SQL Server errorlogs. Since then new errorlogs are created in the
> new location specified in the startup parameter, but in EM I can only
> see the archived ones, not the current.
> Turns out that xp_enumerrorlogs don't return 0, the number for the
> current errorlog. Executing sp_readerrorlog returns the content of
> current errorlog.
> Any ideas how to fix this?
> Tia Markus
>
|||Thanks guys,
I found the problem in the mean time. I had checked the startup
parameter and the registry before, but missed the fact that there was a
trailing space. This had the annoying effect that archive logs had a
name like ERRORLOG .1 and thus appeared in EM. For the current log
Windows removes the trailing space and that's why xp_enumerrorlogs was
unable to find it.
Markus
sql

Current errorlog not showing

Hello everybody,
last week I had to move my master database en with it the location of
my SQL Server errorlogs. Since then new errorlogs are created in the
new location specified in the startup parameter, but in EM I can only
see the archived ones, not the current.
Turns out that xp_enumerrorlogs don't return 0, the number for the
current errorlog. Executing sp_readerrorlog returns the content of
current errorlog.
Any ideas how to fix this?
Tia MarkusFrom the EM, click on Server properties, General Tab & click startup
parameters. The location of the error log can be changed there.
Alternatively, you can change the location directly in the registry as well.
Anith|||Have a look at startup parameters in EM. There is a -e entry for the
location of the errorlog, chaging it here should resolve. The value is being
saved under the following Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\Parameters
Open EM / Right Click "Server" / Properties and choose Startup Parameters
HTH. Ryan
"MarkusB" <m.bohse@.quest-consultants.com> wrote in message
news:1139839000.665337.12560@.g44g2000cwa.googlegroups.com...
> Hello everybody,
> last week I had to move my master database en with it the location of
> my SQL Server errorlogs. Since then new errorlogs are created in the
> new location specified in the startup parameter, but in EM I can only
> see the archived ones, not the current.
> Turns out that xp_enumerrorlogs don't return 0, the number for the
> current errorlog. Executing sp_readerrorlog returns the content of
> current errorlog.
> Any ideas how to fix this?
> Tia Markus
>|||Thanks guys,
I found the problem in the mean time. I had checked the startup
parameter and the registry before, but missed the fact that there was a
trailing space. This had the annoying effect that archive logs had a
name like ERRORLOG .1 and thus appeared in EM. For the current log
Windows removes the trailing space and that's why xp_enumerrorlogs was
unable to find it.
Markus

Current errorlog not showing

Hello everybody,
last week I had to move my master database en with it the location of
my SQL Server errorlogs. Since then new errorlogs are created in the
new location specified in the startup parameter, but in EM I can only
see the archived ones, not the current.
Turns out that xp_enumerrorlogs don't return 0, the number for the
current errorlog. Executing sp_readerrorlog returns the content of
current errorlog.
Any ideas how to fix this?
Tia MarkusFrom the EM, click on Server properties, General Tab & click startup
parameters. The location of the error log can be changed there.
Alternatively, you can change the location directly in the registry as well.
--
Anith|||Have a look at startup parameters in EM. There is a -e entry for the
location of the errorlog, chaging it here should resolve. The value is being
saved under the following Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters
Open EM / Right Click "Server" / Properties and choose Startup Parameters
HTH. Ryan
"MarkusB" <m.bohse@.quest-consultants.com> wrote in message
news:1139839000.665337.12560@.g44g2000cwa.googlegroups.com...
> Hello everybody,
> last week I had to move my master database en with it the location of
> my SQL Server errorlogs. Since then new errorlogs are created in the
> new location specified in the startup parameter, but in EM I can only
> see the archived ones, not the current.
> Turns out that xp_enumerrorlogs don't return 0, the number for the
> current errorlog. Executing sp_readerrorlog returns the content of
> current errorlog.
> Any ideas how to fix this?
> Tia Markus
>|||Thanks guys,
I found the problem in the mean time. I had checked the startup
parameter and the registry before, but missed the fact that there was a
trailing space. This had the annoying effect that archive logs had a
name like ERRORLOG .1 and thus appeared in EM. For the current log
Windows removes the trailing space and that's why xp_enumerrorlogs was
unable to find it.
Markus

Cube with more that one facts Table

Hello,

I made an illustration, that describes the szenario. There is one Master, one dimension and a second facts table. The Master Table holds up all objects. Sometimes I have additional Information for some objects in Master Table. They are stored in extra tables like the table Optional_facts_for_villas.

My question: How can I combine these two fact tables in Cube Designer without doing a Full outer Join in my Database?

The reason why I want it this way, not all optional_fact_tables are necessary now for OLAP, but maybe later. So, I thought, easiest way would be, adding them later to the cube, without changing the database.
Sorry for my english, its not the best :)

SilasYou forgot to mention which version of SQL Server you are using. As far as I remember this should be possible by using SQL Server 2005, but not SQL Server 2000.|||Ok, it's 2000. I think I will use the full outer join ;)

ct_connect errors in xp_cmdshell

I am running a bcp from xp_cmdshell, it was working good
EXEC master.dbo.xp_cmdshell 'bcp DATABASE1..V_TMP_KEYWORDSMMS2 out
c:\Keywords\KEYWORD_00000115_16_12_2004_17_47_27.t xt -c -t~ -SSYN0001
-UUserName -Ppassword '
The server is Microsoft SQL Server 2000 - 8.00.760
Then I installed sybase client in the PC inorder to get replication from
sybase to sql server.
It is giving the following error message.
CTLIB Message: - L6/O8/S5/N3/5/0:
ct_connect(): directory service layer: internal directory control layer
error: Requested server name not found.
Establishing connection failed.
NULL
Any help why is this happenning?
The server, username, password are all correct and I am able to work through
the enterprise manager and query analyser, its gving error only in the
xp_cmdshell and bcp.
After the install, the xp_cmdshell and bcp is not working anymore.
Hi
The Sybase BCP.exe is now being used by your call due to the environment
path settings written by the Sybase setup.
Fully qualify the BCP.exe path in the call and it will work. osql.exe is
also affected in the same way.
Regards
Mike
"Yog" wrote:

> I am running a bcp from xp_cmdshell, it was working good
> EXEC master.dbo.xp_cmdshell 'bcp DATABASE1..V_TMP_KEYWORDSMMS2 out
> c:\Keywords\KEYWORD_00000115_16_12_2004_17_47_27.t xt -c -t~ -SSYN0001
> -UUserName -Ppassword '
> The server is Microsoft SQL Server 2000 - 8.00.760
> Then I installed sybase client in the PC inorder to get replication from
> sybase to sql server.
> It is giving the following error message.
> CTLIB Message: - L6/O8/S5/N3/5/0:
> ct_connect(): directory service layer: internal directory control layer
> error: Requested server name not found.
> Establishing connection failed.
> NULL
> Any help why is this happenning?
> The server, username, password are all correct and I am able to work through
> the enterprise manager and query analyser, its gving error only in the
> xp_cmdshell and bcp.
> After the install, the xp_cmdshell and bcp is not working anymore.
>
>
|||Thank you Mike, that worked.
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> The Sybase BCP.exe is now being used by your call due to the environment
> path settings written by the Sybase setup.
> Fully qualify the BCP.exe path in the call and it will work. osql.exe is
> also affected in the same way.
> Regards
> Mike
> "Yog" wrote:

ct_connect errors in xp_cmdshell

I am running a bcp from xp_cmdshell, it was working good
EXEC master.dbo.xp_cmdshell 'bcp DATABASE1..V_TMP_KEYWORDSMMS2 out
c:\Keywords\KEYWORD_00000115_16_12_2004_17_47_27.txt -c -t~ -SSYN0001
-UUserName -Ppassword '
The server is Microsoft SQL Server 2000 - 8.00.760
Then I installed sybase client in the PC inorder to get replication from
sybase to sql server.
It is giving the following error message.
CTLIB Message: - L6/O8/S5/N3/5/0:
ct_connect(): directory service layer: internal directory control layer
error: Requested server name not found.
Establishing connection failed.
NULL
Any help why is this happenning?
The server, username, password are all correct and I am able to work through
the enterprise manager and query analyser, its gving error only in the
xp_cmdshell and bcp.
After the install, the xp_cmdshell and bcp is not working anymore.Hi
The Sybase BCP.exe is now being used by your call due to the environment
path settings written by the Sybase setup.
Fully qualify the BCP.exe path in the call and it will work. osql.exe is
also affected in the same way.
Regards
Mike
"Yog" wrote:
> I am running a bcp from xp_cmdshell, it was working good
> EXEC master.dbo.xp_cmdshell 'bcp DATABASE1..V_TMP_KEYWORDSMMS2 out
> c:\Keywords\KEYWORD_00000115_16_12_2004_17_47_27.txt -c -t~ -SSYN0001
> -UUserName -Ppassword '
> The server is Microsoft SQL Server 2000 - 8.00.760
> Then I installed sybase client in the PC inorder to get replication from
> sybase to sql server.
> It is giving the following error message.
> CTLIB Message: - L6/O8/S5/N3/5/0:
> ct_connect(): directory service layer: internal directory control layer
> error: Requested server name not found.
> Establishing connection failed.
> NULL
> Any help why is this happenning?
> The server, username, password are all correct and I am able to work through
> the enterprise manager and query analyser, its gving error only in the
> xp_cmdshell and bcp.
> After the install, the xp_cmdshell and bcp is not working anymore.
>
>|||Thank you Mike, that worked.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> The Sybase BCP.exe is now being used by your call due to the environment
> path settings written by the Sybase setup.
> Fully qualify the BCP.exe path in the call and it will work. osql.exe is
> also affected in the same way.
> Regards
> Mike
> "Yog" wrote:
> > I am running a bcp from xp_cmdshell, it was working good
> >
> > EXEC master.dbo.xp_cmdshell 'bcp DATABASE1..V_TMP_KEYWORDSMMS2 out
> > c:\Keywords\KEYWORD_00000115_16_12_2004_17_47_27.txt -c -t~ -SSYN0001
> > -UUserName -Ppassword '
> >
> > The server is Microsoft SQL Server 2000 - 8.00.760
> >
> > Then I installed sybase client in the PC inorder to get replication from
> > sybase to sql server.
> >
> > It is giving the following error message.
> >
> > CTLIB Message: - L6/O8/S5/N3/5/0:
> > ct_connect(): directory service layer: internal directory control layer
> > error: Requested server name not found.
> > Establishing connection failed.
> > NULL
> >
> > Any help why is this happenning?
> >
> > The server, username, password are all correct and I am able to work through
> > the enterprise manager and query analyser, its gving error only in the
> > xp_cmdshell and bcp.
> >
> > After the install, the xp_cmdshell and bcp is not working anymore.
> >
> >
> >