帆软报表执行sql报SQL command not properly ended

如果你在执行预览SQL时报如下图的错误:


 

你需要检查一下几点:

1.是否在SQL在有逗号忘记加了

2.是否有括号少了

3.是否在SQL的最后有分号存在,如果有需要去掉,这点是比较坑的,因为SQL最后加分号在oracle数据库中是能够执行的,但是在帆软这边是不能正常执行的

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Microsoft SQL Server has become an eminent relational database management system (RDBMS) in the marketplace. The SQL Server engine has come a long way from being just another RDBMS; it’s an end-toend business intelligence platform with built-in options for reporting; extract, transform, load (ETL); data mining; and high availability/disaster recovery (HA/DR). Its rich feature set provides a comprehensive solution for deploying, managing, monitoring, maintaining, auditing, reporting, and backing up and restoring databases; building data warehouses; and more! You will learn all about this as you journey through this book toward achieving healthy SQL. Whether it’s small, medium, or large enterprise infrastructures, it is common for organizations to have deployed multiple SQL Server instances in their environments, and as companies deploy various applications, many have had to deal with what’s known as SQL sprawl. This is the 1:1 ratio explosion of deploying every new application to its own SQL Server. The implementation of multiple SQL Server instances has made it difficult for database administrators to manage and maintain them. It is not uncommon to eventually embark on a SQL Server database consolidation project with the assistance of a qualified SQL Server database professional. Another common scenario is that third-party vendors will deploy their applications on back-end SQL Server instances and leave their clientele to their own devices. They will install SQL Server even though it’s doubtful that they know what the proper installation and configuration settings are. The goal of a vendor is to install and set up its application without regard for the ongoing health or performance of SQL Server. This is known as “Set it and forget it.” In a situation of “Set it and forget it,” as the application usage increases, as new records are continuously inserted, updated, and deleted, and as users place demand on the application, response times will eventually slow down, as will the overall performance of the SQL Server database back end. Indexes become fragmented, excessive page splitting occurs, and backups are not properly configured. All these issues that occur on the back-end SQL Server instance frustrate users, and organizations don’t usually have the database administrator (DBA) skill set in-house to fix these performance problems. Often the application vendor will not even have the right know-how or database expertise required to resolve these issues. In these situations, there are a myriad of questions that companies and database professionals need to ask themselves. For example, can SQL Server perform better? Can the application scale if it is necessary? Do we have a recent backup? Is there a disaster recovery plan? Can the database be restored?

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值