Putting SQL Server 05 database on GoDaddy server. Argh!!!

I have a simple Website and Database created in VWD exp.

I've just added a windows account to GoDaddy.com.

Unfortunately there is no way to port your database on to the GoDaddy server directly, but it says you must instead, recreate the database by copying and running SQL statements from a file called "personal-add.sql". (their "help" page: http://help.godaddy.com/article.php?article_id=695)

I can't find any such file. Can someone please let me know what I'm missing here?

Thanks.

Hi Brad -

You should take a look at the Database Publishing Wizard, available at http://www.codeplex.com/sqlhost/Wiki/View.aspx?title=Database%20Publishing%20Wizard&referringTitle=Home. We actually have a guide on how to upload databases using the tool to shared hosters like GoDaddy... see http://www.codeplex.com/sqlhost/Wiki/View.aspx?title=Tutorials&referringTitle=Database%20Publishing%20Wizard.

Let me know if you have any issues.

Thanks,

alex

|||

alex wrote:

Hi Brad -

You should take a look at the Database Publishing Wizard, available at http://www.codeplex.com/sqlhost/Wiki/View.aspx?title=Database%20Publishing%20Wizard&referringTitle=Home. We actually have a guide on how to upload databases using the tool to shared hosters like GoDaddy... see http://www.codeplex.com/sqlhost/Wiki/View.aspx?title=Tutorials&referringTitle=Database%20Publishing%20Wizard.

Let me know if you have any issues.

Thanks,

alex

Thanks for this, for those that are in the same situation as me, a useful program is The SQL Server Database Publishing Wizard

Put Windows Logs into SQL

Hi!
I am looking into a way to put Windows Logs into SQL Server database
and to be able to query them for specific information. Anybody know
the tool that I can use and be able to schedule it to run on a weekly
basis?
Thank you,
T.tolcis,
In Windows Scripting you can use the WMI datareader to read the Event Logs
into a structured resultset. Then you can use ADO to insert the rows into a
table. I don't have any examples handy, but this link might have what you
need. If not search Google.
http://www.databasejournal.com/feat...cle.php/1503181
-- Bill
"tolcis" <nytollydba@.gmail.com> wrote in message
news:1172591825.527761.216540@.8g2000cwh.googlegroups.com...
> Hi!
> I am looking into a way to put Windows Logs into SQL Server database
> and to be able to query them for specific information. Anybody know
> the tool that I can use and be able to schedule it to run on a weekly
> basis?
> Thank you,
> T.
>sql

Put Windows Logs into SQL

Hi!
I am looking into a way to put Windows Logs into SQL Server database
and to be able to query them for specific information. Anybody know
the tool that I can use and be able to schedule it to run on a weekly
basis?
Thank you,
T.tolcis,
In Windows Scripting you can use the WMI datareader to read the Event Logs
into a structured resultset. Then you can use ADO to insert the rows into a
table. I don't have any examples handy, but this link might have what you
need. If not search Google.
http://www.databasejournal.com/features/mssql/article.php/1503181
-- Bill
"tolcis" <nytollydba@.gmail.com> wrote in message
news:1172591825.527761.216540@.8g2000cwh.googlegroups.com...
> Hi!
> I am looking into a way to put Windows Logs into SQL Server database
> and to be able to query them for specific information. Anybody know
> the tool that I can use and be able to schedule it to run on a weekly
> basis?
> Thank you,
> T.
>

Put Windows Logs into SQL

Hi!
I am looking into a way to put Windows Logs into SQL Server database
and to be able to query them for specific information. Anybody know
the tool that I can use and be able to schedule it to run on a weekly
basis?
Thank you,
T.
tolcis,
In Windows Scripting you can use the WMI datareader to read the Event Logs
into a structured resultset. Then you can use ADO to insert the rows into a
table. I don't have any examples handy, but this link might have what you
need. If not search Google.
http://www.databasejournal.com/features/mssql/article.php/1503181
-- Bill
"tolcis" <nytollydba@.gmail.com> wrote in message
news:1172591825.527761.216540@.8g2000cwh.googlegrou ps.com...
> Hi!
> I am looking into a way to put Windows Logs into SQL Server database
> and to be able to query them for specific information. Anybody know
> the tool that I can use and be able to schedule it to run on a weekly
> basis?
> Thank you,
> T.
>

Put data on Windows Storage 2003

We have a NAS-server with WIndows storage 2003, with 3 data-disks in Raid.
Would it be possible to setup an SQL-server on another Windows 2003 server
but ...
put the data on the NAS-server?
And if so what could be the disadvantages?No, you can only use local storage for SQL Server (with local I include SAN, as it is viewed by the
OS as being local). Well, there used to be a trace flag you could add to be able to create a
database on a remote server, but the general consensus is to *not* use it and I don't know it that
even still exists.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"MarioFromBelgium" <MarioFromBelgium@.discussions.microsoft.com> wrote in message
news:73F03CB4-87F8-4221-85FF-91AF6539B7F7@.microsoft.com...
> We have a NAS-server with WIndows storage 2003, with 3 data-disks in Raid.
> Would it be possible to setup an SQL-server on another Windows 2003 server
> but ...
> put the data on the NAS-server?
> And if so what could be the disadvantages?|||try to use the iSCSI protocol.
you can install an iSCSI target (server) on you storage server and connect
your SQL server to this iSCSI server.
the performance is better then a shared folder access.
but limited by the network speed.
for iSCSI I recommand to setup a dedicated subnet with Gbps cards and
switches that support jumbo frames.
Some Storage server vendors provides an iSCSI target in option.
"MarioFromBelgium" <MarioFromBelgium@.discussions.microsoft.com> wrote in
message news:73F03CB4-87F8-4221-85FF-91AF6539B7F7@.microsoft.com...
> We have a NAS-server with WIndows storage 2003, with 3 data-disks in Raid.
> Would it be possible to setup an SQL-server on another Windows 2003 server
> but ...
> put the data on the NAS-server?
> And if so what could be the disadvantages?

Put data on Windows Storage 2003

We have a NAS-server with WIndows storage 2003, with 3 data-disks in Raid.
Would it be possible to setup an SQL-server on another Windows 2003 server
but ...
put the data on the NAS-server?
And if so what could be the disadvantages?No, you can only use local storage for SQL Server (with local I include SAN,
as it is viewed by the
OS as being local). Well, there used to be a trace flag you could add to be
able to create a
database on a remote server, but the general consensus is to *not* use it an
d I don't know it that
even still exists.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"MarioFromBelgium" <MarioFromBelgium@.discussions.microsoft.com> wrote in mes
sage
news:73F03CB4-87F8-4221-85FF-91AF6539B7F7@.microsoft.com...
> We have a NAS-server with WIndows storage 2003, with 3 data-disks in Raid.
> Would it be possible to setup an SQL-server on another Windows 2003 server
> but ...
> put the data on the NAS-server?
> And if so what could be the disadvantages?|||try to use the iSCSI protocol.
you can install an iSCSI target (server) on you storage server and connect
your SQL server to this iSCSI server.
the performance is better then a shared folder access.
but limited by the network speed.
for iSCSI I recommand to setup a dedicated subnet with Gbps cards and
switches that support jumbo frames.
Some Storage server vendors provides an iSCSI target in option.
"MarioFromBelgium" <MarioFromBelgium@.discussions.microsoft.com> wrote in
message news:73F03CB4-87F8-4221-85FF-91AF6539B7F7@.microsoft.com...
> We have a NAS-server with WIndows storage 2003, with 3 data-disks in Raid.
> Would it be possible to setup an SQL-server on another Windows 2003 server
> but ...
> put the data on the NAS-server?
> And if so what could be the disadvantages?

Pull Merge replication between two SQL Server machines in different, but trusted domains

Hi,
We are attempting to setup Pull Merge replication between two SQL Server
(SQL 2K sp3a, Windows Authentication) machines in different domains. We have
been able to get Pull Merge replication to work within the same domain.
While we are running Win2k on both machines, two one way trusts were setup
between them. The server are linked to each other, but cannot initiate the
replication agents. The message we get is:
SQL Server Agent could not access the replication agent. Use the DCOMCNFG
utility to confirm that the SQL Server Agent Windows account has permissions
to launch the replication agent. The step failed.
I did not spot any in DCOMCNFG, but I am not familiar with it. Any
suggections?
Tia
Paul
Paul,
here is an MSDN article which shows how to enable the merge agent to be run
remotely:
http://msdn.microsoft.com/library/de...us/howtosql/ht
_replctem_6c1l.asp
HTH,
Paul Ibison
|||I have a feeling that the error message may be misleading me away from the
true problem. It appears that DCOMCNFG is used for running agents remotely.
I am looking at having the push replication run at the distributor and pull
replications to run at the subscriber. Besides, I couldn't get it to work by
using DCOMCNFG.
I want to have one merge publication which is pushed to subscribers which
will not be intentionally disconnected from the network. And, the same
publication pulled to subscribers which will be removed from the network for
possibly weeks. This currently works as long as long as all the servers are
in the same domain. The problem is that the pull subscribers will be in
different domains with trust relationship setup between them and the
distributor.
When I take the existing scripts that work when all of the server are in the
same domain and run them with the pull subscriber in different domains I get
the error:
SQL Server Agent could not access the replication agent. Use the DCOMCNFG
utility to confirm that the SQL Server Agent Windows account has permissions
to launch the replication agent. The step failed.
I don't think this has any thing to do with running the agent remotely, but
I'm not sure. Any suggestions?
Thanks
Paul
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uQmkhv7FEHA.744@.TK2MSFTNGP09.phx.gbl...
> Paul,
> here is an MSDN article which shows how to enable the merge agent to be
run
> remotely:
>
http://msdn.microsoft.com/library/de...us/howtosql/ht
> _replctem_6c1l.asp
> HTH,
> Paul Ibison
>
|||PaulW,
The easiest way to set up replication between different domains is to create a local user account on both the servers with the same username and password. Make the account an administrator of the local machine. Then set this account as the startup account
for the SQL Server Agent. Restart the SQL Server agent and start the merge agent. This should fix your problem.
Regards
Chris R
|||Thanks for the response. I saw that option for non-trusted domains and when
I presented it, the option was quickly shot down because the production
system will be administered by different companies and they didn't want to
be forced to share passwords..
Thanks,
Paul
"Chris R" <crichardson@.iir-central.com> wrote in message
news:7CE505D6-BE9C-40E4-80D4-75F7287AAB3C@.microsoft.com...
> PaulW,
> The easiest way to set up replication between different domains is to
create a local user account on both the servers with the same username and
password. Make the account an administrator of the local machine. Then set
this account as the startup account for the SQL Server Agent. Restart the
SQL Server agent and start the merge agent. This should fix your problem.
> Regards
> Chris R
|||Non-trusted domains can also be set up using the Guest account, but I would assume that this is even less likely to be allowed :-)
Regards,
Paul Ibison
|||I already know that the guest account has been disabled. There will be a two
way trust between the domains. I don't know how that got approved. There
must be some way to perform pull subscriptions in a trusted relationship
without matching accounts and passwords.
Paul
|||Paul,
I have used pass-through security, or the guest account, because of working
in a non-trusted environment but in your case you should be able to use
impersonation. Have a look at this article:
http://support.microsoft.com/?id=321822.
Regards,
Paul Ibison
|||I think I got it. We started having net work troubles once it appeared to be
working, so I'm not sure. The problem was that the SQL Server agent accounts
had the same name on both machines, but different passwords. Once I changed
the name of the account on one machine and gave it dbo access to the other
machine's database it looked like it was working. Most of the initial
snapshot was applied, but it failed due to the retry count. Before this
change, it never get started.
Thanks for the help.
Paul

Publisher Issues

Right i have two sql 2005 standard edition boxes within a Windows 2003 R2 active directory environment. All updates sp1 etc.

I have an mssql service account setup in AD which all the mssql services on both servers startup with.
I went to setup replication between the two servers for one db.
Firstly i setup distribution no problems no errors.

Then i went to setup the publication, all went well no errors in management studio gui but in the application event logs i got the following:

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 14151
Date: 05/10/2006
Time: 12:37:43
User: DNETWORK\mssqlservice
Computer: SGC
Description:
Replication-Replication Transaction-Log Reader Subsystem: agent SGC-MerakDB-2 failed. Executed as user: dnetwork\sqlrep. A required privilege is not held by the client. The step failed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 47 37 00 00 12 00 00 00 G7......
0008: 04 00 00 00 53 00 47 00 ....S.G.
0010: 43 00 00 00 0d 00 00 00 C.......
0018: 64 00 69 00 73 00 74 00 d.i.s.t.
0020: 72 00 69 00 62 00 75 00 r.i.b.u.
0028: 74 00 69 00 6f 00 6e 00 t.i.o.n.
0030: 00 00

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 14151
Date: 05/10/2006
Time: 12:37:51
User: DNETWORK\mssqlservice
Computer: SGC
Description:
Replication-Replication Snapshot Subsystem: agent SGC-MerakDB-Merak Mail DB-2 failed. Executed as user: dnetwork\sqlrep. A required privilege is not held by the client. The step failed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 47 37 00 00 12 00 00 00 G7......
0008: 04 00 00 00 53 00 47 00 ....S.G.
0010: 43 00 00 00 0d 00 00 00 C.......
0018: 64 00 69 00 73 00 74 00 d.i.s.t.
0020: 72 00 69 00 62 00 75 00 r.i.b.u.
0028: 74 00 69 00 6f 00 6e 00 t.i.o.n.
0030: 00 00

I've tried all sorts to get this to work, the sqlrep user is db_owner for the distro db, ive tried the sqlrep user as domain admin to see if it was a system priv issue, no luck :(

Anyone have any ideas?

Is the account dnetwork\sqlrep the same as SQL Server service account? You can try to add dnetwork\sqlrep to windows user group SQLServer2005SQLAgentUser$<MachineName>$MSSQLSERVER, SQLServer2005MSSQLUser$<MachineName>$MSSQLSERVER, then restart SQL Server service, or reboot the machine to see if the problem goes away. Also can you let us know if you have changed SQL Server service account after installation? If so, it has to be done through SQL Server configuration manager.

Thanks,

Zhiqiang Feng

|||

I tried what you suggested, no luck,

theres a service account for mssql which i named mssqlservice :)
That was set during setup and never changed.

sqlrep was created for replication only, i had already added it to the groups you suggested with no luck. The same error etc.

So i uninstalled then reinstalled mssql from scratch no problems this time.

I believe it was down to a active directory issue when we had to run gpofix it may have altered something down the line. The issue was effecting both servers so i assume it was caused by the active directory issue.

Bit strange though but its sorted now, well so far so good :)

PSSDIAG

Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
Server 2000 SP4 ? It seems to hang.
The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.
I wouldn't use that tool during business hours. I did and it crashed my
server, desipte MS assuring that it would be fine.
"Sylvain Nadeau" wrote:

> Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
> Server 2000 SP4 ? It seems to hang.
> The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.

PSSDIAG

I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4.
The collectif of the trace seems to go well.
When I stop the trace the programm seems to hang after the last message that
says that it's exiting.
I dont't have the problem on a Windows XP SP1.
Is there an issue for windows 2003 sp1 ?
Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
diagnostic ?
1- Do not install PSSDiag in c:\program files or any other directory that
have blank in its name
2- There are two requirements for the PSSDIAG service startup account: 1) it
must be a member of the local administrators group (though not necessarily
the local Administrator), and 2) it must be a member of the SQL Server
sysadmin server role. The default PSSDIAG service startup account is
LocalSystem, and by default it satisfies both of these requirements.
However, if you have removed the local Administrators group from the SQL
sysadmin role, you will need to choose a new PSSDIAG service startup account
that is both an NT administrator and a SQL sysadmin.
3- The .trc file is actually written by the SQL Server process. For this
reason, the SQL Server service startup account must be able to write to the
output directory.
"Sylvain Nadeau" wrote:

> I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4.
> The collectif of the trace seems to go well.
> When I stop the trace the programm seems to hang after the last message that
> says that it's exiting.
> I dont't have the problem on a Windows XP SP1.
> Is there an issue for windows 2003 sp1 ?
> Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
> diagnostic ?

PSSDIAG

I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4.
The collectif of the trace seems to go well.
When I stop the trace the programm seems to hang after the last message that
says that it's exiting.
I dont't have the problem on a Windows XP SP1.
Is there an issue for windows 2003 sp1 ?
Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
diagnostic ?1- Do not install PSSDiag in c:\program files or any other directory that
have blank in its name
2- There are two requirements for the PSSDIAG service startup account: 1) it
must be a member of the local administrators group (though not necessarily
the local Administrator), and 2) it must be a member of the SQL Server
sysadmin server role. The default PSSDIAG service startup account is
LocalSystem, and by default it satisfies both of these requirements.
However, if you have removed the local Administrators group from the SQL
sysadmin role, you will need to choose a new PSSDIAG service startup account
that is both an NT administrator and a SQL sysadmin.
3- The .trc file is actually written by the SQL Server process. For this
reason, the SQL Server service startup account must be able to write to the
output directory.
"Sylvain Nadeau" wrote:

> I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4
.
> The collectif of the trace seems to go well.
> When I stop the trace the programm seems to hang after the last message th
at
> says that it's exiting.
> I dont't have the problem on a Windows XP SP1.
> Is there an issue for windows 2003 sp1 ?
> Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
> diagnostic ?

PSSDIAG

Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
Server 2000 SP4 ? It seems to hang.
The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.I wouldn't use that tool during business hours. I did and it crashed my
server, desipte MS assuring that it would be fine.
"Sylvain Nadeau" wrote:

> Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
> Server 2000 SP4 ? It seems to hang.
> The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.

PSSDIAG

I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4.
The collectif of the trace seems to go well.
When I stop the trace the programm seems to hang after the last message that
says that it's exiting.
I dont't have the problem on a Windows XP SP1.
Is there an issue for windows 2003 sp1 ?
Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
diagnostic ?1- Do not install PSSDiag in c:\program files or any other directory that
have blank in its name
2- There are two requirements for the PSSDIAG service startup account: 1) it
must be a member of the local administrators group (though not necessarily
the local Administrator), and 2) it must be a member of the SQL Server
sysadmin server role. The default PSSDIAG service startup account is
LocalSystem, and by default it satisfies both of these requirements.
However, if you have removed the local Administrators group from the SQL
sysadmin role, you will need to choose a new PSSDIAG service startup account
that is both an NT administrator and a SQL sysadmin.
3- The .trc file is actually written by the SQL Server process. For this
reason, the SQL Server service startup account must be able to write to the
output directory.
"Sylvain Nadeau" wrote:
> I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4.
> The collectif of the trace seems to go well.
> When I stop the trace the programm seems to hang after the last message that
> says that it's exiting.
> I dont't have the problem on a Windows XP SP1.
> Is there an issue for windows 2003 sp1 ?
> Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
> diagnostic ?

PSSDIAG

Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
Server 2000 SP4 ? It seems to hang.
The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.I wouldn't use that tool during business hours. I did and it crashed my
server, desipte MS assuring that it would be fine.
"Sylvain Nadeau" wrote:
> Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
> Server 2000 SP4 ? It seems to hang.
> The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.